From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>, efault@gmx.de
Cc: James.Bottomley@SteelEye.com, michaelc@cs.wisc.edu,
jens.axboe@oracle.com, jgarzik@pobox.com,
B.Zolnierkiewicz@elka.pw.edu.pl, linux-ide@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, gd@spherenet.de, akpm@osdl.org,
bunk@stusta.de
Subject: Re: 2.6.20-rc6: known unfixed regressions (v2) (part 2)
Date: Fri, 02 Feb 2007 14:07:36 +0100 [thread overview]
Message-ID: <20070202130736.185460@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701282247070.3611@woody.linux-foundation.org>
-------- Original-Nachricht --------
Datum: Sun, 28 Jan 2007 23:04:49 -0800 (PST)
Von: Linus Torvalds <torvalds@linux-foundation.org>
An: Mike Galbraith <efault@gmx.de>
CC: Uwe Bugla <uwe.bugla@gmx.de>, Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>, gd@spherenet.de, alan@lxorguk.ukuu.org.uk, linux-ide@vger.kernel.org, B.Zolnierkiewicz@elka.pw.edu.pl, Jeff Garzik <jgarzik@pobox.com>, Jens Axboe <jens.axboe@oracle.com>, Mike Christie <michaelc@cs.wisc.edu>, James Bottomley <James.Bottomley@SteelEye.com>
Betreff: Re: 2.6.20-rc6: known unfixed regressions (v2) (part 2)
>
>
> [ Added Jeff, Jens and Mike Christie to Cc. I would _guess_ this is
> associated with the "larger block pc request" stuff: Mike, Jens? James B
> added for good luck.
>
> It apparently started happening somewhere between 2.6.19 and 2.6.20-rc2,
> and doing a
>
> gitk v2.6.19..v2.6.20-rc2 block/scsi_ioctl.c drivers/ide/
>
> I don't see anything else that really looks all that suspicious.. Unless
> maybe it's that "Fix SG_IO leak". Jeff added because of the hddtemp
> issue, but I think that was effectively SATA-only, so probably isn't
> relevant.
>
> Damn, I just realized that Jens is in the middle of his vacation for a
> week..
>
> Mike, can you please look at this and check? ]
>
> On Mon, 29 Jan 2007, Mike Galbraith wrote:
> >
> > FWIW, I just tried it with 2.6.20-rc6, and can confirm. Once nero is
> > run, the kernel never gives up retrying whatever command failed, so I
> > get...
> >
> > [ 4362.972995] hdd: status error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> > [ 4362.981475] ide: failed opcode was: unknown
> > [ 4362.986183] hdd: drive not ready for command
>
> Ok, I tried the demo version you can download at
>
> http://www.nero.com/eng/nerolinux-prog.html
>
> and yes, nerolinux seems broken. I've never used it before, but it
> triggers:
>
> hda: irq timeout: status=0xc0 { Busy }
> ide: failed opcode was: unknown
>
> and after that there is indeed an endless stream of:
>
> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> ide: failed opcode was: unknown
> hda: drive not ready for command
>
> Which eventially switches to
>
> hda: status error: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: status error: error=0x40 { LastFailedSense=0x04 }
> ide: failed opcode was: unknown
> hda: drive not ready for command
>
> However, it appears to be rather hard to debug, with nerolinux being some
> closed black box. Does anybody who knows nero know if there is some way to
> get debug information out of it to see what it tried to do?
>
> Can somebody try to bisect this?
>
> Linus
Unfortunately not me, Linus, sorry for my ignorance in those things.
But I will try rc7 and see whether this terrible bug is gone.
Regards
Uwe
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail?ac=OM.GX.GX003K11713T4783a
prev parent reply other threads:[~2007-02-02 13:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0701241847360.25027@woody.linux-foundation.org>
2007-01-26 18:11 ` 2.6.20-rc6: known unfixed regressions (part 2) Adrian Bunk
2007-01-26 19:04 ` Michal Piotrowski
2007-01-27 17:42 ` 2.6.20-rc6: known unfixed regressions (v2) " Adrian Bunk
2007-01-28 13:33 ` Uwe Bugla
2007-01-28 23:21 ` Andrew Morton
2007-02-02 12:58 ` Uwe Bugla
2007-01-29 6:26 ` Mike Galbraith
2007-01-29 6:48 ` Andrew Morton
2007-01-29 7:08 ` Mike Galbraith
2007-01-29 7:13 ` Linus Torvalds
2007-01-29 7:04 ` Linus Torvalds
2007-01-29 7:19 ` Mike Galbraith
2007-01-29 10:01 ` Mike Galbraith
2007-01-29 18:16 ` Mike Galbraith
2007-01-29 18:43 ` Linus Torvalds
2007-01-30 4:14 ` Mike Galbraith
2007-01-29 17:16 ` Mike Christie
2007-01-29 20:37 ` Mike Christie
2007-01-29 20:58 ` Linus Torvalds
2007-01-29 22:16 ` Linus Torvalds
2007-01-29 23:01 ` Linus Torvalds
2007-01-29 23:32 ` Linus Torvalds
2007-01-29 23:42 ` Mike Christie
2007-01-30 0:23 ` Linus Torvalds
2007-01-30 0:55 ` Mike Christie
2007-01-30 1:04 ` Mike Christie
2007-01-30 1:45 ` Linus Torvalds
2007-01-30 2:50 ` Mike Christie
2007-01-30 3:02 ` Mike Christie
2007-01-30 3:08 ` Andrew Morton
2007-01-30 2:18 ` Mike Christie
2007-01-30 3:33 ` Andrew Morton
2007-01-30 4:44 ` Linus Torvalds
2007-01-30 4:00 ` Mike Galbraith
2007-01-30 3:25 ` Mike Galbraith
2007-01-30 4:14 ` Jeff Garzik
2007-02-02 13:07 ` Uwe Bugla [this message]
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=20070202130736.185460@gmx.net \
--to=uwe.bugla@gmx.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=efault@gmx.de \
--cc=gd@spherenet.de \
--cc=jens.axboe@oracle.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=torvalds@linux-foundation.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).