Launchpad has imported 23 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=431379.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-02-03T21:50:51+00:00 Dmitry wrote: Description of problem: When trying to "sysread" (perl script) from a AT91xx-based GPS device, connected via "usbserial" kernel module, the system freezes. Nothing seems to work, besides the "Reset" button. Examining the messages file after a reboot reveals nothing. Version-Release number of selected component (if applicable): kernel version: 2.6.23.14-107 How reproducible: every time the sysread is called Steps to Reproduce: 1. Connect the "Gisteq PhotoTrackr Lite" device via USB cable 2. Run "modprobe usbsusbserial vendor=0x03EB product=0x6126" 3. Run a script containing a "sysread" command from previously opened stream Actual results: The system freezes. Expected results: The same script, on the same computer/port/cable/device combination, running Knoppix 5.1.1 Live DVD, continues to run and produces the expected output. Additional info: The Knoppix DVD runs kernel version 2.6.19(.1). The original perl script, causing the system freeze, can be downloaded from it's author's site: http://schimmelnetz.de/projekte/iTU4l/download/iTU4l.pl Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/0 ------------------------------------------------------------------------ On 2008-02-03T21:50:51+00:00 Dmitry wrote: Created attachment 293841 Perl script for reading raw data from AT91xx based GPS-Loggers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/1 ------------------------------------------------------------------------ On 2008-02-07T22:32:59+00:00 Dmitry wrote: I've just checked it with the last 2.6.23.14-115 kernel version. Unfortunately, with the same results: complete system freeze. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/2 ------------------------------------------------------------------------ On 2008-02-14T03:02:16+00:00 Pete wrote: It is vital to convert the freeze into an oops (with NMI watchdog). But first... Dmitry, did you try this on the text console (Alt-F1)? What does happen in that case? No messages? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/3 ------------------------------------------------------------------------ On 2008-02-16T22:37:24+00:00 Dmitry wrote: When running from a console, I just got the script printing the "Opened /dev/ttyUSB0" message, immediately followed by system freeze. When booting with "nmi_watchdog=1", the NMI dumped on the screen some info, but the system still got completely unresponsive - with just "Caps Lock" and "Scroll Lock" flashing. I had to reboot it with the "reset" switch, and next time added "panic=10" to the boot options, which worked. But unfortunately, the "messages" file doesn't contain any helpful information regarding the lockup: the last message recorded there is about new usbserial device connected on /dev/ttyUSB0. Anyway, as I myself have absolutely no experience in kernel debugging, I'll be happy to follow your further recommendations, and to inform you on the results. Thanks ahead. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/4 ------------------------------------------------------------------------ On 2008-02-22T21:39:23+00:00 Dmitry wrote: I've tried it on 2.6.23.15-137 - with the same results :-( Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/5 ------------------------------------------------------------------------ On 2008-03-03T19:01:40+00:00 Dmitry wrote: Created attachment 296661 NMI watchdog screenshot Well, I felt really silly doing this, but I really didn't know any better way: attached is the screenshot (literally!) of what happened when the system became frost. After this, only the reset button worked. I hope it will provide you some clue on what's going on, or at least any idea on how to get some more information. Thanks ahead. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/6 ------------------------------------------------------------------------ On 2008-03-03T21:06:04+00:00 Chuck wrote: Can you capture that with the console in 50-line mode (vga=1) or framebuffer mode (vga=791)? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/7 ------------------------------------------------------------------------ On 2008-03-03T21:59:32+00:00 Dmitry wrote: Created attachment 296683 NMI watchdog screenshot in fb mode Here it is: the screen captured in fb mode. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/8 ------------------------------------------------------------------------ On 2008-03-05T05:00:04+00:00 Pete wrote: Awesome, thanks a lot. The traditional answer is, the generic usb-serial is not useable this way and it _will_ lock up (depending on settings of setserial /dev/ttyUSB0 low_latency perhaps). The solution is to beat those who suggest "modprobe usbsusbserial vendor=0x03EB product=0x6126" with a stick with rusty nails; suggest them to propose patches to real subdrivers (e.g. pl2303). However, I always wanted to see a case of it actually locking up with a traceback, so thanks. I may be able to fix this now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/10 ------------------------------------------------------------------------ On 2008-03-05T07:21:58+00:00 Pete wrote: Created attachment 296859 Fix for recursive lock-taking This seems too simple to be true. I'll poke Greg K-H about it. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/11 ------------------------------------------------------------------------ On 2008-03-05T17:25:39+00:00 Dmitry wrote: Thanks a lot, I hope your patch will fix it. How can I test it? Can you attach compiled module for 2.6.23.15-137 kernel release? It's been at least 5 years since I've compiled a kernel myself, and I'm not sure I still can do it properly - without inserting any artifacts of my own :-( Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/12 ------------------------------------------------------------------------ On 2008-03-05T17:48:01+00:00 Pete wrote: I have submitted the patch upstream, so there's going to be a discussion and a decision if the solution is appropriate. If outcome is positive, the patch recirculates through upstream. If Chuck threw it into Fedora pool for testing, it would be great. Dmitry, I have a request: please attach your /proc/bus/usb/devices. Maybe I can add your GPS to a proper driver as I mentioned in comment #9. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/13 ------------------------------------------------------------------------ On 2008-03-05T18:05:22+00:00 Dmitry wrote: Created attachment 296903 /proc/bus/usb/devices Done. The GPS is the on with Vendor=03eb and ProdID=6126 Thanks again. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/14 ------------------------------------------------------------------------ On 2008-03-05T21:49:17+00:00 Pete wrote: David Brownell suggested that cdc-acm should be able to drive this device. It's apparently commonplace for CDC devices to straddle two interfaces (I thought that only CDC RNDIS did it, but I guess not). Dmitry, please do this: rmmod usbserial # rmmod dependencies first if this fails modprobe cdc_acm dmesg | tail -40 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/15 ------------------------------------------------------------------------ On 2008-03-05T22:05:13+00:00 Dmitry wrote: Here is the (relevant) output: usb 2-1: new full speed USB device using uhci_hcd and address 4 usb 2-1: configuration #1 chosen from 1 choice usbcore: registered new interface driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbserial_generic 2-1:1.0: generic converter detected usbserial_generic 2-1:1.0: Generic device with no bulk out, not allowed. usbserial_generic: probe of 2-1:1.0 failed with error -5 usbserial_generic 2-1:1.1: generic converter detected usb 2-1: generic converter now attached to ttyUSB0 usbcore: registered new interface driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core usbcore: deregistering interface driver usbserial_generic generic ttyUSB0: generic converter now disconnected from ttyUSB0 usbserial_generic 2-1:1.1: device disconnected drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic usbcore: deregistering interface driver usbserial usbcore: registered new interface driver cdc_acm drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/16 ------------------------------------------------------------------------ On 2008-03-05T22:29:49+00:00 Dmitry wrote: Created attachment 296951 Pete's patch adapted to 2.6.23.15 kernel version Awesome! Pete, thank you very much: the problem is solved! I've just rebuild the 2.6.23.15-137 kernel with your patch applied (adapted to the earlier kernel version), and it solved the problem. The computer didn't freeze, and I finally was able to download the memory dump from my GPS gadget. So, on my part, I can recommend including this patch to the upcoming kernel release :-) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/17 ------------------------------------------------------------------------ On 2008-03-06T20:33:23+00:00 Hartmut wrote: Thank you very much ! As the author of the GPS logger read-out perl script (http://itu4l.schimmelnetz.de), with which the problem cames up I hope, you pack away the stick with rusty nails now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/18 ------------------------------------------------------------------------ On 2008-03-08T15:06:15+00:00 Dmitry wrote: I tried your patch (the original one from comment #10) with the newly released kernel 2.6.24.3-12.fc8, and again it worked like a charm. One remark though: I'm not sure it's somehow related to the current discussion, but with this kernel any attempt to set the baud rate to anything bigger then the default 9600 failed with "stty: /dev/ttyUSB0: unable to perform all requested operations". It didn't bother me much: the GPS's memory wasn't that big. But if it is bug-related, may be it'll help with your patch evaluation. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/20 ------------------------------------------------------------------------ On 2008-03-10T22:28:00+00:00 Chuck wrote: Fixed in 2.6.24.3-26. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/21 ------------------------------------------------------------------------ On 2008-03-13T21:58:23+00:00 Fedora wrote: kernel-2.6.24.3-34.fc8 has been submitted as an update for Fedora 8 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/22 ------------------------------------------------------------------------ On 2008-03-16T19:27:49+00:00 Fedora wrote: kernel-2.6.24.3-34.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/23 ------------------------------------------------------------------------ On 2008-03-16T23:27:39+00:00 Dmitry wrote: Can confirm: kernel-2.6.24.3-34.fc8 is working (still, the baud rate restricted as mentioned in comment #18). The bug should stay closed. Thank you all for the help! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/comments/24 ** Changed in: linux (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/198546 Title: freeze after trying to read from /dev/ttyUSB0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Hardy: Won't Fix Status in linux package in Fedora: Fix Released Bug description: Binary package hint: linux-source 1) Tried with both latest Ubuntu and Kubuntu 8.04 hardy alphas (as of March, 4th) 2) linux kernel 3) Version: 2.6.24.11.11 4) I was trying to get data from a gps tracker, which needed usbserial, using the instructions on a that website: http://schimmelnetz.de/projekte/iTU4l/ Here is what I did, in a nutshell: * lsusb showed: Bus 003 Device 005: ID 03eb:6126 Atmel Corp. * Added to /etc/modprobe.d/options: options usbserial vendor=0x03EB product=0x6126 * Added to /etc/udev/rules.d/66-atmel-usb.rules: SUBSYSTEM=="usb", SYSFS{idProduct}=="6126", SYSFS{idVendor}=="03eb", RUN+="/sbin/modprobe usbserial" * Connected the device, lsmod showed: usbserial 35816 0 * Tried to read data from it, using Hartmut Schimmel's tool iTU4l.pl: http://schimmelnetz.de/projekte/iTU4l/download/iTU4l.pl * The tool does a sysread and was expected to get some result back 5) Computer freezed Note: the same setup works if I boot the latest 2.6.22 kernel I had from gutsy: 2.6.22-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
