[Added David Brownell to the CC: since his patch evidently doesn't fix
the ehci_endpoint_disable hang.]
On Thu, 2 Feb 2006, Jan Kiszka wrote:
Alan Stern wrote:
On Sat, 31 Dec 2005, Scott D. Davilla wrote:
A stack trace (Alt-SysRq-T) showing exactly _where_ the khubd process
is
David Brownell wrote:
On Thursday 02 February 2006 7:05 am, Alan Stern wrote:
[Added David Brownell to the CC: since his patch evidently doesn't fix
the ehci_endpoint_disable hang.]
No, there still seems to be some issue where the IAA watchdog timer is
not having the intended effect. It
On Mon, 2 Jan 2006, Scott D. Davilla wrote:
I've heard about this bit before. In my experience with VIA UHCI
controllers it has always been set to 1 -- but I don't have a motherboard
with a VIA chipset.
That option should be set in any case. You may not need to ignore the
babble/EOF2
More information about this;
GetStatus port 2 status 00180b POWER sig=j PEC CSC CONNECT
I added some code to do a 10us delayed double read of the port status
and it's the same so the status of 00180b is true. The important part
of the port status is the lower nibble 0xb, that's bit's 0, 1
On Sun, 1 Jan 2006, Scott D. Davilla wrote:
More information about this;
GetStatus port 2 status 00180b POWER sig=j PEC CSC CONNECT
I added some code to do a 10us delayed double read of the port status
and it's the same so the status of 00180b is true. The important part
of the port
I've heard about this bit before. In my experience with VIA UHCI
controllers it has always been set to 1 -- but I don't have a motherboard
with a VIA chipset.
That option should be set in any case. You may not need to ignore the
babble/EOF2 error; the higher-level USB protocols ought to be
On Fri, 23 Dec 2005, Scott D. Davilla wrote:
Disconnect after 6 days, 4 hours. Here's the log. It looks like the
familiar sporadic root hub disconnect. I suspect that there is a
sporadic condition where the root hub indicates a disconnect but the
disconnect is bogus. Can someone explain or
On Fri, 23 Dec 2005, Scott D. Davilla wrote:
Disconnect after 6 days, 4 hours. Here's the log. It looks like the
familiar sporadic root hub disconnect. I suspect that there is a
sporadic condition where the root hub indicates a disconnect but the
disconnect is bogus. Can someone explain or
On Fri, 23 Dec 2005, Scott D. Davilla wrote:
The hub driver periodically queries ehci-hcd to get port status changes.
When the hardware reports a connect status change, the hub driver
processes the change. There aren't any hardware interrupts involved; it's
driven by a kernel timer. But
Via usb controllers are known to have problems :(
If you insert a ehci pci card in the machine, does the same problem
happen?
Not possible, the one PCI slot is occupied with a gigabit network
card. We can't lose the gigabit so even if a pci ehci card solved the
issue, we get a different
We too are having long term problems with a spontaneous USB
disconnect hanging khubd. The only way to fix is a reboot. The
hardware is VIA EPIA 1GHz Nehemiah running a stock 2.6.14.3 kernel
with latest 117 test VIA bios. It's not a specific USB driver problem
as is occurs with various USB
On Thu, Dec 15, 2005 at 01:16:24PM -0500, Scott D. Davilla wrote:
We too are having long term problems with a spontaneous USB
disconnect hanging khubd. The only way to fix is a reboot. The
hardware is VIA EPIA 1GHz Nehemiah running a stock 2.6.14.3 kernel
with latest 117 test VIA
12 matches
Mail list logo
