lkml.org 
[lkml]   [2000]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.2.15pre14
hi, 

I had some problems with a JAZ disk thatw asn't correctly detected during
boot (it didn't detect at all, reported SCSCI bus reset etc)

Normally this means that the format of the disk is damaged. No sweat, e2fscl
-- no way (sorry for the long lines)

Mar 17 07:34:27 grobbebol kernel: scsi : aborting command due to timeout : pid 12, scsi0, channel 0, id 4, lun 0 Start/Stop Unit 00 00 00 01 00
Mar 17 07:34:27 grobbebol kernel: scsi0: Aborting CCB #22 to Target 4
Mar 17 07:34:27 grobbebol kernel: SCSI host 0 abort (pid 12) timed out - resetting
Mar 17 07:34:27 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:34:27 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:34:29 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:34:29 grobbebol kernel:
Mar 17 07:34:29 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:34:29 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:34:29 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:35:30 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:35:30 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:35:30 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:35:30 grobbebol kernel:
Mar 17 07:35:30 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:35:30 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:35:30 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:36:32 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 12) timed out - resetting
Mar 17 07:36:32 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:36:32 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:36:32 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:36:32 grobbebol kernel:
Mar 17 07:36:32 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:36:32 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:36:32 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:37:36 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 12) timed out - resetting
Mar 17 07:37:36 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:37:36 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:37:37 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:37:37 grobbebol kernel:
Mar 17 07:37:37 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:37:37 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:37:37 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:38:42 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 12) timed out - resetting
Mar 17 07:38:42 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:38:42 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:38:42 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:38:42 grobbebol kernel:
Mar 17 07:38:42 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:38:42 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:38:42 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:38:46 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> <7>VFS: Disk change detected on device sd(8,1)
Mar 17 07:39:16 grobbebol kernel: scsi : aborting command due to timeout : pid 14, scsi0, channel 0, id 4, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
Mar 17 07:39:16 grobbebol kernel: scsi0: Aborting CCB #33 to Target 4
Mar 17 07:39:17 grobbebol kernel: SCSI host 0 abort (pid 14) timed out - resetting
Mar 17 07:39:17 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:39:17 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:39:19 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:39:19 grobbebol kernel:
Mar 17 07:39:19 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:39:19 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:39:19 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:39:52 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 14) timed out - resetting
Mar 17 07:39:52 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:39:52 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:39:53 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:39:53 grobbebol kernel:
Mar 17 07:39:53 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:39:53 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:39:53 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:40:28 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 14) timed out - resetting
Mar 17 07:40:28 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:40:28 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:40:28 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:40:28 grobbebol kernel:
Mar 17 07:40:28 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:40:28 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:40:28 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:41:03 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 14) timed out - resetting
Mar 17 07:41:03 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:41:03 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:41:03 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:41:03 grobbebol kernel:
Mar 17 07:41:03 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:41:03 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:41:03 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:41:37 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 14) timed out - resetting
Mar 17 07:41:37 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:41:37 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:41:38 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:41:38 grobbebol kernel:
Mar 17 07:41:38 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:41:38 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:41:38 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:42:12 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> scsi : aborting command due to timeout : pid 15, scsi0, channel 0, id 4, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
Mar 17 07:42:12 grobbebol kernel: scsi0: Aborting CCB #43 to Target 4
Mar 17 07:42:13 grobbebol kernel: SCSI host 0 abort (pid 15) timed out - resetting
Mar 17 07:42:13 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:42:13 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:42:13 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:42:47 grobbebol kernel: SCSI host 0 abort (pid 15) timed out - resetting
Mar 17 07:42:47 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:42:47 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:42:48 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:42:48 grobbebol kernel:
Mar 17 07:42:48 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:42:48 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:42:48 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:43:23 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 15) timed out - resetting
Mar 17 07:43:23 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:43:23 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:43:23 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:43:57 grobbebol kernel: SCSI host 0 abort (pid 15) timed out - resetting
Mar 17 07:43:57 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:43:57 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:43:58 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:44:31 grobbebol kernel: SCSI host 0 abort (pid 15) timed out - resetting
Mar 17 07:44:31 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:44:31 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:44:32 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:44:32 grobbebol kernel:
Mar 17 07:44:32 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:44:32 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:44:32 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:45:06 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> scsi : aborting command due to timeout : pid 16, scsi0, channel 0, id 4, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
Mar 17 07:45:06 grobbebol kernel: scsi0: Aborting CCB #53 to Target 4
Mar 17 07:45:08 grobbebol kernel: SCSI host 0 abort (pid 16) timed out - resetting
Mar 17 07:45:08 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:45:08 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:45:08 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:45:43 grobbebol kernel: SCSI host 0 abort (pid 16) timed out - resetting
Mar 17 07:45:43 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:45:43 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:45:43 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:45:43 grobbebol kernel:
Mar 17 07:45:43 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:45:43 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:45:43 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:46:17 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 16) timed out - resetting
Mar 17 07:46:17 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:46:17 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:46:18 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:46:18 grobbebol kernel:
Mar 17 07:46:18 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:46:18 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:46:18 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:46:53 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 16) timed out - resetting
Mar 17 07:46:53 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:46:53 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:46:53 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:47:28 grobbebol kernel: SCSI host 0 abort (pid 16) timed out - resetting
Mar 17 07:47:28 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:47:28 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:47:28 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:47:28 grobbebol kernel:
Mar 17 07:47:28 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:47:28 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:47:28 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:47:32 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> sda : READ CAPACITY failed.
Mar 17 07:47:32 grobbebol kernel: sda : status = 1, message = 00, host = 0, driver = 18
Mar 17 07:47:32 grobbebol kernel: sda : extended sense code = 6
Mar 17 07:47:32 grobbebol kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Mar 17 07:47:32 grobbebol kernel: sda: Write Protect is off
Mar 17 07:47:32 grobbebol kernel: sda:<6>Device not ready. Make sure there is a disc in the drive.
Mar 17 07:48:02 grobbebol kernel: scsi : aborting command due to timeout : pid 19, scsi0, channel 0, id 4, lun 0 Read (10) 00 00 00 00 00 00 00 02 00
Mar 17 07:48:02 grobbebol kernel: scsi0: Aborting CCB #65 to Target 4
Mar 17 07:48:03 grobbebol kernel: SCSI host 0 abort (pid 19) timed out - resetting
Mar 17 07:48:03 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:48:03 grobbebol kernel: scsi0: Sending Bus Device Reset CCB #66 to Target 4
Mar 17 07:48:05 grobbebol kernel: SCSI host 0 channel 0 reset (pid 19) timed out - trying harder
Mar 17 07:48:05 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:48:05 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:48:05 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:48:39 grobbebol kernel: SCSI host 0 abort (pid 19) timed out - resetting
Mar 17 07:48:39 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:48:39 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:48:39 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:48:39 grobbebol kernel:
Mar 17 07:48:39 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:48:39 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:48:39 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:49:13 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 19) timed out - resetting
Mar 17 07:49:13 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:49:13 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:49:15 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:49:15 grobbebol kernel:
Mar 17 07:49:15 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:49:15 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:49:15 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:49:48 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 19) timed out - resetting
Mar 17 07:49:48 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:49:48 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:49:50 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:49:50 grobbebol kernel:
Mar 17 07:49:50 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:49:50 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:49:50 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:50:24 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 19) timed out - resetting
Mar 17 07:50:24 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:50:24 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:50:24 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:50:24 grobbebol kernel:
Mar 17 07:50:24 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:50:24 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:50:24 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:50:25 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> scsidisk I/O error: dev 08:00, sector 0
Mar 17 07:50:25 grobbebol kernel: unable to read partition table
Mar 17 07:53:54 grobbebol kernel: scsi : aborting command due to timeout : pid 20, scsi0, channel 0, id 4, lun 0 Start/Stop Unit 00 00 00 01 00
Mar 17 07:53:54 grobbebol kernel: scsi0: Aborting CCB #76 to Target 4
Mar 17 07:53:54 grobbebol kernel: SCSI host 0 abort (pid 20) timed out - resetting
Mar 17 07:53:54 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:53:54 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:53:55 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:53:55 grobbebol kernel:
Mar 17 07:53:55 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:53:55 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:53:55 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:54:59 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 20) timed out - resetting
Mar 17 07:54:59 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:54:59 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:55:00 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:55:00 grobbebol kernel:
Mar 17 07:55:00 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:55:00 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:55:00 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:56:06 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 20) timed out - resetting
Mar 17 07:56:06 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:56:06 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:56:06 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:56:06 grobbebol kernel:
Mar 17 07:56:06 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 07:56:06 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:56:06 grobbebol kernel: bh: 1 [0 1]
Mar 17 07:57:09 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> SCSI host 0 abort (pid 20) timed out - resetting
Mar 17 07:57:09 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:57:09 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:57:10 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:57:10 grobbebol kernel:
Mar 17 07:57:10 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:57:10 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:57:10 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:58:14 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 20) timed out - resetting
Mar 17 07:58:14 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:58:14 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:58:15 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:58:15 grobbebol kernel:
Mar 17 07:58:19 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:58:19 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:58:19 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:58:19 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> <7>VFS: Disk change detected on device sd(8,0)
Mar 17 07:58:49 grobbebol kernel: scsi : aborting command due to timeout : pid 22, scsi0, channel 0, id 4, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
Mar 17 07:58:49 grobbebol kernel: scsi0: Aborting CCB #87 to Target 4
Mar 17 07:58:50 grobbebol kernel: SCSI host 0 abort (pid 22) timed out - resetting
Mar 17 07:58:50 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:58:50 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:58:51 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:58:51 grobbebol kernel:
Mar 17 07:58:51 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:58:51 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:58:51 grobbebol kernel: bh: 1 [1 0]
Mar 17 07:59:25 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 22) timed out - resetting
Mar 17 07:59:25 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 07:59:25 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 07:59:26 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 07:59:26 grobbebol kernel:
Mar 17 07:59:26 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 07:59:26 grobbebol kernel: irq: 0 [0 0]
Mar 17 07:59:26 grobbebol kernel: bh: 1 [1 0]
Mar 17 08:00:00 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 22) timed out - resetting
Mar 17 08:00:00 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 08:00:00 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 08:00:01 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 08:00:01 grobbebol kernel:
Mar 17 08:00:01 grobbebol kernel: wait_on_bh, CPU 0:
Mar 17 08:00:01 grobbebol kernel: irq: 0 [0 0]
Mar 17 08:00:01 grobbebol kernel: bh: 1 [0 1]
Mar 17 08:00:35 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 22) timed out - resetting
Mar 17 08:00:35 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 08:00:35 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 08:00:36 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 08:00:36 grobbebol kernel:
Mar 17 08:00:36 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 08:00:36 grobbebol kernel: irq: 0 [0 0]
Mar 17 08:00:36 grobbebol kernel: bh: 1 [1 0]
Mar 17 08:01:10 grobbebol kernel: <[c010ae85]> <[c01cc300]> <[c01cce9f]> <[c01d2860]> SCSI host 0 abort (pid 22) timed out - resetting
Mar 17 08:01:10 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 08:01:10 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 08:01:11 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 08:01:11 grobbebol kernel:
Mar 17 08:01:11 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 08:01:11 grobbebol kernel: irq: 0 [0 0]
Mar 17 08:01:11 grobbebol kernel: bh: 1 [1 0]
Mar 17 08:01:45 grobbebol kernel: <[c010ae85]> <[c0194b9a]> <[c0194c15]> <[c01a3bed]> <[c0179bf7]> <[c013241f]> <[c013290a]> scsi : aborting command due to timeout : pid 23, scsi0, channel 0, id 4, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
Mar 17 08:01:45 grobbebol kernel: scsi0: Aborting CCB #97 to Target 4
Mar 17 08:01:46 grobbebol kernel: SCSI host 0 abort (pid 23) timed out - resetting
Mar 17 08:01:46 grobbebol kernel: SCSI bus is being reset for host 0 channel 0.
Mar 17 08:01:46 grobbebol kernel: scsi0: Resetting BusLogic BT-930 due to Target 4
Mar 17 08:01:47 grobbebol kernel: scsi0: *** BusLogic BT-930 Initialized Successfully ***
Mar 17 08:01:47 grobbebol kernel:
Mar 17 08:01:47 grobbebol kernel: wait_on_bh, CPU 1:
Mar 17 08:01:47 grobbebol kernel: irq: 0 [0 0]
Mar 17 08:01:47 grobbebol kernel: bh: 1 [1 0]

ad infinitum. Note that the system is unresponsive for every xx seconds for
a second or so. Killing e2fsck also takes quite some work.

I don't know if this _is_ a problem. Just wanted to mention it.

the used system is a dual 466 MHz celeron, 256 MB, non OC, no vmware.

--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.2.14 SMP 2x466MHz / 256 MB | on Usenet. _\_v

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.042 / U:0.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site