Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-26 Thread Johann Klammer
Alan Stern wrote: Can you put the usbmon trace on a web server like pastebin.com? Pastebin chickens out with: `413 Request Entity Too Large` The dump is around 2.5 Mib. Most of it probably the dvb stream. Have now recompiled the kernel with more debug output and will try to reproduce the

Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-26 Thread Johann Klammer
Alan Stern wrote: This is probably a low-level hardware error. Interference between the two ports of some kind. This is quite possible. Have been able to produce a more verbose logfile snippet. [25045.734288] af9013_update_ber_unc: err bits:1286 total bits:1632 abort count:0

Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-26 Thread Alan Stern
On Sat, 26 Nov 2011, Johann Klammer wrote: Alan Stern wrote: This is probably a low-level hardware error. Interference between the two ports of some kind. This is quite possible. Have been able to produce a more verbose logfile snippet. The log shows that your EHCI controller reports

Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-26 Thread Malcolm Priestley
On Fri, 2011-11-25 at 03:21 +0100, Johann Klammer wrote: When using a DVB-T Dongle and an external HDD simultaneously, EHCI almost always disconnects. Ideally HDD, and DVB devices shouldn't share the the same controller. Most systems have two. However, it is difficult for users know how

Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-26 Thread Johann Klammer
Alan Stern wrote: This could be the result of an electrical glitch or power fluctuation. Are these devices bus-powered? The DVB Stick is. The HDD is not. Or it could simply be something wrong with your EHCI controller. Possible. The power supply is old, too and there's a telephone in the

Re: PROBLEM: EHCI disconnects DVB HDD

2011-11-25 Thread Alan Stern
On Fri, 25 Nov 2011, Johann Klammer wrote: When using a DVB-T Dongle and an external HDD simultaneously, EHCI almost always disconnects. When tuning, it works for some time, but after a while, probably triggered by disk activity the dmesg log fills up with disk errors and failed i2c