* [9fans] usbuhci bug
@ 2011-09-01 15:44 erik quanstrom
2011-09-01 16:31 ` Gorka Guardiola
0 siblings, 1 reply; 5+ messages in thread
From: erik quanstrom @ 2011-09-01 15:44 UTC (permalink / raw)
To: 9fans
speaking of usb ...
using a serial-to-usb converter and usb/serial, i've been able to
put my terminal into an unusable state on a fairly regular basis.
here's the step-by-step.
1. run usb/serial
2. wait for a usb disconnect due to a failed read
3. notice that your machine is having trouble scheduling.
4. note that usbuhci is blasting 100,000 interrupts/sec!
5. try to slay and restart usb/serial ... no joy there.
6. give up and reboot terminal.
unfortunately, i don't have any time to dig into this one atm.
- erik
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] usbuhci bug
2011-09-01 15:44 [9fans] usbuhci bug erik quanstrom
@ 2011-09-01 16:31 ` Gorka Guardiola
2011-09-01 16:35 ` erik quanstrom
0 siblings, 1 reply; 5+ messages in thread
From: Gorka Guardiola @ 2011-09-01 16:31 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
Can you send me off-list usb/serial -dd output. At least so I know what device we are talking about :-).
On Sep 1, 2011, at 5:44 PM, erik quanstrom <quanstro@labs.coraid.com> wrote:
> speaking of usb ...
>
> using a serial-to-usb converter and usb/serial, i've been able to
> put my terminal into an unusable state on a fairly regular basis.
>
> here's the step-by-step.
> 1. run usb/serial
> 2. wait for a usb disconnect due to a failed read
> 3. notice that your machine is having trouble scheduling.
> 4. note that usbuhci is blasting 100,000 interrupts/sec!
> 5. try to slay and restart usb/serial ... no joy there.
> 6. give up and reboot terminal.
>
> unfortunately, i don't have any time to dig into this one atm.
>
> - erik
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] usbuhci bug
2011-09-01 16:31 ` Gorka Guardiola
@ 2011-09-01 16:35 ` erik quanstrom
2011-09-01 20:06 ` Gorka Guardiola
[not found] ` <CACm3i_hSQNXe0dU91QgXfFX1oroByPaGKm-DPSOH+tBx6i+_=g@mail.gmail.c>
0 siblings, 2 replies; 5+ messages in thread
From: erik quanstrom @ 2011-09-01 16:35 UTC (permalink / raw)
To: 9fans
> > 5. try to slay and restart usb/serial ... no joy there.
i should have been more clear. restarting usb/serial worked
fine. the interrupt problem didn't go away.
- erik
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [9fans] usbuhci bug
2011-09-01 16:35 ` erik quanstrom
@ 2011-09-01 20:06 ` Gorka Guardiola
[not found] ` <CACm3i_hSQNXe0dU91QgXfFX1oroByPaGKm-DPSOH+tBx6i+_=g@mail.gmail.c>
1 sibling, 0 replies; 5+ messages in thread
From: Gorka Guardiola @ 2011-09-01 20:06 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Thu, Sep 1, 2011 at 6:35 PM, erik quanstrom <quanstro@labs.coraid.com> wrote:
>> > 5. try to slay and restart usb/serial ... no joy there.
>
> i should have been more clear. restarting usb/serial worked
> fine. the interrupt problem didn't go away.
>
Hmm, but the old usb/serial dies/is killed?. Because it is a very
different problem (in one case it
is most probably a serial problem in the other it is an ehci problem
or hardware).
Another question is, the fail read is because the serial is unplugged
or a hardware
issued error?.
Thanks,
G.
^ permalink raw reply [flat|nested] 5+ messages in thread[parent not found: <CACm3i_hSQNXe0dU91QgXfFX1oroByPaGKm-DPSOH+tBx6i+_=g@mail.gmail.c>]
* Re: [9fans] usbuhci bug
[not found] ` <CACm3i_hSQNXe0dU91QgXfFX1oroByPaGKm-DPSOH+tBx6i+_=g@mail.gmail.c>
@ 2011-09-01 20:10 ` erik quanstrom
0 siblings, 0 replies; 5+ messages in thread
From: erik quanstrom @ 2011-09-01 20:10 UTC (permalink / raw)
To: paurea, 9fans
On Thu Sep 1 16:08:21 EDT 2011, paurea@gmail.com wrote:
> On Thu, Sep 1, 2011 at 6:35 PM, erik quanstrom <quanstro@labs.coraid.com> wrote:
> >> > 5. try to slay and restart usb/serial ... no joy there.
> >
> > i should have been more clear. restarting usb/serial worked
> > fine. the interrupt problem didn't go away.
> >
>
> Hmm, but the old usb/serial dies/is killed?. Because it is a very
> different problem (in one case it
> is most probably a serial problem in the other it is an ehci problem
> or hardware).
>
> Another question is, the fail read is because the serial is unplugged
> or a hardware
> issued error?.
it is a hardware issued error. the serial was in the same state overnight.
it was also interesting that unplugging the serial dongle didn't fix the
interrupt problem either.
- erik
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-09-01 20:10 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-01 15:44 [9fans] usbuhci bug erik quanstrom
2011-09-01 16:31 ` Gorka Guardiola
2011-09-01 16:35 ` erik quanstrom
2011-09-01 20:06 ` Gorka Guardiola
[not found] ` <CACm3i_hSQNXe0dU91QgXfFX1oroByPaGKm-DPSOH+tBx6i+_=g@mail.gmail.c>
2011-09-01 20:10 ` erik quanstrom
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).