On Wed, Mar 26, 2003 at 10:52:36AM -0800, Greg KH wrote:
> On Wed, Mar 26, 2003 at 04:25:38PM +0000, Chris Sykes wrote:
> > However it is easy to cause the BUG by simply:
> >
> > bash # echo "Some string" >/dev/ttyUSB0
>
> The oops happens on close(), right? To verify this try:
Yes it would seem so.
> cat /dev/ttyUSB0
> no oops should happen until you interrupt this.
>
> Anyway, this is a known usb-serial bug right now. It should be fixed in
> the 2.5 tree, but I haven't had enough people test that code out to know
> if this is really true (I can't duplicate the bug on 2.4 myself.)
I seem to have worked around it for now. I've jumpered the hardware
to stop it from echoing what you transmit back locally and all seems
OK now.
> Can you test 2.5 to see if this is fixed there for you or not?
I can test it yes, but 2.5 may be a bit too unstable for our
production use ATM.
Anyway I'll test out a 2.5 kernel when I'm back in the office
tomorrow, I can devote some time to tracking down the problem if you
can give me some pointers on where to start. I'd like to be able to
feel confident that this will work reliably under 2.4, otherwise I
guess I need to look for alternate solutions.
Thanks for your help,
--(o- Chris Sykes -- GPG Key: http://www.sigsegv.plus.com/key.txt //\ "Don't worry. Everything is getting nicely out of control ..." V_/_ Douglas Adams - The Salmon of Doubt
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:25 EST