From: Jens Axboe <axboe@suse.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: readcd hangs in blk_execute_rq
Date: Thu, 21 Oct 2004 18:11:01 +0200 [thread overview]
Message-ID: <20041021161100.GA14154@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0410211844540.29471-100000@math.ut.ee>
On Thu, Oct 21 2004, Meelis Roos wrote:
> > > And here it hangs. ps shows readcd is in D state, in blk_execute_rq.
> > > dmesg shows lines of
> > >
> > > hdc: lost interrupt
>
> Meanwhile I found out that if I eject the CD by pressing button, it
> resumes its work and reports error to the user process.
>
> > > ide-cd: cmd 0x28 timed out
> > > hdc: DMA interrupt recovery
> > > hdc: lost interrupt
> > > hdc: status timeout: status=0xd0 { Busy }
> > > hdc: status timeout: error=0x00
> > > hdc: DMA disabled
> > > hdc: drive not ready for command
> > > hdc: ATAPI reset complete
> >
> > Did it previously work reliably with dma (which kernel)? Does it now
> > work reliably without dma now? Do send your entire dmesg after a boot
> > too, btw.
>
> It worked in earlier 2.4 kernels (2.4.18?) with DMA - I don't remember
> if it had some reliability problems. Since then, it's no dma. We have 3
> such computers here (Intel D816EEA2 mainboard, this specific Sony CDrom)
> and they all behave the same.
2.4.x never used dma for this operation. Does 2.6.9 work if you turn off
dma first?
--
Jens Axboe
next prev parent reply other threads:[~2004-10-21 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 15:11 readcd hangs in blk_execute_rq Meelis Roos
2004-10-21 15:41 ` Jens Axboe
2004-10-21 15:47 ` Meelis Roos
2004-10-21 16:11 ` Jens Axboe [this message]
2004-10-21 16:19 ` Meelis Roos
2004-10-21 16:22 ` Jens Axboe
2004-10-21 17:16 ` Meelis Roos
2004-10-21 20:15 ` Jens Axboe
2004-10-22 7:53 ` Meelis Roos
2004-10-25 16:55 ` Meelis Roos
2004-10-25 16:58 ` Jens Axboe
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=20041021161100.GA14154@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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