From: Scott McDermott <vaxerdec@frontiernet.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Dillow <dave@thedillows.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21: kernel BUG at ide-iops.c:1262!
Date: Wed, 25 Jun 2003 18:47:23 -0400 [thread overview]
Message-ID: <20030625184723.L9583@newbox.localdomain> (raw)
In-Reply-To: <1056542418.2460.22.camel@dhcp22.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Wed, Jun 25, 2003 at 01:00:18PM +0100
Alan Cox on Wed 25/06 13:00 +0100:
> Its a known problem. There are two approaches. Either
> rewrite the ide scsi reset code to use ide_abort
> infrastructure or switch ide-scsi back to the old
> abort/reset code not new_eh and use SCSI_RESET_PUNT so
> that the recovery is all handled by the ide layer.
>
> For 2.4 the latter may be the best approach, for 2.5 it
> has to use new_eh
is this what
o First crack at fixing the ide reset oopses (me)
tries to fix?
The CDRW devices that have problems with Test Unit Ready
during finalization (like the GCC-4240N) are broken and this
won't fix that problem, but the fix you're talking about
will stop the kernel from crashing when it happens, do I
have that right?
next prev parent reply other threads:[~2003-06-25 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 22:19 David Dillow
2003-06-25 0:48 ` Scott McDermott
2003-06-25 3:54 ` David Dillow
2003-06-25 12:00 ` Alan Cox
2003-06-25 22:47 ` Scott McDermott [this message]
2003-06-25 22:49 ` Alan Cox
[not found] ` <1056557323.1444.4.camel@dhcp22.swansea.linux.org.uk>
2003-06-26 3:17 ` David Dillow
2003-06-26 21:34 ` Alan Cox
2003-06-27 2:58 ` David Dillow
2003-06-25 7:42 ` Roland Mas
2003-06-25 21:20 ` Adrian Bunk
2003-06-25 21:37 ` Scott McDermott
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=20030625184723.L9583@newbox.localdomain \
--to=vaxerdec@frontiernet.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@thedillows.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
all inboxes | Powered by JetHome®