linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samium Gromoff <deepfire@ibe.miee.ru>
To: linux-kernel@vger.kernel.org
Subject: [IDE] 2.6.0-test1: (__ide_dma_test_irq) called while not waiting
Date: Thu, 24 Jul 2003 14:39:34 +0400	[thread overview]
Message-ID: <87r84g5huh.wl%deepfire@ibe.miee.ru> (raw)


That is an intel i443bx ide controller, with a rather dated 2gb
quantum pioneer attached to it.

That i get rather repeatable, sometimes:

Jul 22 19:57:17 betelheise kernel: hda: dma_timer_expiry: dma status == 0x21
Jul 22 19:57:27 betelheise kernel: hda: timeout waiting for DMA
Jul 22 19:57:27 betelheise kernel: hda: timeout waiting for DMA
Jul 22 19:57:27 betelheise kernel: hda: (__ide_dma_test_irq) called while not waiting
Jul 22 19:57:27 betelheise kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Jul 22 19:57:27 betelheise kernel:
Jul 22 19:57:27 betelheise kernel: hda: drive not ready for command
Jul 22 19:57:49 betelheise kernel: hda: dma_timer_expiry: dma status == 0x21
hda: timeout waiting for DMA
hda: timeout waiting for DMA
hda: (__ide_dma_test_irq) called while not waiting
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hda: drive not ready for command
Jul 22 19:57:59 betelheise kernel: hda: timeout waiting for DMA
Jul 22 19:57:59 betelheise kernel: hda: timeout waiting for DMA
Jul 22 19:57:59 betelheise kernel: hda: (__ide_dma_test_irq) called while not waiting
Jul 22 19:57:59 betelheise kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Jul 22 19:57:59 betelheise kernel:
Jul 22 19:57:59 betelheise kernel: hda: drive not ready for command

regards, Samium Gromoff

             reply	other threads:[~2003-07-24 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 10:39 Samium Gromoff [this message]
2003-07-24 10:53 ` [IDE] 2.6.0-test1: (__ide_dma_test_irq) called while not waiting Samium Gromoff
2003-07-24 16:28 ` Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r84g5huh.wl%deepfire@ibe.miee.ru \
    --to=deepfire@ibe.miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).