[4223] in linux-scsi channel archive
Re: SCSI Boot Problem with 2.0.34 SMP
daemon@ATHENA.MIT.EDU (Brendan Miller)
Fri Jun 26 03:46:40 1998
Date: Thu, 25 Jun 1998 23:19:23 -0700
From: Brendan Miller <brmiller@xenon.kudzu.gammalink.com>
To: "Frederick F. Gleason" <fredg@wava.com>
Cc: linux-scsi@vger.rutgers.edu, linux-smp@rutgers.edu, necaise@home.com
Reply-To: Brendan Miller <brmiller@wco.com>
In-Reply-To: <Pine.LNX.3.96.980625200853.4462A-100000@caspian.wava.com>; from Frederick F. Gleason on Thu, Jun 25, 1998 at 08:23:11PM -0400
On Thu, Jun 25, 1998 at 08:23:11PM -0400, Frederick F. Gleason wrote:
> Having problems booting 2.0.34 compiled for SMP. Keep getting the
> following at boot-time:
>
> SCSI Host 0 Abort (pid 4) timed out - resetting
> SCSI bus is being reset for host 0 channel 0
> SCSI Host 0 Channel 0 reset (pid 4) timed out - trying harder
> SCSI bus is being reset for host 0 channel 0
> (scsi0:-1:-1:-1) Bad scbptr 255 during SELTO Referenced SCB 255 not valid
> SCSISEQ=0x0 SEQADDR=0x0 SSTAT0=0x5 STAT1=0x88
I was reflecting on this and my own dilemma (see thread regarding BusLogic
BT-958 AND Adaptec 2940), and noticed similar messages from my boot logs:
(scsi1:0:-1:-1) Scanning channel for devices.
(scsi1:-1:-1:-1) Bad scbptr 255 during SELTO.
(scsi1:-1:-1:-1) Referenced SCB 255 not valid duri ng SELTO.
SCSISEQ = 0x12 SEQADDR = 0xb SSTAT0 = 0x15 SSTAT1 = 0x88
> There's lots more in the same vein, all of it seeming to be related to an
> invalid scb of 255. The machine was quite stable with 2.0.33 SMP, and
> also boots correctly with 2.0.34 UP.
This, too, was with a 2.0.34 SMP kernel. I have gotten similar results
with 2.1.105 SMP. I can't remember how 2.0.34 UP faired, but I just
built and booted 2.0.33 SMP, and everything is fine:
aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PCI 11
aic7xxx: Warning - detected auto-termination. Please verify driver
detected settings and use manual termination if necessary.
aic7xxx: BIOS enabled, IO Port 0x8000, IO Mem 0xe1000000, IRQ 12, Revision B
aic7xxx: Single Channel, SCSI ID 7, 16/16 SCBs, QFull 16, QMask 0x1f
scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.1.1/3.2.1
scsi : 2 hosts.
scsi1: Scanning channel A for devices.
Vendor: HP Model: C3725S Rev: 6039
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi1, channel 0, id 1, lun 0
Vendor: IOMEGA Model: ZIP 100 Rev: D.09
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sde at scsi1, channel 0, id 5, lun 0
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 4194058 [2047 MB] [2.0 GB]
sdd: sdd1 sdd2 sdd3
SCSI device sde: hdwr sector= 512 bytes. Sectors= 196608 [96 MB] [0.1 GB]
sde: Write Protect is off
sde: sde4
So I wonder if there's something about 2.0.34, aic7xxx, and SMP? I had used
the aic7xxx patch recommended for 2.0.34 also, but I still got the scbptr
errors.
Maybe we're on to something? Since 2.0.33 SMP works with my aic7xxx, I
tempted now to think that my cabling and termination are okay. :)
Brendan Miller
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
