From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: AIC7xxx on 2.6.18 Date: Tue, 30 Jan 2007 09:57:46 -0800 Message-ID: <20070130095746.8c2e7db9.akpm@osdl.org> References: <20070128194620.GA6358@animx.eu.org> <20070128162408.9fffb6de.akpm@osdl.org> <20070130121820.GA11843@animx.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from smtp.osdl.org ([65.172.181.24]:40369 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965655AbXA3R6E (ORCPT ); Tue, 30 Jan 2007 12:58:04 -0500 In-Reply-To: <20070130121820.GA11843@animx.eu.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Wakko Warner Cc: linux-scsi@vger.kernel.org On Tue, 30 Jan 2007 07:18:20 -0500 Wakko Warner wrote: > NOTE: I am not on the linux-scsi list, keep me in CC. > > Andrew Morton wrote: > > On Sun, 28 Jan 2007 14:46:20 -0500 > > Wakko Warner wrote: > > > > > I have 2 machine that oops with these cards. > > > > > > 1) The bios has the option to enable/disable option roms on individual PCI > > > slots. I have an AHA-39160 and an AHA-2940U/UW (dual channel). If I > > > disable option roms, the driver oopses when accessing the 2nd card. > > > > > > I can get the oops if really needed as I don't like rebooting this machine. > > > > > > 2) I have an AHA-39160 with Apple/Mac firmware. When attempting to use it > > > on a PC, the driver oopses presumably because the card wasn't initialized or > > > something. I realize this is probably not a supported configuration, but I > > > don't believe that it should be oopsing. > > > > > > I can get the oops for this one if it'll help. > > > > Yes, getting the oops traces will help, thanks. And confirmation on a more > > recent kernel would be good. > > I tested with a 2.6.20-rc6 kernel and the MAC 39160 card. There was no oops > and I was able to access the 2 disks. This was on a different PC though. > I'll try it again on the original PC. Thanks. > Should I try 2.6.19 as well? There's not a lot of point in doing so. If/when we come up with a 2.6.20-rc6 fix we'll know whether it is applicable to 2.6.19.x.