On Thu, 17 Nov 2005, Jan Kiszka wrote:
> You mean something like this:
>
> khubd D 003D446F 0 1749 6 5752 692 (L-TLB)
> ccfade98 bec52600 003d446f ccefd688 ccefd560 bec52600 003d446f
> c0316a60 ccfadea8 00f94b77 cdb57800 cdb578e0
> c0
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.
>>
>>Next step?
>
>
> Unfortunately the stack trace
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.
>
> Next step?
Unfortunately the stack trace doesn't mention khubd. Undoubte
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
>>sit aside my box all the time...) still contain valuable
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
> sit aside my box all the time...) still contain valuable information? Or
> shou
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. So the
>> high-level driver se
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. So the
> high-level driver seems to be out of the game
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. Could you try the patch
>>>I've attached, to see if it prints
> > > 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 are as far as I can tell always with VIA hardware. I have
> > no idea what causes them.
>
> Any chance t
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. Could you try the patch
> > I've attached, to see if it prints anything?
> >
>
> Addit
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
On Monday 14 November 2005 20:39, 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 are a
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 are as far as I can tell always wit
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
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 are as far as I can tell always with VIA hardware. I have
no idea w
On Mon, 14 Nov 2005, 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 is like this:
>
> kernel: hub 4-0:1.0: state 5 ports 6 chg evt 0008
> kernel: ehc
On Mon, Nov 14, 2005 at 07:36:13PM +0100, Jan Kiszka wrote:
> 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 dis
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 after longer
operation times. Typically, there is no USB loa
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 after longer
> >> operation times. Typically, there is no USB load when it disconne
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 is like this:
>>
>> kernel: hub 4-0:1.0: state
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 is like this:
>
> kernel: hub 4-0:1.0: state 5 ports 6 chg ev
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
23 matches
Mail list logo
