On Fri, 3 Feb 2012, Christian Janoff wrote: > Hi there! > > I'm running a VDR installation on an Asus EEE PC 701. > > This is what I get once (sometimes twice) a day: ... > Feb 3 14:14:23 localhost vdr: [14791] read incomplete section - len = > 93, r = 555 > Feb 3 14:14:32 localhost kernel: [232621.634959] ehci_hcd 0000:00:1d.7: > fatal error > Feb 3 14:14:32 localhost kernel: [232621.634981] ehci_hcd 0000:00:1d.7: > fatal command 0010020 (park)=0 ithresh=1 Async period=1024 HALT > Feb 3 14:14:32 localhost kernel: [232621.634996] ehci_hcd 0000:00:1d.7: > fatal status b019 Async Recl Halt FATAL FLR INT > Feb 3 14:14:32 localhost kernel: [232621.635003] ehci_hcd 0000:00:1d.7: > reset command 0010022 (park)=0 ithresh=1 Async period=1024 Reset HALT > Feb 3 14:14:32 localhost kernel: [232621.635003] ehci_hcd 0000:00:1d.7: > HC died; cleaning up ... > The Netbook always runs with its power supply plugged in. Besides > this error, the VDR runs fine. But it's not reliable. I have to > reboot it daily. What happens if you do "rmmod ehci-hcd ; insmod ehci-hcd" when the error occurs instead of rebooting? > I also enabled "USB verbose debug messages" in the kernel > but the messages above is all I got. The EEE PC has 3 USB > connectors. It doesn't matter where I plug in the devices. The output from dmesg might or might not contain more information. It will be more reliable than the system log, in any case. What happens if you use the devices on a different computer? > I also tried new (better) USB cables. No change. > > Is there a way to find out why this happens? Not all that easy. One thing you can do is go into /sys/kernel/debug/usb/ehci/0000:00:1d.7/ and post the contents of the files you find there immediately after the error occurs. 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
