[4600] in linux-scsi channel archive
Oops with Buslogic in 2.0.35
daemon@ATHENA.MIT.EDU (rune@ftech.net)
Mon Aug 24 08:40:29 1998
To: linux-scsi@vger.rutgers.edu, linux-kernel@vger.rutgers.edu
Cc: lnz@dandelion.com, rune@ftech.net
From: rune@ftech.net
Date: 24 Aug 1998 13:19:51 +0100
Hi,
This is a reccuring problem, although I received better logging this
time around.
I just got this in my kernel log, the scsi bus has hung completely and
I will shortly have to power cycle the box.
scsi : aborting command due to timeout : pid 18368158, scsi1, channel 0, id 5, lun 0 Write (6) 00 00 8f 02 00
scsi1: Aborting CCB #18368183 to Target 5
scsi : aborting command due to timeout : pid 18368134, scsi1, channel 0, id 3, lun 0 Write (6) 09 d6 99 f4 00
scsi1: Aborting CCB #18368159 to Target 3
[repeated many times for targets 2 - 5.]
SCSI host 1 abort (pid 18368134) timed out - resetting
SCSI bus is being reset for host 1 channel 0.
scsi1: Sending Bus Device Reset CCB #18368227 to Target 3
SCSI host 1 channel 0 reset (pid 18368134) timed out - trying harder
SCSI bus is being reset for host 1 channel 0.
scsi1: Resetting BusLogic BT-952 due to Target 3
scsi1: *** BusLogic BT-952 Initialized Successfully ***
I host 1 abort (pid 18368134) timed out - resetting
SCSI bus is being reset for host 1 channel 0.
scsi1: Resetting BusLogic BT-952 due to Target 3
scsi1: *** BusLogic BT-952 Initialized Successfully ***
general protection: 0000
CPU: 0
EIP: 0010:[BusLogic_ResetHostAdapter+667/764]
EFLAGS: 00010002
eax: 472d4a56 ebx: 00000000 ecx: 00080068 edx: 00fec018
esi: 00fe9b00 edi: 1fffd410 ebp: 00080068 esp: 001c6a80
ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=001c4c00)
Stack: 1fffd410 00080068 00000002 1fff7214 00080018 000019a0 00000000 001777a0
00000003 00000203 001a3f70 00080068 1fff7214 00000002 00000000 00080018
1fff7214 00000002 1fff7257 00000002 00000000 00185a68 1fff7214 00000002
Call Trace: [console_print+360/380]
[BusLogic_ResetCommand+160/280]
[scsi_reset+196/776]
[scsi_times_out+107/296]
[scsi_main_timeout+134/168]
[timer_bh+248/820]
[do_bottom_half+59/96]
[handle_bottom_half+11/24]
[sys_idle+92/112]
[system_call+85/124]
[init+0/612]
[BusLogic_InitializeMultiMasterProbeInfo+456/1552]
[start_kernel+429/440]
Code: ff d0 89 df 83 c4 04 85 ff 75 da 8b 76 78 85 f6 75 bf c7 44
Aiee, killing interrupt handler
SCSI host 1 channel 0 reset (pid 18368134) timed out - trying harder
SCSI bus is being reset for host 1 channel 0.
scsi1: Unable to Reset Command to Target 3 - Reset Pending
scsi : aborting command due to timeout : pid 18368135, scsi1, channel 0, id 3, lun 0 Write (6) 09 d7 8d 44 00
[repeated many times for id 2 & 3]
kfree of non-kmalloced memory: 001c6c48, next= 00000000, order=0
kfree of non-kmalloced memory: 001c6c38, next= 00000000, order=0
kfree of non-kmalloced memory: 001c714c, next= 00000000, order=0
idle task may not sleep
last message repeated 4 times
SCSI host 1 reset (pid 18368134) timed out again -
last message repeated 4 times
SCSI host 1 reset (pid 18368134) timed out again -
probably an unrecoverable SCSI bus or device hang.
[and then many more]
scsi1: Unable to Reset Command to Target 2 - Reset Pending
SCSI host 1 abort (pid 18368151) timed out - resetting
[for Target 2 & 3]
Useful info:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DCAS-34330W Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DCAS-34330W Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: IBM Model: DDRS-39130W Rev: S92A
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: IBM Model: DDRS-39130W Rev: S71D
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: IBM Model: DDRS-39130W Rev: S71D
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: IBM Model: DDRS-39130W Rev: S71D
Type: Direct-Access ANSI SCSI revision: 02
Machine contains BT 958 wide, disks are runnning at:
Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset 15
scsi0 is active-terminated, scsi1 is terminated by Id5.
Is this just due to lack of active termination on scsi1 - or something
more sinister?
- Regards, Robert.
--
Robert Collier - Network Operations - Frontier Internet
----------------------------------------------------------------
Disclaimer: The views contained herein may not reflect the views
of my employer and reliance should not be placed thereon.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
