From: Andrew Morton <akpm@osdl.org>
To: Mike Galbraith <efault@gmx.de>
Cc: nickpiggin@yahoo.com.au, linux-ide@vger.kernel.org,
petero2@telia.com, linux-kernel@vger.kernel.org,
livio@eecg.toronto.edu, Adrian Bunk <bunk@stusta.de>,
B.Zolnierkiewicz@elka.pw.edu.pl, linuxppc-dev@ozlabs.org,
paulus@samba.org, anton@samba.org, gd@spherenet.de,
cijoml@volny.cz, ttb@tentacle.dhs.org, rml@novell.com,
Uwe Bugla <uwe.bugla@gmx.de>,
torvalds@linux-foundation.org, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.6.20-rc6: known unfixed regressions (v2) (part 2)
Date: Sun, 28 Jan 2007 22:48:34 -0800 [thread overview]
Message-ID: <20070128224834.37482553.akpm@osdl.org> (raw)
In-Reply-To: <1170051963.6454.7.camel@Homer.simpson.net>
On Mon, 29 Jan 2007 07:26:03 +0100
Mike Galbraith <efault@gmx.de> 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
>
> endlessly.
Do you have time to bisect it?
next prev parent reply other threads:[~2007-01-29 6:48 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 [this message]
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
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=20070128224834.37482553.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=bunk@stusta.de \
--cc=cijoml@volny.cz \
--cc=efault@gmx.de \
--cc=gd@spherenet.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=livio@eecg.toronto.edu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulus@samba.org \
--cc=petero2@telia.com \
--cc=rml@novell.com \
--cc=torvalds@linux-foundation.org \
--cc=ttb@tentacle.dhs.org \
--cc=uwe.bugla@gmx.de \
/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).