USB storage device transfers freeze when usbdevs is run: hardware bug or software bug? While I was doing a "gzcat < *.gz > /dev/rsd2d", where sd2 was a USB memory stick, I happened to run "usbdevs -dv" and the writes to the USB device froze, and indeed the writing process was stuck in the kernel (I couldn't even stop it with ^Z). Luckily yanking the stick out seemed to unfreeze and kill the process and clean everything up nicely and I was able to re-insert it and re-do the write to it without incident. This is on an amd64 server running 9.99.64. Upon removal and subsequent re-insertion the kernel said the following (but was silent before this when usbdevs ran): [ 193334.306434] umass0: BBB reset failed, IOERROR [ 193334.306434] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.318288] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.318288] umass0: BBB reset failed, IOERROR [ 193334.329223] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.329223] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.341024] umass0: BBB reset failed, IOERROR [ 193334.341024] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.351781] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.357775] sd2d: error writing fsbn 4053632 of 4053632-4053759 (sd2 bn 4053632; cn 4021 tn 7 sn 23) [ 193334.366963] umass0: BBB reset failed, IOERROR [ 193334.366963] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.378283] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.378283] umass0: BBB reset failed, IOERROR [ 193334.389225] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.389225] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.401026] umass0: BBB reset failed, IOERROR [ 193334.401026] umass0: BBB bulk-in clear stall failed, IOERROR [ 193334.411782] umass0: BBB bulk-out clear stall failed, IOERROR [ 193334.417780] umass0: BBB reset failed, IOERROR [ 193334.417780] sd2(umass0:0:0:0): generic HBA error [ 193334.426444] sd2: detached [ 193334.426444] scsibus1: detached [ 193334.426444] umass0: detached [ 193334.436445] umass0: at uhub6 port 2 (addr 5) disconnected reinsertion: [ 193341.516925] umass0 at uhub6 port 2 configuration 1 interface 0 [ 193341.516925] umass0: SMI Corporation (0x090c) USB DISK (0x1000), rev 2.00/11.00, addr 5 [ 193341.526926] umass0: using SCSI over Bulk-Only [ 193341.526926] scsibus1 at umass0: 2 targets, 1 lun per target [ 193342.366983] sd2 at scsibus1 target 0 lun 0: <SMI, USB DISK, 1100> disk removable [ 193342.376985] sd2: 7712 MB, 15744 cyl, 16 head, 63 sec, 512 bytes/sect x 15794176 sectors [ 193342.386986] sd2: GPT GUID: d1e3490c-b0e6-42e9-9d9e-3ac286a0f7e0 [ 193342.396989] dk6 at sd2: "EFI system", 262144 blocks at 2048, type: msdos [ 193342.396989] dk7 at sd2: "d3aa0396-d911-4aac-baa8-f2478557d31a", 7544832 blocks at 264192, type: ffs I'm guessing it's a software bug with bad locking order somewhere. -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpndc9O1afVU.pgp
Description: OpenPGP Digital Signature