[7620] in linux-scsi channel archive
Re: SCSI Broken after 2.2.10 for Adaptec 7xxx ???
daemon@ATHENA.MIT.EDU (Steven N. Hirsch)
Sun Dec 5 20:38:42 1999
Date: Sun, 5 Dec 1999 20:27:13 -0500 (EST)
From: "Steven N. Hirsch" <shirsch@adelphia.net>
To: "George R. Kasica" <georgek@netwrx1.com>
Cc: linux-scsi@vger.rutgers.edu, linux-kernel@vger.rutgers.edu
In-Reply-To: <si4l4sk2i6m3eickgp7178nfqhersnerm2@4ax.com>
Message-ID: <Pine.LNX.4.10.9912052021430.6503-100000@pii.fast.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Sun, 5 Dec 1999, George R. Kasica wrote:
> Hello:
>
> I think something got broken after 2.2.10 in the SCSI code for the
> Adaptec 7XXX adapters....Below is my boot up info for 2.2.10 (last one
> that appears to work) and then 2.2.11, 2.2.12 and 2.2.13 all fail
> similarly. They were complied with the same options using
> Dec 5 09:50:55 eagle kernel: scsi : 1 host.
> Dec 5 09:50:55 eagle kernel: Vendor: SEAGATE Model: ST32550N
> Rev:0021
> Dec 5 09:50:55 eagle kernel: Type: Direct-Access
> ANSISCSI revision: 02
> Dec 5 09:50:55 eagle kernel: Detected scsi disk sda at scsi0, channel
>
> Under 2.2.11,2.2.12 or 2.2.13 I get the following error:
> --------------------------------------------------------
> scsi: Aborting Command due to timeout pid 11,scsi0,channel 0,id3,lun 0
> Testing Unit Ready 00 00 00 00 00
>
> and it just keeps repeating and the system will not boot.
I saw the same problem with an older Seagate drive here. A Barracuda
ST15150W just would not work on a 7890-based controller under any of
Doug's newer drivers. If I reverted back to the driver of circa-2.2.9 (I
think it was aic7xxx 5.1.10) it was just fine. This only occurred on a
7890 controller. The drive's previous home was in an older box with 2940A
controller (7880 chipset), where it worked (and continues to work) fine.
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
