Re: usb-serial ipaq kernel problem

From: Luiz Fernando N. Capitulino
Date: Wed May 31 2006 - 17:09:45 EST


On Tue, 30 May 2006 23:36:35 +0200
Frank Gevaerts <frank.gevaerts@xxxxxx> wrote:

| On Tue, May 30, 2006 at 05:52:08PM -0300, Luiz Fernando N. Capitulino wrote:
| > On Tue, 30 May 2006 19:48:21 +0200
| > Frank Gevaerts <frank.gevaerts@xxxxxx> wrote:
| >
| > | On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz Fernando N. Capitulino wrote:
| > | > On Tue, 30 May 2006 11:38:01 -0300
| > | > "Luiz Fernando N. Capitulino" <lcapitulino@xxxxxxxxxxxxxxx> wrote:
| > | >
| > | > If it ran _before_ the timeout expires with no timeout error it does not
| > | > depend. Then we can do the simpler solution: just kill the read urb in the
| > | > ipaq_open's error path.
| > |
| > | That seems to work.
| > | I also found that both the return in ipaq_write_bulk_callback and the
| > | flush_scheduled_work() in destroy_serial() are needed to get rid of the
| > | usb_serial_disconnect() bug.
| >
| > Then did you hit it with my patch?
| >
| > I'm just worried with the fact that you're hitting it with every
| > proposed fix. Maybe it's something else.
|
| I'm hitting it with either of the proposed fixes, but not when both are
| applied.

Is this still true? :)

--
Luiz Fernando N. Capitulino
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/