Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267935AbTCFIwC>; Thu, 6 Mar 2003 03:52:02 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267927AbTCFIwB>; Thu, 6 Mar 2003 03:52:01 -0500
Received: from modemcable092.130-200-24.mtl.mc.videotron.ca ([24.200.130.92]:23887
	"EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP
	id <S267368AbTCFIwA>; Thu, 6 Mar 2003 03:52:00 -0500
Date: Thu, 6 Mar 2003 04:00:20 -0500 (EST)
From: Zwane Mwaikambo <zwane@linuxpower.ca>
X-X-Sender: zwane@montezuma.mastecende.com
To: Mike Anderson <andmike@us.ibm.com>
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
In-Reply-To: <20030306085506.GB2222@beaverton.ibm.com>
Message-ID: <Pine.LNX.4.50.0303060354550.25282-100000@montezuma.mastecende.com>
References: <UTC200303060639.h266dIo22884.aeb@smtp.cwi.nl>
 <20030306064921.GA1425@beaverton.ibm.com>
 <Pine.LNX.4.50.0303060256200.25282-100000@montezuma.mastecende.com>
 <20030306083054.GB1503@beaverton.ibm.com>
 <Pine.LNX.4.50.0303060331030.25282-100000@montezuma.mastecende.com>
 <20030306085506.GB2222@beaverton.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1235
Lines: 27

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

	Zwane
-- 
function.linuxpower.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/