Bug#733826: crazy loop "xhci_hcd Too many fragments"
>>>>> "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
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
# grep -c xhci /var/log/syslog
1052831:
Jan 1 07:04:58 jidanni5 kernel: [ 568.615382] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63
Jan 1 07:04:58 jidanni5 kernel: [ 568.615391] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63
Jan 1 07:04:58 jidanni5 kernel: [ 568.615400] xhci_hcd 0000:00:14.0: Too many fragments 79, max 63
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
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
Jan 1 07:04:58 jidanni5 kernel: [ 568.842558] usb 1-4.3: new full-speed USB device number 6 using xhci_hcd
Jan 1 07:05:03 jidanni5 kernel: [ 573.840855] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
Jan 1 07:05:04 jidanni5 kernel: [ 574.813608] usb 1-4.3: not running at top speed; connect to a high speed hub
Jan 1 07:05:04 jidanni5 kernel: [ 574.816058] usb 1-4.3: New USB device found, idVendor=090c, idProduct=1000
Jan 1 07:05:04 jidanni5 kernel: [ 574.816074] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 1 07:05:04 jidanni5 kernel: [ 574.816080] usb 1-4.3: Product: USB DISK
Jan 1 07:05:04 jidanni5 kernel: [ 574.816084] usb 1-4.3: Manufacturer: SMI Corporation
Jan 1 07:05:04 jidanni5 kernel: [ 574.816088] usb 1-4.3: SerialNumber: AA330463000360008655
Jan 1 07:05:04 jidanni5 kernel: [ 574.816658] usb-storage 1-4.3:1.0: USB Mass Storage device detected
Jan 1 07:05:04 jidanni5 kernel: [ 574.816713] scsi9 : usb-storage 1-4.3:1.0
Jan 1 07:05:05 jidanni5 kernel: [ 575.817473] scsi 9:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS
Jan 1 07:05:05 jidanni5 kernel: [ 575.817921] sd 9:0:0:0: Attached scsi generic sg7 type 0
Jan 1 07:05:05 jidanni5 kernel: [ 575.819774] sd 9:0:0:0: [sdi] 7553024 512-byte logical blocks: (3.86 GB/3.60 GiB)
Jan 1 07:05:05 jidanni5 kernel: [ 575.820658] sd 9:0:0:0: [sdi] Write Protect is off
Jan 1 07:05:05 jidanni5 kernel: [ 575.820663] sd 9:0:0:0: [sdi] Mode Sense: 43 00 00 00
Jan 1 07:05:05 jidanni5 kernel: [ 575.821457] sd 9:0:0:0: [sdi] No Caching mode page found
Jan 1 07:05:05 jidanni5 kernel: [ 575.821462] sd 9:0:0:0: [sdi] Assuming drive cache: write through
Jan 1 07:05:05 jidanni5 kernel: [ 575.825400] sd 9:0:0:0: [sdi] No Caching mode page found
Jan 1 07:05:05 jidanni5 kernel: [ 575.825405] sd 9:0:0:0: [sdi] Assuming drive cache: write through
Jan 1 07:05:05 jidanni5 kernel: [ 575.829815] sdi: sdi1 sdi2
Jan 1 07:05:05 jidanni5 kernel: [ 575.832884] sd 9:0:0:0: [sdi] No Caching mode page found
Jan 1 07:05:05 jidanni5 kernel: [ 575.832890] sd 9:0:0:0: [sdi] Assuming drive cache: write through
Jan 1 07:05:05 jidanni5 kernel: [ 575.832894] sd 9:0:0:0: [sdi] Attached SCSI removable disk
Jan 1 07:08:14 jidanni5 kernel: [ 763.966121] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:08:14 jidanni5 kernel: [ 763.966200] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:08:14 jidanni5 kernel: [ 763.966228] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:08:14 jidanni5 kernel: [ 763.966297] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:08:14 jidanni5 kernel: [ 763.966322] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
50 lines later:
Jan 1 07:08:14 jidanni5 kernel: [ 764.000872] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:08:14 jidanni5 kernel: [ 764.000880] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:32:59 jidanni5 kernel: [ 2248.702148] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:33:00 jidanni5 kernel: [ 2249.967051] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:35:32 jidanni5 kernel: [ 2402.304784] EXT4-fs warning (device sdg2): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:37:20 jidanni5 kernel: [ 2509.557854] EXT4-fs (sdi2): mounting ext3 file system using the ext4 subsystem
Jan 1 07:37:20 jidanni5 kernel: [ 2509.695905] EXT4-fs (sdi2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
Jan 1 07:37:33 jidanni5 kernel: [ 2523.007946] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
Jan 1 07:37:39 jidanni5 kernel: [ 2528.960437] EXT4-fs error (device sdg1): ext4_put_super:772: Couldn't clean up the journal
Jan 1 07:37:39 jidanni5 kernel: [ 2528.960447] EXT4-fs (sdg1): Remounting filesystem read-only
Jan 1 07:40:12 jidanni5 kernel: [ 2682.139737] EXT4-fs (sdi1): mounting ext3 file system using the ext4 subsystem
Jan 1 07:40:12 jidanni5 kernel: [ 2682.177316] EXT4-fs (sdi1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
I had now unmounted, fsck -f'd, and remounted.
# lswh # today
*-scsi:3
physical id: 5
bus info: usb@1:4.3
logical name: scsi7
capabilities: emulated
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdg
size: 3688MiB (3867MB)
capabilities: partitioned partitioned:dos
configuration: sectorsize=512 signature=c3072e18
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@7:0.0.0,1
logical name: /dev/sdg1
logical name: /var/lib/apt/lists
version: 1.0
serial: 26a1643a-011c-4d6b-8234-c327f9dc2495
size: 424MiB
capacity: 424MiB
capabilities: primary journaled extended_attributes recover ext3 ext2 initialized
configuration: created=2013-07-26 15:17:15 filesystem=ext3 lastmountpoint=/var/lib/apt/lists modified=2014-01-04 04:23:41 mount.fstype=ext3 mount.options=rw,noatime,errors=remount-ro,data=ordered mounted=2014-01-04 04:23:41 state=mounted
*-volume:1
description: EXT3 volume
vendor: Linux
physical id: 2
bus info: scsi@7:0.0.0,2
logical name: /dev/sdg2
logical name: /var/cache/apt/archives
version: 1.0
serial: 82152152-fd1b-41f5-8860-a65f18de2275
size: 3263MiB
capacity: 3263MiB
capabilities: primary journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2013-03-11 19:34:02 filesystem=ext3 lastmountpoint=/var/cache/apt/archives modified=2014-01-04 04:23:39 mount.fstype=ext3 mount.options=rw,noatime,errors=remount-ro,data=ordered mounted=2014-01-04 04:23:39 state=mounted
Anyway, just don't print 1 MILLION lines of anything without any restraint...
Reply to: