[3064] in linux-scsi channel archive
Linux 2.0.33 crashes with certain 2940 options
daemon@ATHENA.MIT.EDU (Kevin Chu)
Sat Jan 10 04:39:31 1998
Date: Sat, 10 Jan 1998 01:29:05 -0800
From: Kevin Chu <kevin@portal.ca>
To: linux-scsi@vger.rutgers.edu
I am running a Red Hat 4.2 system. The out-of-the-box 2.0.30 kernel
runs fine with my Adaptec 2940. I recently compiled a new 2.0.33
kernel, and encountered some problems. One problem is the one described
by Ulrich Windl on Thu, 18 Dec 1997:
> scsi0: Referenced SCB 255 not valid during SELTO.
> SCSISEQ = 0x5a SEQADDR = 0x4 SSTAT0 = 0x15 SSTAT1 = 0x8a
(The numbers might be a little different on my system.) After this
error, the bus resets and times out (15 s), and then my system starts
running again. A more serious error is:
> scsi0: Unexpected busfree, LASTPHASE = 0x80, SEQADDR = 0x124
after which my system crashes dead. The system runs for minutes to
hours before it crashes.
After reading many HOWTOs and other sources of information, I came up
with nothing. I looked at the driver's source code (aic7xxx.c) but I
don't know enough about SCSI or these chips to figure out what's going
on. Since my 2.0.30 kernel has been running fine since the release of
Red Hat 4.2, I decided to compile a new 2.0.33 kernel with the same SCSI
options as the 2.0.30 kernel. This new 2.0.33 kernel has been running
fine for over twelve hours now with no crashes. Here are the options
used:
=============== the working 2.0.30 kernel
Adaptec AIC7xxx driver version: 4.0/3.2/4.0
Compile Options:
AIC7XXX_RESET_DELAY : 15
AIC7XXX_TWIN_SUPPORT : Enabled
AIC7XXX_TAGGED_QUEUEING: Disabled
AIC7XXX_PAGE_ENABLE : Disabled
AIC7XXX_PROC_STATS : Disabled
Adapter Configuration:
SCSI Adapter: AHA-2940
(AIC-787x chipset)
Host Bus: Single
Base IO: 0xe000
IRQ: 11
SCBs: Used 4, HW 16, Page 16
Interrupts: 8701
Serial EEPROM: True
Extended Translation: Disabled
SCSI Bus Reset: Enabled
Ultra SCSI: Disabled
Target Disconnect: Enabled
=============== the crashing 2.0.33 kernel
Adaptec AIC7xxx driver version: 4.1.1/3.2.1
Compile Options:
AIC7XXX_RESET_DELAY : 15
AIC7XXX_TAGGED_QUEUEING: Enabled
AIC7XXX_PAGE_ENABLE : Enabled
AIC7XXX_PROC_STATS : Disabled
Adapter Configuration:
SCSI Adapter: Adaptec AHA-294X SCSI host adapter
(AIC-787x chipset)
Host Bus: Single
Base IO: 0xe000
Base IO Memory: 0xfb000000
IRQ: 11
SCBs: Used 10, HW 16, Page 255
Interrupts: 2469
Serial EEPROM: True
Extended Translation: Disabled
SCSI Bus Reset: Enabled
Ultra SCSI: Disabled
Disconnect Enable Flags: 0xff
=============== the working 2.0.33 kernel (2.0.30 options)
Adaptec AIC7xxx driver version: 4.1.1/3.2.1
Compile Options:
AIC7XXX_RESET_DELAY : 15
AIC7XXX_TAGGED_QUEUEING: Disabled
AIC7XXX_PAGE_ENABLE : Disabled
AIC7XXX_PROC_STATS : Disabled
Adapter Configuration:
SCSI Adapter: Adaptec AHA-294X SCSI host adapter
(AIC-787x chipset)
Host Bus: Single
Base IO: 0xe000
Base IO Memory: 0xfb000000
IRQ: 11
SCBs: Used 4, HW 16, Page 16
Interrupts: 49196
Serial EEPROM: True
Extended Translation: Disabled
SCSI Bus Reset: Enabled
Ultra SCSI: Disabled
Disconnect Enable Flags: 0xff
=============== end of /proc listings
Note the "SCBs" line. What does it mean?
The kernel-configuration documentation leads me to believe that I should
be able to use tagged queueing and page enable with my 2940, and the
documentation even makes it sound like these two options are better than
sliced bread. However, enabling the two options causes problems on my
system. The SCSI devices connected are:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300N
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: QUANTUM Model: LP240S GM240S01X Rev: 6.4
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: TOSHIBA Model: CD-ROM XM-4101TA Rev: 0064
Type: CD-ROM ANSI SCSI revision: 02
and the system is a Pentium 133 MHz with 32 MB of RAM. 2940 BIOS info
is: AHA-2940 BIOS 1.16 (C) 1995 Adaptec.
Can anyone tell me:
1) If I can turn on tagged queueing and page enable?
2) If yes, why do I get these errors?
3) If no, why?
4) If no, will my system run stably the way it is now?
Kevin
--
Kevin Chu
Mail: kevin@portal.ca
URL: http://www.geocities.com/SiliconValley/Horizon/6871/