[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#312320: kernel-image-2.6.11-1-k7: Firewire hard freeze on moderate load



  I also see this problem; for me it happens reproducibly when copying
several gigabytes to a firewire HD with kernel-image-2.6.11-1-686-smp
2.6.11-5 (I've also reproduced it under kernel-image-2.6.8-2-686
2.6.8-16).  The error messages I get when the error happens are:

Jun  6 21:12:12 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:12 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:12:12 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:12 localhost vmunix: Write (10) 2a 00 03 89 2e cb 00 00 01 00
Jun  6 21:12:22 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:22 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:12:22 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:22 localhost vmunix: Write (10) 2a 00 03 89 2e eb 00 00 01 00
Jun  6 21:12:42 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:42 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:12:42 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:42 localhost vmunix: Write (10) 2a 00 03 89 2f 2b 00 00 01 00
Jun  6 21:12:52 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:52 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:12:52 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:12:52 localhost vmunix: Write (10) 2a 00 03 89 2f 4b 00 00 01 00
Jun  6 21:13:02 localhost vmunix: borting sbp2 command
Jun  6 21:13:02 localhost vmunix: Write (10) 2a 00 03 89 2f 6b 00 00 01 00
Jun  6 21:13:12 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:13:22 localhost vmunix: Test Unit R<3>ieee1394: sbp2: aborting sbp2 command
Jun  6 21:13:22 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:13:22 localhost vmunix: ieee1394: sbp2: reset requested
Jun  6 21:13:22 localhost vmunix: ieee1394: sbp2: Generating sbp2 fetch agent reset
Jun  6 21:13:32 localhost vmunix: t Ready 00 00 00 00 00 00
Jun  6 21:13:32 localhost vmunix: ieee1394: sbp2: reset requested

... snip ...

Jun  6 21:16:32 localhost vmunix: ieee1394: sbp2: aborting sbp2 command
Jun  6 21:16:32 localhost vmunix: Test Unit Ready 00 00 00 00 00 00
Jun  6 21:16:32 localhost vmunix: scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 0 lun 0
Jun  6 21:16:32 localhost last message repeated 7 times
Jun  6 21:16:32 localhost vmunix: SCSI error : <2 0 0 0> return code = 0x50000
Jun  6 21:16:32 localhost vmunix: end_request: I/O error, dev sdb, sector 59322027
Jun  6 21:16:32 localhost vmunix: Buffer I/O error on device sdb1, logical block 59321964
Jun  6 21:16:32 localhost vmunix: lost page write due to I/O error on sdb1
Jun  6 21:16:32 localhost vmunix: scsi2 (0:0): rejecting I/O to offline device
Jun  6 21:16:32 localhost vmunix: Buffer I/O error on device sdb1, logical block 59322220
Jun  6 21:16:32 localhost vmunix: lost page write due to I/O error on sdb1
Jun  6 21:16:32 localhost vmunix: SCSI error : <2 0 0 0> return code = 0x50000

  ... and so on.  The same device works reliably when I connect it via
its USB2 connector.  This is the dmesg output from connecting the device
(via firewire):

Jun  6 20:12:45 localhost vmunix: ieee1394: Error parsing configrom for node 0-01:100-00:1023]  GUID[0050770e900005cd]
Jun  6 20:12:45 localhost vmunix: sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
Jun  6 20:12:46 localhost vmunix: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Jun  6 20:12:46 localhost vmunix:   Vendor: Maxtor 6  Model: B200P0            Rev:     
Jun  6 20:12:46 localhost vmunix:   Type
Jun  6 20:12:46 localhost vmunix: us0/target0/lun0: p1
Jun  6 20:12:46 localhost vmunix: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0

  The firewire controller is:

0000:01:03.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61)

-- 
Andrew Moise <chops@demiurgestudios.com>




Reply to: