From: Jens Axboe <axboe@suse.de>
To: Moritz Muehlenhoff <jmm@informatik.uni-bremen.de>
Cc: linux-kernel@vger.kernel.org, ken@kenjo.org, cw@f00f.org
Subject: Re: [BUG] DVD writing in 2.6.6-rc2
Date: Wed, 28 Apr 2004 13:30:56 +0200 [thread overview]
Message-ID: <20040428113056.GA2150@suse.de> (raw)
In-Reply-To: <8n23m1-g22.ln1@legolas.mmuehlenhoff.de>
On Wed, Apr 28 2004, Moritz Muehlenhoff wrote:
> Jens Axboe wrote:
> >> I have a problem when using growisofs version 5.19.
> >>
> >> The problem is that in the very end when gowisofs tries to flush the
> >> cache. When stracing the process I can see it sits in a call to poll
> >> that never returns.
> >
> > I noted the same thing yesterday with cdrdao, so yours is not an
> > isolated incident. I'll debug it tomorrow.
>
> I can confirm this bug for kernel 2.6.3-rc4 as well, so it's not too recent.
> I found the following on my console after quitting k3b ungracefully, maybe
This is really strange, I haven't been able to locate a kernel problem.
Looking at command traces, cdrdao issues two FLUSH_CACHE commands when
ending the writes. The last commands are:
0x2a (last real write)
0x35 (first flush cache) (takes about 10 seconds to complete)
0x00 (test unit ready)
0x51 (read disc info, length 4)
0x35 (2nd flush cache) -> never completes
That last sync cache never generates an interrupt, so cdrdao gets stuck
forever waiting on it. I cannot even reproduce this with a test case
--
Jens Axboe
next prev parent reply other threads:[~2004-04-28 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 17:59 [BUG] DVD writing in 2.6.6-rc2 Kenneth Johansson
2004-04-27 18:36 ` Jens Axboe
2004-04-27 22:16 ` Moritz Muehlenhoff
2004-04-28 11:30 ` Jens Axboe [this message]
2004-04-28 18:29 ` Kenneth Johansson
2004-04-28 20:09 ` Jens Axboe
2004-04-28 22:13 ` Chris Wedgwood
2004-04-29 6:19 ` Jens Axboe
2004-04-29 6:24 ` Chris Wedgwood
2004-04-29 6:29 ` Jens Axboe
2004-04-28 19:20 ` Moritz Muehlenhoff
2004-04-27 22:24 ` Panagiotis Papadakos
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=20040428113056.GA2150@suse.de \
--to=axboe@suse.de \
--cc=cw@f00f.org \
--cc=jmm@informatik.uni-bremen.de \
--cc=ken@kenjo.org \
--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