On Sat, 2014-01-04 at 05:44 +0800, jidanni@jidanni.org wrote: > >>>>> "BH" == Ben Hutchings <ben@decadent.org.uk> writes: > BH> And what were those error messages? > BH> Which USB devices are you using (this is probably disk or network > BH> related)? > > I had done an aptitude update on writing onto > # fdisk -l > Disk /dev/sdg: 3867 MB, 3867148288 bytes OK, the important thing is it's usb-storage. > 181 heads, 32 sectors/track, 1304 cylinders, total 7553024 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0xc3072e18 > > # mount > Device Boot Start End Blocks Id System > /dev/sdg1 32 868799 434384 83 Linux > /dev/sdg2 868800 7553023 3342112 83 Linux > > /dev/sdg2 on /var/cache/apt/archives type ext3 (rw,noatime,errors=remount-ro,data=ordered) > /dev/sdg1 on /var/lib/apt/lists type ext3 (rw,noatime,errors=remount-ro,data=ordered) > > # cat /var/log/syslog > > Jan 1 06:57:38 jidanni5 ntpd[2822]: Listen normally on 5 lo ::1 UDP 123 > Jan 1 06:57:38 jidanni5 ntpd[2822]: Listen normally on 6 eth0 fe80::2289:84ff:fe28:ad9 UDP 123 > Jan 1 06:57:38 jidanni5 ntpd[2822]: peers refreshed > Jan 1 06:57:38 jidanni5 ntpd[2822]: Listening on routing socket on fd #23 for interface updates > Jan 1 07:04:49 jidanni5 kernel: [ 559.624680] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63 > Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63 > Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63 > > 100000 lines later... oops I mean an actual MILLION lines later Assuming my fix for the repetition is correct, the remaining problem is why usb-storage is generating such large/fragmented urbs. (And how did this work before the recent changes to Link TRBs? Or did it result in a different failure mode?) [...] > Jan 1 07:04:58 jidanni5 kernel: [ 568.615784] usb 1-4.3: USB disconnect, device number 5 > Jan 1 07:04:58 jidanni5 kernel: [ 568.622573] sd 7:0:0:0: [sdg] Unhandled error code > Jan 1 07:04:58 jidanni5 kernel: [ 568.622577] sd 7:0:0:0: [sdg] > Jan 1 07:04:58 jidanni5 kernel: [ 568.622579] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK > Jan 1 07:04:58 jidanni5 kernel: [ 568.622581] sd 7:0:0:0: [sdg] CDB: > Jan 1 07:04:58 jidanni5 kernel: [ 568.622583] Write(10): 2a 00 00 06 85 0e 00 00 da 00 I think this is a write of 218 sectors, presumably 512 bytes each. > Jan 1 07:04:58 jidanni5 kernel: [ 568.622591] end_request: I/O error, dev sdg, sector 427278 > Jan 1 07:04:58 jidanni5 kernel: [ 568.622595] Buffer I/O error on device sdg1, logical block 213623 > Jan 1 07:04:58 jidanni5 kernel: [ 568.622596] lost page write due to I/O error on sdg1 > Jan 1 07:04:58 jidanni5 kernel: [ 568.622673] Aborting journal on device sdg1-8. > Jan 1 07:04:58 jidanni5 kernel: [ 568.622702] JBD2: Error -5 detected when updating journal superblock for sdg1-8. > Jan 1 07:04:58 jidanni5 kernel: [ 568.622782] journal commit I/O error [...] Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo.
Attachment:
signature.asc
Description: This is a digitally signed message part