From: rob@osinvestor.com (Rob Radez)
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: 2.5.63/64 do not boot: loop in scsi_error
Date: Wed, 5 Mar 2003 23:15:34 -0500 [thread overview]
Message-ID: <20030306041534.GA15791@osinvestor.com> (raw)
In-Reply-To: <UTC200303060101.h2611cg08660.aeb@smtp.cwi.nl>
On Thu, Mar 06, 2003 at 02:01:38AM +0100, Andries.Brouwer@cwi.nl wrote:
> See that 2.5.64 came out - good. Time to send the next dev_t patch.
> Unfortunately 2.5.63 and 2.5.64 do not boot.
>
> A moment ago I looked at what goes wrong, and it turns out that
> scsi_error is activated
> [always a bad sign - I have never see it do any good, and
> often see it crash the machine]
> and an infinite loop occurs, leaving the machine rather dead.
>
> (Total of 1 commands require eh work; scsi_unjam_host; requesting sense;
> scsi_eh_done: result 0) - infinite repeat.
>
> Have no time tonight to make a patch, but I suppose the author of
> the 2.5.63 scsi_error.c changes knows what she did wrong.
Even with the patch to scsi_error.c floating around, I still get the
same hang/infinite loop after the information for my scsi cd-rom is
printed on both 2.5.63 and .64.
Regards,
Rob Radez
next prev parent reply other threads:[~2003-03-06 4:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 1:01 2.5.63/64 do not boot: loop in scsi_error Andries.Brouwer
2003-03-06 1:13 ` Patrick Mansfield
2003-03-06 1:22 ` Linus Torvalds
2003-03-06 4:15 ` Rob Radez [this message]
2003-03-06 6:39 Andries.Brouwer
2003-03-06 6:49 ` Mike Anderson
2003-03-06 7:59 ` Zwane Mwaikambo
2003-03-06 8:30 ` Mike Anderson
2003-03-06 8:35 ` Zwane Mwaikambo
2003-03-06 8:55 ` Mike Anderson
2003-03-06 9:00 ` Zwane Mwaikambo
2003-03-06 9:18 ` Mike Anderson
2003-03-06 9:58 ` Zwane Mwaikambo
2003-03-06 16:31 ` James Bottomley
2003-03-06 17:15 ` Zwane Mwaikambo
2003-03-06 17:21 ` James Bottomley
2003-03-06 17:39 ` Zwane Mwaikambo
2003-03-06 18:14 ` Mike Anderson
2003-03-06 17:24 ` Mike Anderson
2003-03-06 8:37 ` Mike Anderson
2003-03-06 9:22 Andries.Brouwer
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=20030306041534.GA15791@osinvestor.com \
--to=rob@osinvestor.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).