Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter
Hi everyone,
I'm trying to run a Kernel 2.6 on the following machine:
Debian Sarge 3.1 with newest updates
gcc version 3.3.4 (Debian 1:3.3.4-13)
Dual Pentium III at 1000 MHz with 1 GByte RAM and Quantum ATLAS10K2-TY367J
Output from lspci:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 0000:00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 0000:00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 0000:00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 0000:00:07.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
0000:00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 Ultra3 SCSI Adapter (rev 01) 0000:00:08.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 Ultra3 SCSI Adapter (rev 01) 0000:00:0c.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
0000:02:0c.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 5598/6326 (rev 0b)
On boot it hangs with following messages:
sym0: <1010-33> rev 0x1 at pci 0000:00:08.1 irq 169
sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
sym0: handling phase mismatch from SCRIPTS.
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18j
Vendor: QUANTUM Model: ATLAS10K2-TY367J Rev: DDD6
Type: Direct-Access ANSI SCSI revision: 03
sym0:1:0: tagged command queuing enabled, command queue depth 16. scsi(0:0:1:0): Beginning Domain Validation
sym0:1: wide asynchronous.
sym0:1:0: ABORT operation started.
sym0:1:0: ABORT operation timed-out.
sym0:1:0: DEVICE RESET operation started.
sym0:1:0: DEVICE RESET operation timed-out.
sym0:1:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0: SCSI BUS operation completed.
At this point only a hard-reset helps.
With Kernel 2.4.26 and 2.4.27 it runs without any problems. I've tried almost every Kernel 2.6:
2.6.5 (vanilla), 2.6.9 (vanilla), 2.6.10-rc1-bk13, 2.6.10-rc1-mm2, 2.6.8 (Debian Sources), 2.6.9 (Debian Sources)
It seems that this problem is not new or not unknown, but I didn't find a solution yet.
Best Regards,
Thomas
Quoted 1 line · Thomas Babut
Dual Pentium III at 1000 MHz with 1 GByte RAM and Quantum ATLAS10K2-TY367J
...
Quoted 10 lines
sym0:1:0: ABORT operation started. sym0:1:0: ABORT operation timed-out. sym0:1:0: DEVICE RESET operation started. sym0:1:0: DEVICE RESET operation timed-out. sym0:1:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0: SCSI BUS operation completed.At this point only a hard-reset helps.
You need to upgrade to a more recent kernel, I had the same problem - it's a known issue with the hard disk's firmware. That particular version of the symbios driver added domain validation code which triggers the bug, the are work-arounds in the latest stable kernel.
George
Quoted 18 lines · George Glover
Quoted 1 line · Thomas Babut
Dual Pentium III at 1000 MHz with 1 GByte RAM and Quantum ATLAS10K2-TY367J
...
Quoted 10 lines
sym0:1:0: ABORT operation started. sym0:1:0: ABORT operation timed-out. sym0:1:0: DEVICE RESET operation started. sym0:1:0: DEVICE RESET operation timed-out. sym0:1:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0: SCSI BUS operation completed.At this point only a hard-reset helps.
Quoted 6 lines
You need to upgrade to a more recent kernel, I had the same problem - it's a known issue with the hard disk's firmware. That particular version of the symbios driver added domain validation code which triggers the bug, the are work-arounds in the latest stable kernel.
George
Which latest Kernel do you mean exactly? I've tried it with 2.6.9, 2.6.10-rc1-bk13, 2.6.10-rc1-mm2 with no success.
Thanks.
Regards,
Thomas