From: Mike Anderson <andmike@us.ibm.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Andries.Brouwer@cwi.nl, torvalds@transmeta.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.5.63/64 do not boot: loop in scsi_error
Date: Thu, 6 Mar 2003 01:18:24 -0800 [thread overview]
Message-ID: <20030306091824.GA2577@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303060354550.25282-100000@montezuma.mastecende.com>
Zwane Mwaikambo [zwane@linuxpower.ca] wrote:
> On Thu, 6 Mar 2003, Mike Anderson wrote:
>
> > Zwane Mwaikambo [zwane@linuxpower.ca] wrote:
> > > I'm not concerned about that, that was peripheral damage from another
> > > patch (affected irq handling), the difference being is that with 2.5.62 it boots
> > > after printing those errors a couple of times, but with 2.5.63 it doesn't.
> >
> > Ok I will keep looking at this , I believe I have a PLEXTOR CD in the
> > lab I will add this to my qlogic isp bus and see if I can get the error
> > to show up. I am running cd drives on the other adapters and I am not
> > seeing a problem.
>
> My apologies, i think i wasn't being too clear. You won't be able to
> replicate that exact error by default, i got it because i killed
> interrupt routing/handling on the interrupt controllers servicing the bus
> on which the scsi controller is on. The errors generated by the SCSI layer
> in turn kill the box in 2.5.63 whilst only spewing those errors and
> continuing boot with 2.5.62
Would it be possible for you to send me a console output with
scsi_logging=1 so that I can narrow down the failure case.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-03-06 9:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 6:39 2.5.63/64 do not boot: loop in scsi_error 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 9:22 Andries.Brouwer
2003-03-06 1:01 Andries.Brouwer
2003-03-06 1:13 ` Patrick Mansfield
2003-03-06 1:22 ` Linus Torvalds
2003-03-06 4:15 ` Rob Radez
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=20030306091824.GA2577@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zwane@linuxpower.ca \
/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