Bug 108605
| Summary: | Oops on USB serial disconnect | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charlie Brady <charlieb-fedora-bugzilla> |
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | davej, monkiki5, weisen+rh-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-12-07 06:35:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Charlie Brady
2003-10-30 16:32:20 UTC
Same problem on a Thinkpad T40p w/ Fedora Core 1. Driving me nuts. I wonder if this is a relevant patch. I tried patching, but right now the Fedora kernel source package doesn't build for me. Haven't been able to track that down yet. http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg15835.html The patch referenced in my comment above appears to have fixed the problem. I had to add the patch manually to usbserial.c, but it seems to have fixed the oops. It was quite reproducible on my system... basically the first disconnect on a ttyUSB would kill off the usbserial driver and then it couldn't be used or unloaded until next reboot. I have the same bug when disconnection my iPAQ h1930. Does the same happen on 2.4.22-1.2140? If yes, please attach dmesg taken after the fault (dmesg > /tmp/dmesg.out). Please DO NOT drop it in the comments box. This bug is fixed in kernel 2.4.23. The modified file is drivers/usb/serial/usbserial.c Cheers! Charlie, ignore Paco and answer my request, please :-) I know that 2.4.23 works. I need to know if what I backported from 2.4.23 worked or something else is needed. I'm using the last kernel (2.4.22-1.2149.nptl) and my iPAQ doesn't work well :-( This is the kernel message: ---------------------------------------------------------------------- Jan 26 23:03:56 antares devlabel: devlabel service started/restarted Jan 26 23:04:02 antares pppd[9178]: pppd 2.4.1 started by root, uid 0 Jan 26 23:04:03 antares pppd[9178]: Serial connection established. Jan 26 23:04:03 antares pppd[9178]: Using interface ppp0 Jan 26 23:04:03 antares pppd[9178]: Connect: ppp0 <--> /dev/ttyUSB0 Jan 26 23:04:03 antares modprobe: modprobe: Can't locate module ppp-compress-21 Jan 26 23:04:03 antares kernel: PPP Deflate Compression module registered Jan 26 23:04:03 antares modprobe: modprobe: Can't locate module ppp-compress-21 Jan 26 23:04:03 antares pppd[9178]: local IP address 192.168.131.102 Jan 26 23:04:03 antares pppd[9178]: remote IP address 192.168.131.201 Jan 26 23:04:18 antares kernel: usbserial.c: too much data (101) Jan 26 23:04:18 antares kernel: usbserial.c: too much data (100) Jan 26 23:04:18 antares kernel: usbserial.c: too much data (100) Jan 26 23:04:19 antares kernel: usbserial.c: too much data (108) ---------------------------------------------------------------------- I can't browse iPAQ filesystem because of this error: "too much data". The solution exposed on comment #5 is better. And when I unplug USB from iPAQ, my computer locks up! fc1 - eol |