On Mon, 21 Feb 2011, Sarah Sharp wrote: > On Mon, Feb 21, 2011 at 05:35:47PM +0200, Tanya Brokhman wrote: > > Hi Sarah > > > > > That particular error is from the host side. It means the xHCI driver > > > tried to move the ring dequeue pointer past the last part of your > > > command (probably the status phase), and the host refused to do so, > > > because that was the "active" stream ID. Can you please send me the > > > full dmesg for the stalled request with CONFIG_USB_XHCI_HCD_DEBUGGING > > > turned on? > > > > Np. I've already overcame this issue but I'll roll back and send you the > > dmesg output. When I tried enabling this flag the dmesg was swamped with > > xhci messages and the messages I was looking for weren't there already. > > I read that in order to increase the dmesg buffer size one needs to update > > the #define of LOG_BUF_LEN in linux/kernel/printk.c. I haven't tried that > > yet. Is this correct? The appropriate way to change this value is by updating the kernel configuration. The value is set by CONFIG_LOG_BUF_SHIFT (General setup / Kernel log buffer size, if you use "make menuconfig"). > There will be a lot of messages, but you can capture them by running > this command line: > > tail -f /var/log/kern.log | tee logfile.txt This is not as reliable as using dmesg. When a lot of messages are generated very quickly, the log daemons often drop some of them. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
