Hello Sarah, These were off, just the length3 patch, and some stuff under kernel hacking. But i find it strange to get so much output, since it should quite fast stop from it self due to the return -ESHUTDOWN; shouldn't it ? -- Sander Tuesday, August 10, 2010, 10:36:03 PM, you wrote: > On Tue, Aug 10, 2010 at 10:21:10PM +0200, Sander Eikelenboom wrote: >> Hi Sarah, >> >> Just triend on 2.6.35 final + isoc patches and debugfs and some debug options (kmemleak spinlock, dma-api) on. > Which debug options did you have turned on? If it was CONFIG_USB_DEBUG > and CONFIG_USB_XHCI_HCD_DEBUGGING, then you're going to have a lot of > output. You should be able to turn off CONFIG_USB_XHCI_HCD_DEBUGGING. >> On baremetal, so without xen interfering. >> But it seems to be even worse than with Xen ... The console gets completely flooded with the >> >> >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c60e0 2082c7b4 00000000 00040b4c 80001424 >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c60f0 20840000 00000000 00040b4c 80001424 >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c6100 20840b4c 00000000 00040b4c 80001424 >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c6110 20841698 00000000 00040b4c 80001424 >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c6120 208421e4 00000000 00040b4c 80001424 >> Aug 10 22:01:01 localhost kernel: [ 322.691778] xhci_hcd 0000:04:00.0: @206c6130 20842d30 00000000 00040b4c 80001424 >> >> And i had a hard time stopping ffmpeg from grabbing. > What do you mean by "hard time"? Like the program wouldn't quit, or the > system was not responsive because of the excess debug messages, or ? > Sarah Sharp -- Best regards, Sander mailto:linux@xxxxxxxxxxxxxx -- 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
