Skip to contentSkip to conversation

Deadlock: Linux-2.2.18, sym53c8xx, Compaq ProLiant, HP Ultrium

DISCUSSION Andreas Haumer 2 participants 4 messages Dec 19, 2001 – Dec 20, 2001

lore
Share & tools
lore
#0 lore raw

Hi!

We experience a problem with a HP Ultrium LTO drive connected to a Compaq ProLiant ML380 server: in the last 6 months we had two deadlocks of the machine which seem to be related to the sym53c8xx driver.

What happens seems to be as follows:

*) From monday to friday, once a day an amanda backup process
starts and dumps about 70GB of data to the tape.

*) this works quite fine, but twice in the last 6 months we
got the following tape error at the start of the backup:

[...]

Dec 10 15:00:00 server kernel: sym53c1510D-0-<3,*>: FAST-20 WIDE SCSI
40.0 MB/s (50 ns, offset 15)
Dec 10 15:00:01 server kernel: st0: Error with sense data: Info
fld=0x8000, Current st09:00: sense key Hardware Error
Dec 10 15:00:01 server kernel: Additional sense indicates Internal

target failure
[...]

After that, the amanda process hangs in state "D" and cannot be killed anymore. The machine itself is still working.
This _seems_ to be the indication of an error of the HP Ultrium itself, though the drive works quite fine otherwise...

*) In order to unlock the hanging amanda process I tried to
remove the SCSI drive from the driver:

echo "scsi remove-single-device" > /proc/scsi/scsi

This did work well: the hanging amanda process terminated fine after that.

*) Next I tried to re-scan the SCSI bus to make the Ultrium
drive available again for a new backup:

echo "scsi add-single-device 0 0 3 0" > /proc/scsi/scsi

Result: the machine completely deadlocked. No log-message, no ping (the server currently runs without monitor and keyboard connected...)
We had to power-switch the machine to get it back... :-(

I now have the following problems/questions:

a) Does anyone have any experience with such an HP Ultrium drive? (good/bad?)

b) Does the st0 error message indicate it should be replaced?

c) Is there a bug in the sym53c8xx driver which makes the amanda process hang uninterruptable when this error occurs? It is not nice to be forced to reboot the machine just because the SCSI tape drive reported some error... :-(( After all, this is not a windows server, and there are 40 workstations which get fileservice from this server!

d) Is there a bug in the driver which deadlocks the server as soon as someone does a remove/add on the SCSI bus? We can live without this feature, but I don't think a documented function should deadlock the kernel...

The Ultrium hardware error is not reproducable at will. It just happens every now and then.
Next thing I will try is to use a different SCSI controller (Adaptec 29160 or the like) to see if the hanging process occurs with a different SCSI driver, too.

Following is some information about the server:

Hardware: Compaq ProLiant ML370, Intel PIII/933, 512MB RAM, Compaq Smart Array 5302/32 RAID Controller with about 80GB of disk-capacity, 3Com 3c985 1000BaseSX NIC

Software: Linux-2.2.18 with newer acenic driver (for the 3Com NIC)

Some information from the running system:

root@server {533} # free
total used free shared buffers
cached
Mem: 517644 439092 78552 47404 166716
178744
-/+ buffers/cache: 93632 424012
Swap: 1052592 18400 1034192

root@server {534} # lspci -v
00:00.0 Host bridge: Relience Computer CNB20HE (rev 05)
Flags: bus master, medium devsel, latency 64

00:00.1 Host bridge: Relience Computer CNB20HE (rev 05)
Flags: bus master, medium devsel, latency 64

00:01.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR):
Unknown device 000a (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b143
Flags: bus master, medium devsel, latency 255, IRQ 10 I/O ports at 2000
Memory at c6cffc00 (32-bit, non-prefetchable) Memory at c6cfe000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2

00:01.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR):
Unknown device 000a (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b143
Flags: bus master, medium devsel, latency 255, IRQ 11 I/O ports at 2400
Memory at c6cfdc00 (32-bit, non-prefetchable) Memory at c6cfc000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2

00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Compaq Computer Corporation: Unknown device b134
Flags: bus master, medium devsel, latency 64, IRQ 15 Memory at c6cfb000 (32-bit, non-prefetchable) I/O ports at 2800
Memory at c6b00000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2

00:03.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc: Unknown device 4756
Flags: bus master, stepping, medium devsel, latency 64 Memory at c5000000 (32-bit, prefetchable)
I/O ports at 2c00
Memory at c6aff000 (32-bit, non-prefetchable)
Capabilities: [5c] Power Management version 1

00:04.0 System peripheral: Compaq Computer Corporation: Unknown device a0f0
Subsystem: Compaq Computer Corporation: Unknown device b0f3
Flags: medium devsel
I/O ports at 1800
Memory at c6afef00 (32-bit, non-prefetchable)

00:0f.0 ISA bridge: Relience Computer: Unknown device 0200 (rev 51)
Subsystem: Relience Computer: Unknown device 0200
Flags: bus master, medium devsel, latency 0

00:0f.1 IDE interface: Relience Computer: Unknown device 0211 (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at 3000

03:03.0 RAID bus controller: Compaq Computer Corporation: Unknown device b060 (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device 4070
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 5 Memory at c6fc0000 (32-bit, non-prefetchable) Memory at c6e00000 (32-bit, non-prefetchable) I/O ports at 4000
Capabilities: [f0] Power Management version 2
Capabilities: [f8] Vital Product Data

03:06.0 Ethernet controller: 3Com Corporation 3c985 1000BaseSX (rev
01)
Subsystem: Unknown device 9850:0001
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 15 Memory at c6dfc000 (32-bit, non-prefetchable)

root@server {535} # cat /proc/cciss/cciss0
cciss0: Compaq Smart Array 5300 Controller
Board ID: 40700e11
Firmware Version: 1.62
Memory Address: e0812000
IRQ: 0x5
Logical drives: 2
Current Q depth: 0
Current # commands on controller 0 Max Q depth since init: 1
Max # commands on controller since init: 128 Max SG entries since init: 22

cciss/c0d0: blksz=512 nr_blocks=17764320
cciss/c0d1: blksz=512 nr_blocks=142261440
nr_allocs = 11831533
nr_frees = 11831533

root@server {536} # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: HP Model: Ultrium 1-SCSI Rev: N11D
Type: Sequential-Access ANSI SCSI revision: 03

root@server {537} # cat /proc/scsi/sym53c8xx/0 General information:
Chip sym53c1510D, device id 0xa, revision id 0x2 On PCI bus 0, device 1, function 0, IRQ 10 Synchronous period factor 10, max commands per lun 32

root@server {538} # cat /proc/scsi/sym53c8xx/1 General information:
Chip sym53c1510D, device id 0xa, revision id 0x2 On PCI bus 0, device 1, function 1, IRQ 11 Synchronous period factor 10, max commands per lun 32

root@server {539} # cat /proc/interrupts
CPU0

  0:   76904808          XT-PIC  timer
  1:          2          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:    5231002          XT-PIC  serial
  5:   11578119          XT-PIC  cciss0
  8:          2          XT-PIC  rtc
 10:   13412657          XT-PIC  sym53c8xx
 11:        450          XT-PIC  sym53c8xx
 13:          1          XT-PIC  fpu
 15:   36100885          XT-PIC  eth0
NMI:          0
ERR:          0

root@server {540} # uname -a
Linux server 2.2.18 #1 SMP Sun May 27 23:14:43 CEST 2001 i686 unknown

root@server {541} # lsmod
Module Size Used by
sym53c8xx 56592 0

af_packet               6528   1  (autoclean)
nfsd                  184416  16  (autoclean)
nfs                    75872   1  (autoclean)
lockd                  47344   1  (autoclean) [nfsd nfs]
sunrpc                 63376   1  (autoclean) [nfsd nfs lockd]
acenic                125744   1  (autoclean)
softdog                 1584   1  (autoclean)
st                     25424   0
scsi_mod               55504   2  [sym53c8xx st]
cciss                  17552   9
ext2                   42032   7

These are the sym53c8xx driver's boot-messages:
[...]
sym53c8xx: at PCI bus 0, device 1, function 0
sym53c8xx: 53c1510D detected
sym53c8xx: at PCI bus 0, device 1, function 1
sym53c8xx: 53c1510D detected
sym53c1510D-0: rev 0x2 on pci bus 0 device 1 function 0 irq 10
sym53c1510D-0: ID 7, Fast-40, Parity Checking
sym53c1510D-1: rev 0x2 on pci bus 0 device 1 function 1 irq 11
sym53c1510D-1: ID 7, Fast-40, Parity Checking
scsi0 : sym53c8xx-1.7.1-20000726
scsi1 : sym53c8xx-1.7.1-20000726
scsi : 2 hosts.
Vendor: HP Model: Ultrium 1-SCSI Rev: N11D
Type: Sequential-Access ANSI SCSI revision: 03
Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0 [...]

Any help is appreciated!
Many thanks in advance!

- andreas

Signature · 4 lines
Andreas Haumer                     | mailto:[email protected]
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
#1 lore raw
Quoted 12 lines · Andreas Haumer

Hi!

We experience a problem with a HP Ultrium LTO drive connected to a Compaq ProLiant ML380 server: in the last 6 months we had two deadlocks of the machine which seem to be related to the sym53c8xx driver.

What happens seems to be as follows:

*) From monday to friday, once a day an amanda backup process
starts and dumps about 70GB of data to the tape.

Quoted 6 lines

*) this works quite fine, but twice in the last 6 months we
got the following tape error at the start of the backup:

[...]

Dec 10 15:00:00 server kernel: sym53c1510D-0-<3,*>: FAST-20 WIDE SCSI

40.0 MB/s (50 ns, offset 15)

This messages indicates teh synchronous parameters that have been negotiated with the device.

Quoted 4 lines
Dec 10 15:00:01 server kernel: st0: Error with sense data: Info
fld=0x8000, Current st09:00: sense key Hardware Error
Dec 10 15:00:01 server kernel: Additional sense indicates Internal

target failure

This one is the result of a REQUEST SENSE performed due probably to a CHECK condition SCSI status reported by the device. It is not a SCSI transport problem. The device just reports an error to the application client. This is not a normal situation but happens very often.

Quoted 8 lines

[...]

After that, the amanda process hangs in state "D" and cannot be killed anymore. The machine itself is still working.
This _seems_ to be the indication of an error of the HP Ultrium itself, though the drive works quite fine otherwise...

The 'D' states indicates that the process is waiting for something without being interruptible. This may be due to it not having been waken up on the IO error. The sym53c8xx driver did its work by performing the REQUEST SENSE, but something in upper layer seem not to complete the IO.

Quoted 7 lines

*) In order to unlock the hanging amanda process I tried to
remove the SCSI drive from the driver:

echo "scsi remove-single-device" > /proc/scsi/scsi

This did work well: the hanging amanda process terminated fine after that.

Hmmm... You seems brave. :-)

Quoted 9 lines

*) Next I tried to re-scan the SCSI bus to make the Ultrium
drive available again for a new backup:

echo "scsi add-single-device 0 0 3 0" > /proc/scsi/scsi

Result: the machine completely deadlocked. No log-message, no ping (the server currently runs without monitor and keyboard connected...)
We had to power-switch the machine to get it back... :-(

But certainly too much. :)

To be serious, I cannot explain what happenned here. But something was messy since the hang-up, so you should only expect some luck here to help you.

Quoted 4 lines

I now have the following problems/questions:

a) Does anyone have any experience with such an HP Ultrium drive? (good/bad?)

None, here.

Quoted 1 line

b) Does the st0 error message indicate it should be replaced?

Probably not. But it is very poor an information about the real issue.

Quoted 2 lines

c) Is there a bug in the sym53c8xx driver which makes the amanda process hang uninterruptable when this error occurs?

Not known. But possible, even if in my opinion, the driver is not at fault.

Quoted 2 lines

It is not nice to be forced to reboot the machine just because the SCSI tape drive reported some error... :-((

Agreed.

Quoted 7 lines

After all, this is not a windows server, and there are 40 workstations which get fileservice from this server!

d) Is there a bug in the driver which deadlocks the server as soon as someone does a remove/add on the SCSI bus? We can live without this feature, but I don't think a documented function should deadlock the kernel...

There are probably still bugs in the driver, but none are intentionnal, beleive me.

Quoted 5 lines

The Ultrium hardware error is not reproducable at will. It just happens every now and then.
Next thing I will try is to use a different SCSI controller (Adaptec 29160 or the like) to see if the hanging process occurs with a different SCSI driver, too.

This is indeed something to try.
I am very interested in the result.

Gérard.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Quoted 199 lines

Following is some information about the server:

Hardware: Compaq ProLiant ML370, Intel PIII/933, 512MB RAM, Compaq Smart Array 5302/32 RAID Controller with about 80GB of disk-capacity, 3Com 3c985 1000BaseSX NIC

Software: Linux-2.2.18 with newer acenic driver (for the 3Com NIC)

Some information from the running system:

root@server {533} # free
total used free shared buffers
cached
Mem: 517644 439092 78552 47404 166716
178744
-/+ buffers/cache: 93632 424012
Swap: 1052592 18400 1034192

root@server {534} # lspci -v
00:00.0 Host bridge: Relience Computer CNB20HE (rev 05)
Flags: bus master, medium devsel, latency 64

00:00.1 Host bridge: Relience Computer CNB20HE (rev 05)
Flags: bus master, medium devsel, latency 64

00:01.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR):
Unknown device 000a (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b143
Flags: bus master, medium devsel, latency 255, IRQ 10 I/O ports at 2000
Memory at c6cffc00 (32-bit, non-prefetchable) Memory at c6cfe000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2

00:01.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR):
Unknown device 000a (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b143
Flags: bus master, medium devsel, latency 255, IRQ 11 I/O ports at 2400
Memory at c6cfdc00 (32-bit, non-prefetchable) Memory at c6cfc000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2

00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Compaq Computer Corporation: Unknown device b134
Flags: bus master, medium devsel, latency 64, IRQ 15 Memory at c6cfb000 (32-bit, non-prefetchable) I/O ports at 2800
Memory at c6b00000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2

00:03.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc: Unknown device 4756
Flags: bus master, stepping, medium devsel, latency 64 Memory at c5000000 (32-bit, prefetchable)
I/O ports at 2c00
Memory at c6aff000 (32-bit, non-prefetchable)
Capabilities: [5c] Power Management version 1

00:04.0 System peripheral: Compaq Computer Corporation: Unknown device a0f0
Subsystem: Compaq Computer Corporation: Unknown device b0f3
Flags: medium devsel
I/O ports at 1800
Memory at c6afef00 (32-bit, non-prefetchable)

00:0f.0 ISA bridge: Relience Computer: Unknown device 0200 (rev 51)
Subsystem: Relience Computer: Unknown device 0200
Flags: bus master, medium devsel, latency 0

00:0f.1 IDE interface: Relience Computer: Unknown device 0211 (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at 3000

03:03.0 RAID bus controller: Compaq Computer Corporation: Unknown device b060 (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device 4070
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 5 Memory at c6fc0000 (32-bit, non-prefetchable) Memory at c6e00000 (32-bit, non-prefetchable) I/O ports at 4000
Capabilities: [f0] Power Management version 2
Capabilities: [f8] Vital Product Data

03:06.0 Ethernet controller: 3Com Corporation 3c985 1000BaseSX (rev
01)
Subsystem: Unknown device 9850:0001
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 15 Memory at c6dfc000 (32-bit, non-prefetchable)

root@server {535} # cat /proc/cciss/cciss0
cciss0: Compaq Smart Array 5300 Controller
Board ID: 40700e11
Firmware Version: 1.62
Memory Address: e0812000
IRQ: 0x5
Logical drives: 2
Current Q depth: 0
Current # commands on controller 0 Max Q depth since init: 1
Max # commands on controller since init: 128 Max SG entries since init: 22

cciss/c0d0: blksz=512 nr_blocks=17764320
cciss/c0d1: blksz=512 nr_blocks=142261440
nr_allocs = 11831533
nr_frees = 11831533

root@server {536} # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: HP Model: Ultrium 1-SCSI Rev: N11D
Type: Sequential-Access ANSI SCSI revision: 03

root@server {537} # cat /proc/scsi/sym53c8xx/0 General information:
Chip sym53c1510D, device id 0xa, revision id 0x2 On PCI bus 0, device 1, function 0, IRQ 10 Synchronous period factor 10, max commands per lun 32

root@server {538} # cat /proc/scsi/sym53c8xx/1 General information:
Chip sym53c1510D, device id 0xa, revision id 0x2 On PCI bus 0, device 1, function 1, IRQ 11 Synchronous period factor 10, max commands per lun 32

root@server {539} # cat /proc/interrupts
CPU0

  0:   76904808          XT-PIC  timer
  1:          2          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:    5231002          XT-PIC  serial
  5:   11578119          XT-PIC  cciss0
  8:          2          XT-PIC  rtc
 10:   13412657          XT-PIC  sym53c8xx
 11:        450          XT-PIC  sym53c8xx
 13:          1          XT-PIC  fpu
 15:   36100885          XT-PIC  eth0
NMI:          0
ERR:          0

root@server {540} # uname -a
Linux server 2.2.18 #1 SMP Sun May 27 23:14:43 CEST 2001 i686 unknown

root@server {541} # lsmod
Module Size Used by
sym53c8xx 56592 0

af_packet               6528   1  (autoclean)
nfsd                  184416  16  (autoclean)
nfs                    75872   1  (autoclean)
lockd                  47344   1  (autoclean) [nfsd nfs]
sunrpc                 63376   1  (autoclean) [nfsd nfs lockd]
acenic                125744   1  (autoclean)
softdog                 1584   1  (autoclean)
st                     25424   0
scsi_mod               55504   2  [sym53c8xx st]
cciss                  17552   9
ext2                   42032   7

These are the sym53c8xx driver's boot-messages:
[...]
sym53c8xx: at PCI bus 0, device 1, function 0
sym53c8xx: 53c1510D detected
sym53c8xx: at PCI bus 0, device 1, function 1
sym53c8xx: 53c1510D detected
sym53c1510D-0: rev 0x2 on pci bus 0 device 1 function 0 irq 10
sym53c1510D-0: ID 7, Fast-40, Parity Checking
sym53c1510D-1: rev 0x2 on pci bus 0 device 1 function 1 irq 11
sym53c1510D-1: ID 7, Fast-40, Parity Checking
scsi0 : sym53c8xx-1.7.1-20000726
scsi1 : sym53c8xx-1.7.1-20000726
scsi : 2 hosts.
Vendor: HP Model: Ultrium 1-SCSI Rev: N11D
Type: Sequential-Access ANSI SCSI revision: 03
Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0 [...]

Any help is appreciated!
Many thanks in advance!

- andreas

--

Andreas Haumer                     | mailto:[email protected]
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw

Hi Gérard,

thanks for your reply!

Quoted 3 lines · Gérard Roudier

On Wed, 19 Dec 2001, Andreas Haumer wrote:

[...]

Quoted 11 lines
Quoted 5 lines
Dec 10 15:00:01 server kernel: st0: Error with sense data: Info
fld=0x8000, Current st09:00: sense key Hardware Error
Dec 10 15:00:01 server kernel: Additional sense indicates Internal

target failure

This one is the result of a REQUEST SENSE performed due probably to a CHECK condition SCSI status reported by the device. It is not a SCSI transport problem. The device just reports an error to the application client. This is not a normal situation but happens very often.

Ok.

Quoted 11 lines
Quoted 8 lines

[...]

After that, the amanda process hangs in state "D" and cannot be killed anymore. The machine itself is still working.
This _seems_ to be the indication of an error of the HP Ultrium itself, though the drive works quite fine otherwise...

The 'D' states indicates that the process is waiting for something without being interruptible. This may be due to it not having been waken up on the

I knew that...

Quoted 3 lines

IO error. The sym53c8xx driver did its work by performing the REQUEST SENSE, but something in upper layer seem not to complete the IO.

That's what I wasn't sure about...

[...]

Quoted 5 lines
Quoted 2 lines

b) Does the st0 error message indicate it should be replaced?

Probably not. But it is very poor an information about the real issue.

I know, but I have the problem to decide how to proceed in this situation...

Quoted 6 lines
Quoted 2 lines

c) Is there a bug in the sym53c8xx driver which makes the amanda process hang uninterruptable when this error occurs?

Not known. But possible, even if in my opinion, the driver is not at fault.

Ok.

[...]

Quoted 4 lines

There are probably still bugs in the driver, but none are intentionnal, beleive me.

I honestly do believe you! :-)

Quoted 9 lines
Quoted 5 lines

The Ultrium hardware error is not reproducable at will. It just happens every now and then.
Next thing I will try is to use a different SCSI controller (Adaptec 29160 or the like) to see if the hanging process occurs with a different SCSI driver, too.

This is indeed something to try.
I am very interested in the result.

The controller change is scheduled on December 28th. We'll then see how it works in the next weeks/months. I'll keep you (and LKML) informend...

Thank you.

- andreas

Signature · 4 lines
Andreas Haumer                     | mailto:[email protected]
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
#3 lore raw

On Thu, 20 Dec 2001, Andreas Haumer wrote:

[...]

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines

The Ultrium hardware error is not reproducable at will. It just happens every now and then.
Next thing I will try is to use a different SCSI controller (Adaptec 29160 or the like) to see if the hanging process occurs with a different SCSI driver, too.

Quoted 6 lines
Quoted 3 lines

This is indeed something to try.
I am very interested in the result.

The controller change is scheduled on December 28th. We'll then see how it works in the next weeks/months. I'll keep you (and LKML) informend...

Thanks in advance.

In the meantime, you may give a try with the newer major version of the driver. It is available in latests 2.4.x and 2.5.x kernels and tarballs usable under not too old linux-2.2.x are ftp-available:

ftp://ftp.tux.org/roudier/drivers/protables/sym-2.1.x/

sym-2.1.16-20011028.tar.gz should apply to linux-2.2.18.

This new major driver version uses EH threads for error recovery.

Gérard.