Hi, I found this patch causes troubles on 2.4.25-pre4 and also 2.4.24-rc2. Here is the resolved stack trace in "cr.res" file. :(
Some details. The usb0 had assigned an IP address and was up(not sure if that matters). In "dmesg" I saw several times: usb0: rxqlen 0 --> 1 NETDEV WATCHDOG: usb0: transmit timed out usbnet.c: usb0 tx: err -2
Then likely your PL-230x based cable really can't work without that reset. Prolific seems to have designed them to require some sort of handshaking with the host on the other end, but they did a poor job of documenting those requirements. (And it's not clear why any handshaking should be required either.)
I unplugged the usb cable and that triggered kernel panic. This bug manifests only with the patch applied. :(
Hmm, that's odd. But your stack trace was nonsense. Does a 2.6 kernel do the same thing? 2.6 should at least make it easier to report a sensible stack trace. I can't think of any reason such a change should trigger an oops in current kernels.
BTW:
I tried to use GEMBIRD USB-USB cable (UAU211), but it's not detected at all, possibly it has unsupported chipset. Any clue on that?
No, but it's quite possible it'd work if you just set it up to work like, say, the Belkin parts work ... especially if it's only got a pair of bulk endpoints. (Which is all such hardware really needs.)
- Dave
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
