[4254] in linux-scsi channel archive
Re: Problems with aha2940UW in 2.0.34 and 2.0.35
daemon@ATHENA.MIT.EDU (Brendan Miller)
Tue Jun 30 12:01:11 1998
Date: Tue, 30 Jun 1998 08:55:38 -0700
From: Brendan Miller <brmiller@xenon.kudzu.gammalink.com>
To: Vidar Kroslid <vidarkr@ifi.uio.no>
Cc: linux-scsi@vger.rutgers.edu
Reply-To: Brendan Miller <brmiller@wco.com>
In-Reply-To: <199806300958.LAA25564@ifi.uio.no>; from Vidar Kroslid on Tue, Jun 30, 1998 at 11:58:25AM +0200
> In 2.0.34 I get this:
> (scsi0:0:-1:-1) Scanning channel for devices
> scsi: detected total
>
> later I get:
> Bad scbptr 255 during SELTO
> Referenced scb 255 not valid
This seems to happen to several people on the list (see other threads from
last two weeks). I think the answer I got was
+ The aic7xxx driver in the stock 2.0.34 is broke
+ The aic7xxx driver in the patch for 2.0.34 may also be broke
Since I run SMP, I am interested in the IO-APIC stuff in the development
kernels, and found that the aic7xxx driver in 2.1.105 didn't give me the
"Bad scbptr" message, but didn't always detect my drives either. (It
just pretended they weren't there!) I run 2.1.107 now, and everything
seems to be okay.
> Any suggestions on what is wrong? (And why does this work in 2.0.33 while
> 2.0.34 is broken?)
> Can I use the 2.0.33 scsi-drivers in 2.0.34+ in some way if this isn't fixed?
That was one thought I had. The aic7xxx driver in 2.0.33 seems to be fine.
(So does 2.0.33.) I ran 2.0.33 SMP with its aic7xxx driver for several
days and also didn't have any problems.
I really don't know what the plan for the aic7xxx driver in the near future
is with regard to addressing this problem. I have had several helpful folks
suggest certain things, and I eventually got up and running with both 2.0.33
and 2.1.107, but as near as I can tell 2.0.34 is out.
Brendan Miller
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
