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.
Alan Stern wrote:
> On Tue, 15 Nov 2005, Jan Kiszka wrote:
>
>
>>Trace attached. One ehci_endpoint_disable call actually does not return.
>>
>>I furthermore had my box running without ehci for about 8 hours today,
>>and no disconnect occured.
>>
>>Nex
Alan Stern wrote:
> On Tue, 15 Nov 2005, Jan Kiszka wrote:
>
>
>>>And get that stack trace. It's the best way to find the exact location of
>>>the problem.
>>>
>>
>>Will the trace I request typically hours after the disconnect (I can't
Alan Stern wrote:
> On Tue, 15 Nov 2005, Jan Kiszka wrote:
>
>> I placed some printks in the rt2570's disconnect routine. While I can
>> find them in the logs when I physically disconnect the stick, I did not
>> get them last night during another sporadic disconnect
Alan Stern wrote:
> ...
> The hang is almost certainly caused by the device's driver. Apparently
> its disconnect method is not returning. Since that routine is called by
> the main hub driver and with a lock held, this means that most other major
> activities of the USB stack will be blocked
David Brownell wrote:
> On Monday 14 November 2005 12:58 pm, Jan Kiszka wrote:
>
>>David Brownell wrote:
>>
>>>...
>>>EBUSY status code happens in a few cases, and in this path I'd suspect
>>>it means the URB is already being returned. Coul
David Brownell wrote:
> ...
> EBUSY status code happens in a few cases, and in this path I'd suspect
> it means the URB is already being returned. Could you try the patch
> I've attached, to see if it prints anything?
>
Additional question regarding this check: should this warning never show
up
David Brownell wrote:
> On Monday 14 November 2005 9:35 am, Jan Kiszka wrote:
>
>>ehci_hcd :00:10.3: GetStatus port 3 status 00180b POWER sig=j PEC CSC
>>CONNECT
>
>
> Translation: the root hub spontaneously disconnected. There are such
> reports, which a
Alan Stern wrote:
> ...
> The hang is almost certainly caused by the device's driver. Apparently
> its disconnect method is not returning. Since that routine is called by
> the main hub driver and with a lock held, this means that most other major
> activities of the USB stack will be blocked
Greg KH wrote:
> On Mon, Nov 14, 2005 at 06:54:17PM +0100, Jan Kiszka wrote:
>> Greg KH wrote:
>>> On Mon, Nov 14, 2005 at 06:35:22PM +0100, Jan Kiszka wrote:
>>>> Hi,
>>>>
>>>> on a VIA Eden box, I'm getting sporadic USB disconnects af
Greg KH wrote:
> On Mon, Nov 14, 2005 at 06:35:22PM +0100, Jan Kiszka wrote:
>> Hi,
>>
>> on a VIA Eden box, I'm getting sporadic USB disconnects after longer
>> operation times. Typically, there is no USB load when it disconnects.
>> The kernel output i
Hi,
on a VIA Eden box, I'm getting sporadic USB disconnects after longer
operation times. Typically, there is no USB load when it disconnects.
The kernel output is like this:
kernel: hub 4-0:1.0: state 5 ports 6 chg evt 0008
kernel: ehci_hcd :00:10.3: GetStatus port 3 status 00180b POWER
12 matches
Mail list logo
