[4225] in linux-scsi channel archive
Re: SCSI Boot Problem with 2.0.34 SMP
daemon@ATHENA.MIT.EDU (Christopher B. Smith)
Fri Jun 26 06:01:13 1998
Date: Fri, 26 Jun 1998 04:12:54 -0400 (EDT)
From: "Christopher B. Smith" <cbsmith@clarke.envise.com>
To: Brendan Miller <brmiller@wco.com>
cc: "Frederick F. Gleason" <fredg@wava.com>, linux-scsi@vger.rutgers.edu,
linux-smp@rutgers.edu, necaise@home.com
In-Reply-To: <19980625231923.41595@xenon.kudzu.gammalink.com>
On Thu, 25 Jun 1998, Brendan Miller wrote:
> On Thu, Jun 25, 1998 at 08:23:11PM -0400, Frederick F. Gleason wrote:
> 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
>
> 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. :)
I've been having the exact same problem, and I'm not SMP. I've got a Dell
XPS D233, which of course means the 2940UW plus a NEC CD-ROM. The problem
for ME appears to be with the NEC CD-ROM. I'm getting basically EXACTLY
the same error (SCSISEQ and SEQADDR are different). I sent a message about
this problem to the aic7xxx maintainer, but I haven't heard anything back.
My guess is he's pouring over all the wonderful docs he got from Adaptect
recently. ;-)
Anyway, my system works fine w/2.0.33. So it's definitely in 2.0.34. It's
worth noting I have the same problem both pre and post patch.
--Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
