Greg KH wrote:
On Tue, Oct 26, 2010 at 05:53:14PM +0200, XI wrote:
Hi, there seems to be a regression in latest kernels regarding Edgeport
USB <-> serial devices.
*** Problem description:
I use USB <-> Serial converters from Inside Out Networks (model
Edgeport 4S & Edgeport 8S, kernel driver io_ti)
Since kernel 2.6.33, disconnecting the USB plug of the device _while
a transfer is in progress_ cause severe problem to the Linux kernel:
-> Kernel OOPS in 2.6.33.x to 2.6.34.x series (No USB device is
working after this Oops)
-> Computer hang in 2.6.36 (there is no Oops anymore but the
problem is even worst because the computer is stuck until I
reconnect the device / and sometimes forever)
-> Note: 2.6.35.x also fail but I don't remember if they produce an
Oops. Also note that 2.6.32.24 and previous works just fine.
Hm, can you run 'git bisect' between 2.6.32 and 2.6.33 to try to find
the problem patch that caused this issue?
thanks,
greg k-h
Hi,
I have run git bisect between 2.6.32 and v2.6.33. Git result is below :
"
git bisect bad
e1108a63e10d344284011cccc06328b2cd3e5da3 is the first bad commit
commit e1108a63e10d344284011cccc06328b2cd3e5da3
Author: Alan Cox <alan@xxxxxxxxxxxxxxx>
Date: Tue Oct 6 16:06:36 2009 +0100
usb_serial: Use the shutdown() operation
As Alan Stern pointed out - now we have tty_port_open the shutdown
method and locking allow us to whack the other bits into the full helper
methods and provide a shutdown op which the tty port code will
synchronize with setup for us.
Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx>
Cc: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Cc: Oliver Neukum <oliver@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
:040000 040000 415f5c46a1bb71a4fe6f7d76ab3149e955ef0ed6
561d8a0423a9f996eebffed326eeb2ced14ef046 M drivers
"
It seems related to my problem since the OOPS occurs when I disconnect
the Edgeport USB<->Serial device.
What do you think ?
Regards,
Xavier
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
