Bug#733826: crazy loop xhci_hcd Too many fragments
From: Alan Stern Subject: Re: Bug#733826: crazy loop xhci_hcd Too many fragments On Mon, 6 Jan 2014, Ben Hutchings wrote: On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote: ... # 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 :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0: Too many fragments 79, max 63 10 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. usb-storage doesn't generate large or fragmented anything. It merely passes on the scatter-gather information it gets from the block layer. Although not a real fix to the underlying problem, it seems that the default ring size is far too small. Any amount of network traffic also activates the ring expansion code. IIRC each ring entry is 16 bytes, so increasing the ring size to 256 still keeps the rings to a single 4k page. Whether anything regularly exceeds 255 fragments is a another matter. David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
On Mon, Jan 06, 2014 at 03:52:24PM +, David Laight wrote: From: Alan Stern Subject: Re: Bug#733826: crazy loop xhci_hcd Too many fragments On Mon, 6 Jan 2014, Ben Hutchings wrote: On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote: ... # 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 :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0: Too many fragments 79, max 63 10 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. usb-storage doesn't generate large or fragmented anything. It merely passes on the scatter-gather information it gets from the block layer. Although not a real fix to the underlying problem, it seems that the default ring size is far too small. Did you mean ring segment size? Any amount of network traffic also activates the ring expansion code. IIRC each ring entry is 16 bytes, so increasing the ring size to 256 still keeps the rings to a single 4k page. Whether anything regularly exceeds 255 fragments is a another matter. If so, yes, changing the segment size makes sense. TRBS_PER_SEGMENT could be increased to 256. I'm not sure if we should switch to using dma_alloc_coherent instead of a DMA pool. Some systems could be using bigger than 4K pages, so we should probably still stick with DMA pools. Ben, can you change your patch to increase TRBS_PER_SEGMENT to 256? Sarah Sharp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
On Mon, Jan 06, 2014 at 10:06:33AM -0500, Alan Stern wrote:
On Mon, 6 Jan 2014, Ben Hutchings wrote:
On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote:
BH == Ben Hutchings b...@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 :00:14.0:
Too many fragments 79, max 63
Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0:
Too many fragments 79, max 63
Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0:
Too many fragments 79, max 63
10 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.
usb-storage doesn't generate large or fragmented anything. It merely
passes on the scatter-gather information it gets from the block layer.
And the block layer depends on drivers to tell it what their
scatter-gather capabilities are.
The answer appears to be that xhci is lying:
int xhci_gen_setup(struct usb_hcd *hcd, xhci_get_quirks_t get_quirks)
{
[...]
/* Accept arbitrarily long scatter-gather lists */
hcd-self.sg_tablesize = ~0;
and this value gets copied up the stack to the block layer.
Ben.
--
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
On Sat, 2014-01-04 at 05:44 +0800, jida...@jidanni.org wrote: BH == Ben Hutchings b...@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 :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0: Too many fragments 79, max 63 10 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. signature.asc Description: This is a digitally signed message part
Bug#733826: crazy loop xhci_hcd Too many fragments
BH == Ben Hutchings b...@decadent.org.uk writes: BH Assuming my fix for the repetition is correct, the remaining problem is BH why usb-storage is generating such large/fragmented urbs. (And how did BH this work before the recent changes to Link TRBs? Or did it result in a BH different failure mode?) Well all I know is now in my cat /etc/ppp/ip-up.d/z50apt-get I added syncs, sync; apt-get update; sync and haven't had the problem again, and now using $ uname -a Linux jidanni3 3.12-1-686-pae #1 SMP Debian 3.12.6-2 (2013-12-29) i686 GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
BH == Ben Hutchings b...@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 :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0: Too many fragments 79, max 63 10 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 :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:58 jidanni5 kernel: [ 568.615391] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:58 jidanni5 kernel: [ 568.615400] xhci_hcd :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 :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: [
Bug#733826: crazy loop xhci_hcd Too many fragments
Crap. The same thing happened again today. Now it is up to # grep -c xhci /var/log/syslog 1958427 lines! 222] usb 1-4.3: USB disconnect, device number 5 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883696] sd 7:0:0:0: [sdg] Unhandled error code Jan 4 05:28:05 jidanni5 kernel: [ 3904.883702] sd 7:0:0:0: [sdg] Jan 4 05:28:05 jidanni5 kernel: [ 3904.883703] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jan 4 05:28:05 jidanni5 kernel: [ 3904.883705] sd 7:0:0:0: [sdg] CDB: Jan 4 05:28:05 jidanni5 kernel: [ 3904.883707] Write(10): 2a 00 00 06 84 e0 00 00 bc 00 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883715] end_request: I/O error, dev sdg, sector 427232 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883756] EXT4-fs warning (device sdg1): ext4_end_bio:316: I/O error writing to inode 49349 (offset 0 size 0 starting block 130529) jidanni5 kernel: [ 3904.884184] EXT4-fs warning (device sdg1): ext4_end_bio:316: I/O error writing to inode 49349 (offset 0 size 0 starting block 133885) Jan 4 05:28:05 jidanni5 kernel: [ 3904.885980] Aborting journal on device sdg1-8. Jan 4 05:28:05 jidanni5 kernel: [ 3904.886159] JBD2: Error -5 detected when updating journal superblock for sdg1-8. Jan 4 05:28:05 jidanni5 kernel: [ 3904.886294] journal commit I/O error Jan 4 05:28:05 jidanni5 kernel: [ 3904.893305] EXT4-fs error (device sdg1): ext4_journal_check_start:56: Detected aborted journal Jan 4 05:28:05 jidanni5 kernel: [ 3904.893312] EXT4-fs (sdg1): Remounting filesystem read-only Jan 4 05:28:05 jidanni5 kernel: [ 3904.893314] EXT4-fs (sdg1): previous I/O error to superblock detected Jan 4 05:28:05 jidanni5 kernel: [ 3905.111627] usb 1-4.3: new full-speed USB device number 6 using xhci_hcd Jan 4 05:28:06 jidanni5 kernel: [ 3905.440770] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0) 06:16 ~# fsck -V -f -v /dev/sdi1 fsck from util-linux 2.20.1 [/sbin/fsck.ext3 (1) -- /var/lib/apt/lists] fsck.ext3 -f -v /dev/sdi1 e2fsck 1.42.9 (28-Dec-2013) /dev/sdi1: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (351333, counted=347029). Fixy? y yes Free inodes count wrong (108932, counted=108929). Fixy? yes /dev/sdi1: * FILE SYSTEM WAS MODIFIED * 39 inodes used (0.04%, out of 108968) 16 non-contiguous files (41.0%) 1 non-contiguous directory (2.6%) # of inodes with ind/dind/tind blocks: 18/7/0 87148 blocks used (20.07%, out of 434177) 0 bad blocks 0 large files 27 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 30 files 06:17 1 ~# fsck -V -f -v /dev/sdi2 fsck from util-linux 2.20.1 [/sbin/fsck.ext3 (1) -- /var/cache/apt/archives] fsck.ext3 -f -v /dev/sdi2 e2fsck 1.42.9 (28-Dec-2013) /dev/sdi2: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 1489 inodes used (0.71%, out of 209248) 709 non-contiguous files (47.6%) 1 non-contiguous directory (0.1%) # of inodes with ind/dind/tind blocks: 1087/59/0 360570 blocks used (43.15%, out of 835528) 0 bad blocks 1 large file 1477 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 1480 files 06:18 ~# mount /var/cache/apt/archives/ 06:19 ~# mount /var/lib/apt/lists/ 06:19 ~# mount |grep apt /dev/sdi2 on /var/cache/apt/archives type ext3 (rw,noatime,errors=remount-ro,data=ordered) /dev/sdi1 on /var/lib/apt/lists type ext3 (rw,noatime,errors=remount-ro,data=ordered) 06:19 ~# aptitude update ... OK # grep -v ^// /etc/apt/apt.conf.d/10jidanni APT::Default-Release experimental;//just order them in sources.list UNTRUE APT::Cache::AllVersions false; APT::Clean-Installed false; APT::Get::Purge true; APT::Install-Recommends false; Aptitude::CmdLine::Always-Prompt true; Aptitude::Purge-Unused true; Aptitude::CmdLine::Show-Why true;//511...@bugs.debian.org Aptitude::CmdLine::Show-Deps true;//587...@bugs.debian.org Acquire::http::No-Cache true;//564829 Acquire::PDiffs false; -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
BH == Ben Hutchings b...@decadent.org.uk writes: BH No, this message did not exist in that version. You are right. Wish there was a way to do $ reportbug $(the current kernel package name I am running) so I could avoid mistakes. BH Is any other error message logged? Yes, I recall some about disk problems, but mainly there were 10 of the problem message in a row, only differing by the millisecond counter prepended. BH Which USB devices are you using (this is probably disk or network BH related)? I was doing an aptitude update with my cache set to write to a USB SD card. Later I did fsck -f and remounted everything was OK. Anyway yes they forgot to rate limit that message. OK thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
Control: tag -1 moreinfo On Fri, Jan 03, 2014 at 12:52:30AM +0800, jida...@jidanni.org wrote: BH == Ben Hutchings b...@decadent.org.uk writes: BH No, this message did not exist in that version. You are right. Wish there was a way to do $ reportbug $(the current kernel package name I am running) so I could avoid mistakes. reportbug kernel BH Is any other error message logged? Yes, I recall some about disk problems, but mainly there were 10 of the problem message in a row, only differing by the millisecond counter prepended. And what were those error messages? BH Which USB devices are you using (this is probably disk or network BH related)? I was doing an aptitude update with my cache set to write to a USB SD card. Later I did fsck -f and remounted everything was OK. Anyway yes they forgot to rate limit that message. OK thanks. Which filesystem did you use on the SD card? Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
Control: severity -1 normal Control: notfound -1 3.11.10-1 Control: found -1 3.12.6-1 Control: clone -1 -2 Control: retitle -1 xhci_hcd 'Too many fragments' warning appears Control: retitle -2 xhci_hcd 'Too many fragments' warning should be rate-limited On Wed, 2014-01-01 at 07:33 +0800, jida...@jidanni.org wrote: Package: src:linux Version: 3.11.10-1 No, this message did not exist in that version. Severity: wishlist Whatever you do, please add some break out code. Do not just loop putting # grep -c xhci /var/log/syslog 1052792 lines of xhci_hcd :00:14.0: Too many fragments 79, max 63 swelling # ls -l /var/log/syslog -rw-r- 1 root adm 107977515 01-01 07:17 /var/log/syslog Is any other error message logged? Which USB devices are you using (this is probably disk or network related)? Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#733826: crazy loop xhci_hcd Too many fragments
Package: src:linux Version: 3.11.10-1 Severity: wishlist Whatever you do, please add some break out code. Do not just loop putting # grep -c xhci /var/log/syslog 1052792 lines of xhci_hcd :00:14.0: Too many fragments 79, max 63 swelling # ls -l /var/log/syslog -rw-r- 1 root adm 107977515 01-01 07:17 /var/log/syslog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
