Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
This is just an interim report on what I have discovered so far. 1) The garmin gps serial connection uses on 3 signals: rx,tx and grnd which are taken to the 9-pin coonector as follows: Garmin etrek hc 9-pin -- - rx pin 3 tx pin 2 grndpin 5 All the other pins on the 9-pin RS232 connector seem to be open. I have run the usual gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx test on the old working kernel. The breakout box (a Cablefaker) shows activity on the rx, tx lines as expected. Trying the same on the failing 3.0.0-xx kernel, the breakout box shows no activity at all. Which suggests that gpsbabel is not managing to send anything to the gps at all. Rather than the gps failing to respond, it looks if nothing is sent in the first place. I do not know how the ark chip is connected to its male 9 pin connector: it is moulded plastic and there does not seem to be anyway to dismantle it. The plastic shell is slightly transparent, and it looks as if all 9 pins are soldered to the pcb, but that might just be for physical support. I have yet to check other aspects and get an oscilloscope on the signals, nor try the other experiments suggested, so this is partial and to be continued. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111001135954.GA2639@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Thu, Sep 29, 2011 at 04:35:31PM +0200, Bart Hartgers wrote: If you have a breakout-box, it would also be interesting to 'manually' toggle some signals, basically just short rxd and/or cts to gnd for a sec. That should trigger some messages in the log if the ark3116 module is loaded with debug=1. Some more results using the breakout box and a multimeter: 1) Garmin gps only connected; pin 2 (tx on gps) : -5.57 V pin 3 (rx on gps) : -0.64 V pin 2 (gps tx) pulls down to -3.26V with 245 \ohm and to -1.95V with 100 \ohm to grnd (pin 5). --- 2) Ark converter only: pin 2 (tx on gps, so rx on ark): 0.01V pin 3 (rx on gps) : 0.04V (Same results on both working failing kernel, module loaded). --- 3) Both ark and garmin attached and working. pin 2 (tx on gps) : 0.01V on module load pin 3 (rx on gps) : -5.52V on module load - Using gpsbabel under the old working kernel 2.6.32, activity is seen on both pins 2 3 (as expected): just multimeter at this stage. No activity visible with multimeter under the 3.0.0 kernel. --- Pulling down pin 2 (tx on gps, rx on ark) to grnd via 100 \ohm on working kernel with debug=1 gives Oct 1 17:17:49 elf kernel: [ 259.932936] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 003 ok Oct 1 17:17:49 elf kernel: [ 259.933521] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 004 ok Oct 1 17:17:49 elf kernel: [ 259.934542] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 005 ok Oct 1 17:17:49 elf kernel: [ 259.935536] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 006 ok Oct 1 17:17:49 elf kernel: [ 259.937855] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 007 1 bytes [0x03] Oct 1 17:17:49 elf kernel: [ 259.938541] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 008 ok Oct 1 17:17:49 elf kernel: [ 259.939534] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 009 ok Oct 1 17:17:49 elf kernel: [ 259.941517] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 010 ok Oct 1 17:17:49 elf kernel: [ 259.942629] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 011 ok Oct 1 17:17:49 elf kernel: [ 259.943545] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 012 1 bytes [0x03] Oct 1 17:17:49 elf kernel: [ 259.944520] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 013 ok Oct 1 17:17:49 elf kernel: [ 259.946321] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 014 1 bytes [0x00] Oct 1 17:17:49 elf kernel: [ 259.946529] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 015 ok Oct 1 17:17:49 elf kernel: [ 259.947543] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 016 1 bytes [0x00] Oct 1 17:17:49 elf kernel: [ 259.949517] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 017 ok Oct 1 17:17:49 elf kernel: [ 259.950526] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 018 1 bytes [0x01] Oct 1 17:17:49 elf kernel: [ 259.951526] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 019 ok Oct 1 17:17:49 elf kernel: [ 259.952526] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 020 1 bytes [0xB0] Oct 1 17:17:49 elf kernel: [ 259.953529] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 147 ok Oct 1 17:17:49 elf kernel: [ 259.954542] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 148 ok Oct 1 17:17:49 elf kernel: [ 259.955537] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 149 ok Oct 1 17:17:49 elf kernel: [ 259.956517] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 150 ok Oct 1 17:17:49 elf kernel: [ 259.957522] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 151 1 bytes [0x03] Oct 1 17:17:49 elf kernel: [ 259.958516] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: 152 ok Oct 1 17:17:49 elf kernel: [
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
I have just tried shorting pin 4 (rts ?) to ground under kernel-3.0.0. This with debug=1 on the module. Absolutely nothing in /var/log/debug or dmesq. I tried several times. So this seems to be a major difference from the old working modules. As for the explanation... Progress of a sort, I think. I just might get the 'scope out later this evening if I have time. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111001171145.GA2537@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sat, Oct 01, 2011 at 06:01:24PM +0100, ael wrote: 3) Both ark and garmin attached and working. pin 2 (tx on gps) : 0.01V on module load pin 3 (rx on gps) : -5.52V on module load Looks to me as if I reversed pins 2 3 above, although it is what I wrote down at the time... ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111001193821.GA2534@precise.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Thu, Sep 29, 2011 at 04:35:31PM +0200, Bart Hartgers wrote: Hi ael, I have a real RS232 port on a desktop (back at home now), so I guess I could connect from the netbook USB - ark3116 - RS232 desktop. I will have to see what cables I have, but I think I have a very old RS232 breakout box somewhere, so I can probably fix something up. I have found the breakout box. Unfortunately it is all 25 pin connectors, so I will have to dig out or make some 25 -- 9 pin cables. Make take a while... That would be great! Hopefully we can make some progress that way. I suppose I could use picoterm or similar to view the incoming data on the desktop: it is a while since I looked at those programs. I realized I made a mistake: the program I meant is called picocom. If you have a breakout-box, it would also be interesting to 'manually' toggle some signals, basically just short rxd and/or cts to gnd for a sec. That should trigger some messages in the log if the ark3116 module is loaded with debug=1. It is a very long time since I played with stty, statserial and such. So I may need to pore over man pages try and work out what I am doing. I seem to remember having using minicom at one time. I think one could set up the serial parameters from a menu, and otherwise it just worked as a terminal. Somewhere, I think I have the specification for the garmin connector, but I can trace the wires otherwise. I guess I will start there. It can't be very complicated. I suppose just using statserial while the garmin is attached to the ordinary RS232 port would at least reveal its initial state. Unfortunately a hard disc has just failed on one machine (it would have to be the boot disc..) and the latest xorg packages have decided to stop working properly on another machine, so I have my hands rather full just now... ) ael Thanks! Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110929154741.GA2693@conquest3.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/21 ael law_ence@ntlworld.com: I have just done another test. This because that garmin odd connector often fails to make proper contact. So in this case I first verified that I could use gpsbabel successfully with the old kernel, so confirming a proper connection. Then I just used $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 Hi ael, I finally managed to find some time to test this on my own hardware on 2.6.38. I do not have a garmin gps, so I connect my ark3116 to a second serial interface. I used the same gpsbabel command as you to connect to my ark3116, and I could see data coming in on the second port and if I sent a reply the other way, it is received by gpsbabel. In short, everything seems to work as it should, which is not helping. Your traces show that gpsbabel never receives anything in your case, so somehow something is behaving different. I am running out of ideas. Would it be possible for you to do a similar experiment with a second serial port? That way we might learn if data actually makes it to the serial output when sending or if data is received on the serial input but not forwarded to the USB bus. Another thing to try could be to use picoterm or some other terminal program to send some characters to the gps (9600N8), to see what happens, and then directly afterwards try the gpsbabel command again. If the underlying problem has to do with somekind of timing mismatch, or initialisation problem, this might help. Thanks. Groeten, Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cak7h4ydudcvb0jtvt9h1ivaes6jtxppvctkq+ad+hwmesvr...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Wed, Sep 28, 2011 at 08:55:40PM +0200, Bart Hartgers wrote: 2011/9/21 ael law_ence@ntlworld.com: I have just done another test. This because that garmin odd connector often fails to make proper contact. So in this case I first verified that I could use gpsbabel successfully with the old kernel, so confirming a proper connection. Then I just used $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 Hi ael, I finally managed to find some time to test this on my own hardware on 2.6.38. I do not have a garmin gps, so I connect my ark3116 to a second serial interface. I used the same gpsbabel command as you to connect to my ark3116, and I could see data coming in on the second port and if I sent a reply the other way, it is received by gpsbabel. In short, everything seems to work as it should, which is not helping. Your traces show that gpsbabel never receives anything in your case, so somehow something is behaving different. I am running out of ideas. Would it be possible for you to do a similar experiment with a second serial port? That way we might learn if data actually makes it to the serial output when sending or if data is received on the serial input but not forwarded to the USB bus. I have a real RS232 port on a desktop (back at home now), so I guess I could connect from the netbook USB - ark3116 - RS232 desktop. I will have to see what cables I have, but I think I have a very old RS232 breakout box somewhere, so I can probably fix something up. I suppose I could use picoterm or similar to view the incoming data on the desktop: it is a while since I looked at those programs. I could also use a multimeter or whatever to see how those four wires on the garmin are connected to the 9-pin RS232 plug in case that throws any light on handshaking, if any. I might need a bit of hand holding since my serial knowledge is now rather rusty. It may take a day or two to find time to try all of this. I could also perhaps put an oscilloscope onto the RS232 breakout box to see what at least a couple of the signals are doing, but I will need to clear some bench space which is in very short supply! I guess that might also throw some light on what happens when connected to the garmin. That said, trying to follow serial signals on a 'scope isn't always straight forward: now if I had a logic analyser available, it might be much easier :-) If I do go to the 'scope, I guess a comparison between the old working kernel talking to the garmin and the latest problem version might help. But I suspect triggering properly might make that pretty difficult. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110928194809.GA4926@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
I have just done another test. This because that garmin odd connector often fails to make proper contact. So in this case I first verified that I could use gpsbabel successfully with the old kernel, so confirming a proper connection. Then I just used $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 Here are the extracts from /var/log/debug: -- Sep 21 19:27:23 elf kernel: [ 105.693623] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 21 19:27:23 elf kernel: [ 105.693635] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 21 19:27:23 elf kernel: [ 105.701012] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 21 19:27:23 elf kernel: [ 105.701035] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 21 19:27:28 elf kernel: [ 109.878778] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_read_int_callback - urb shutting down with status: -2 I haven't checked carefully, but I think no change? So I think that is all I can get from the debug log. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110921184556.GA2449@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Tue, Sep 20, 2011 at 09:38:04PM +0200, Bart Hartgers wrote: Hope something here gives a clue... Alas, no. As far as I can tell, the hardware is correctly setup to do 9600N8 without rtscts handshaking. Nothing in the log about a failing transmit, so it seems that gpsbabel's command goes out to the device, but somehow nothing is received in response. I am now worrying that the garmin connector was not making proper contact. I will try and test again tomorrow, first on the old kernel so that I am sure there is a good connection, and then try again on 3.0.nnn. But I suspect that it was making contact: I tried to check carefully, although that is not always reliable. I'll try to see if my 3116 still works with a 3.0 kernel, hopefully tomorrow. Maybe that brings us further. Thanks again, ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110920195937.GA2896@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux - Sep 18 08:55:59 elf kernel: [ 308.938724] usbcore: registered new interface driver usbserial Sep 18 08:55:59 elf kernel: [ 308.938785] USB Serial support registered for generic Sep 18 08:55:59 elf kernel: [ 308.938860] usbcore: registered new interface driver usbserial_generic Sep 18 08:55:59 elf kernel: [ 308.938868] usbserial: USB Serial Driver core Sep 18 08:55:59 elf kernel: [ 308.942683] USB Serial support registered for ark3116 Sep 18 08:55:59 elf kernel: [ 308.942758] usbcore: registered new interface driver ark3116 Sep 18 08:55:59 elf kernel: [ 308.942767] ark3116:v0.6:USB ARK3116 serial/IrDA driver Sep 18 08:56:05 elf kernel: [ 314.953411] usbcore: deregistering interface driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.953540] USB Serial deregistering driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.967004] USB Serial support registered for ark3116 Sep 18 08:56:05 elf kernel: [ 314.967178] usbcore: registered new interface driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.967195] ark3116:v0.6:USB ARK3116 serial/IrDA driver -- The above messages just from loading the module: the ark3116 was not plugged in. On plugging it: --- Sep 18 08:56:47 elf kernel: [ 357.080183] usb 2-1: new full speed USB device number 2 using uhci_hcd Sep 18 08:56:47 elf kernel: [ 357.240209] usb 2-1: New USB device found, idVendor=6547, idProduct=0232 Sep 18 08:56:47 elf kernel: [ 357.240229] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Sep 18 08:56:47 elf kernel: [ 357.240243] usb 2-1: Product: USB-UART Controller Sep 18 08:56:47 elf kernel: [ 357.240254] usb 2-1: Manufacturer: ArkMicroChips Sep 18 08:56:47 elf kernel: [ 357.242579] ark3116 2-1:1.0: ark3116 converter detected Sep 18 08:56:47 elf mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control -- As far as I can see that is just the same as when debug is not set. Or did I get the parameter wrong? I can't see any acknowledgement that debug is set. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110918081028.GA2619@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/18 ael law_ence@ntlworld.com: On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control Strange. The rmmod and modprobe shoudl set the debug flag, so I would expect some debug messages around the 'software flow control' stuff. Did you check the output of 'dmesg'? (The prefixes suggest these are coming through syslogd.) Perhaps the debug messages end up in a different log or something? By the way, the 'software flow control' warnings are relatively harmless. They appear when software flow control is asked for, because that cannot be done reliably without somekind of support in the hardware. But at 9600 baud that should not be a factor. Groeten, Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAK7h4yeq-84M2ZF0msuj79Z=VaG25rjDWzwtEq5031Lntyj5=q...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sun, Sep 18, 2011 at 01:55:50PM +0200, Bart Hartgers wrote: 2011/9/18 ael law_ence@ntlworld.com: On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control Strange. The rmmod and modprobe shoudl set the debug flag, so I would expect some debug messages around the 'software flow control' stuff. Did you check the output of 'dmesg'? (The prefixes suggest these are coming through syslogd.) Perhaps the debug messages end up in a different log or something? Ooops. I think you are right. I didn't check dmesg directly believing that it all appeared in /var/log/messages. But now I see /var/log/debug.. Sep 18 08:56:47 elf kernel: [ 357.542178] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 18 08:56:47 elf kernel: [ 357.542195] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:56:47 elf kernel: [ 357.550315] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 57600 Sep 18 08:56:47 elf kernel: [ 357.550339] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:52 Sep 18 08:56:47 elf kernel: [ 357.557438] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 0 Sep 18 08:56:47 elf kernel: [ 357.557460] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:56:47 elf kernel: [ 357.667612] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 57600 Sep 18 08:56:47 elf kernel: [ 357.667636] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:52 Sep 18 08:57:00 elf kernel: [ 370.008846] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_read_int_callback - urb shutting down with status: -2 Sep 18 08:57:00 elf kernel: [ 370.009808] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 18 08:57:00 elf kernel: [ 370.009872] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:57:00 elf kernel: [ 370.022971] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 115200 Sep 18 08:57:00 elf kernel: [ 370.022994] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:26 Sep 18 08:57:06 elf kernel: [ 376.007693] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_read_int_callback - urb shutting down with status: -2 Sep 18 08:57:21 elf kernel: [
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/13 ael law_ence@ntlworld.com: On Tue, Sep 13, 2011 at 08:56:54PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. truncated the termios data. Could you please rerun the strace with the '-v' option? Ok. Attached. Hi ael, As far as I can tell from the logs, gpsbabel does not enable handshaking. Unfortunately I do not another idea of what might be the problem. Another thing to try would be to load the ark3116 module with the debug=1 flag. Maybe something will appear in the kernel log/dmesg that gives a clue to what is going on. I'll see if I can find my ark3116 and hook it up with a null modem to try to reproduce the problem myself. But it will take a while before I can spend some time on that. Groeten, Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cak7h4yc3rcmp4r-6dzmpecbmpk9pgojcbejdijc2ad6pztk...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: 2011/9/13 ael law_ence@ntlworld.com: On Tue, Sep 13, 2011 at 08:56:54PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. truncated the termios data. Could you please rerun the strace with the '-v' option? Ok. Attached. Hi ael, As far as I can tell from the logs, gpsbabel does not enable handshaking. Unfortunately I do not another idea of what might be the problem. Another thing to try would be to load the ark3116 module with the debug=1 flag. Maybe something will appear in the kernel log/dmesg that gives a clue to what is going on. I'll see if I can find my ark3116 and hook it up with a null modem to try to reproduce the problem myself. But it will take a while before I can spend some time on that. I would try that now but it is a bit late and I am too tired to get the gps unit out and connect it tonight. But note that the dmesgs appear when the module is loaded before gpsbabel is run. I thought that I looked at the modinfo for ark3116 for a debug parameter: I must have missed it. But what I can do now is connect the ark3116 without the gps unit attached. Without debug, I see: Sep 16 20:20:29 elf kernel: [ 886.628117] USB Serial support registered for ark3116 Sep 16 20:20:29 elf kernel: [ 886.628230] ark3116 2-1:1.0: ark3116 converter detected Sep 16 20:20:29 elf kernel: [ 886.639145] usb 2-1: ark3116 using RS232 mode Sep 16 20:20:29 elf kernel: [ 886.639675] usb 2-1: ark3116 converter now attached to ttyUSB2 Sep 16 20:20:29 elf kernel: [ 886.639801] usbcore: registered new interface driver ark3116 Sep 16 20:20:29 elf kernel: [ 886.639818] ark3116:v0.6:USB ARK3116 serial/IrDA driver Sep 16 20:20:29 elf kernel: [ 886.721160] usb 2-1: ark3116: don't know how to do software flow control Sep 16 20:20:29 elf kernel: [ 886.734143] usb 2-1: ark3116: don't know how to do software flow control Sep 16 20:20:29 elf kernel: [ 886.742143] usb 2-1: ark3116: don't know how to do software flow control Sep 16 20:20:29 elf kernel: [ 886.850147] usb 2-1: ark3116: don't know how to do software flow control So that is nothing to do with the gps or gpsbabel. # rmmod ark3116; modprobe ark3116 debug=1 Now the tail of /var/log/messages has:- -- Sep 16 20:22:41 elf kernel: [ 1018.338935] usbcore: deregistering interface driver ark3116 Sep 16 20:22:41 elf kernel: [ 1018.339340] ark3116 ttyUSB2: ark3116 converter now disconnected from ttyUSB2 Sep 16 20:22:41 elf kernel: [ 1018.339442] ark3116 2-1:1.0: device disconnected Sep 16 20:22:41 elf kernel: [ 1018.339542] USB Serial deregistering driver ark3116 Sep 16 20:22:41 elf kernel: [ 1018.361551] USB Serial support registered for ark3116 Sep 16 20:22:41 elf kernel: [ 1018.362726] ark3116 2-1:1.0: ark3116 converter detected Sep 16 20:22:41 elf kernel: [ 1018.373754] usb 2-1: ark3116 using RS232 mode Sep 16 20:22:41 elf kernel: [ 1018.374179] usb 2-1: ark3116 converter now attached to ttyUSB2 Sep 16 20:22:41 elf kernel: [ 1018.374250] usbcore: registered new interface driver ark3116 Sep 16 20:22:41 elf kernel: [ 1018.374259] ark3116:v0.6:USB ARK3116 serial/IrDA driver -- So the don't know how to do messages have gone. Maybe I need to do a hot replug with debug on, or maybe the debug switch has changed a race or some such. I just unplugged and replugged (I assume ark3116 stayed loaded with debug=1 set) and just got: -- Sep 16 20:29:38 elf kernel: [ 1435.592212] usb 2-1: USB disconnect, device number 2 Sep 16 20:29:38 elf kernel: [ 1435.592788] ark3116 ttyUSB2: ark3116 converter now disconnected from ttyUSB2 Sep 16 20:29:38 elf kernel: [ 1435.592888] ark3116 2-1:1.0: device disconnected Sep 16 20:29:44 elf kernel: [ 1441.260149] usb 2-1: new full speed USB device number 3 using uhci_hcd Sep 16 20:29:44 elf kernel: [ 1441.420141] usb 2-1: New USB device found, idVendor=6547, idProduct=0232 Sep 16 20:29:44 elf kernel: [ 1441.420163] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Sep 16 20:29:44 elf kernel: [ 1441.420177] usb 2-1: Product: USB-UART Controller Sep 16 20:29:44 elf kernel: [ 1441.420188] usb 2-1: Manufacturer: ArkMicroChips Sep 16 20:29:44 elf kernel: [ 1441.422581] ark3116 2-1:1.0: ark3116 converter detected Sep 16 20:29:44 elf mtp-probe: checking bus 2, device 3: /sys/devices/pci:00/:00:1d.0/usb2/2-1 Sep 16 20:29:44 elf kernel: [ 1441.437135] usb 2-1: ark3116 using RS232 mode Sep 16 20:29:44 elf kernel: [ 1441.437541] usb 2-1: ark3116 converter now attached to ttyUSB2 Sep 16 20:29:44 elf mtp-probe: bus: 2, device: 3 was not an MTP device
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Tue, Sep 13, 2011 at 08:56:54PM +0200, Bart Hartgers wrote:
[Previous messages are logged at http://bugs.debian.org/640391.
Thanks for the strace. It seems that gpsbabel is treating the device
as a tty and not just a plain file. My main suspect is still a problem
with the cts/rts handshaking. Unfortunately, I cannot tell what
exactly gpsbabel does to the handshake signals because strace
truncated the termios data. Could you please rerun the strace with the
'-v' option?
Ok. Attached.
One proviso. The peculiar garmin serial connector on this gps unit
sometimes doesn't make good contact. I am pretty sure that it was ok
for this run, but it is just possible that the connector was playing
up. (Known problem on this model, I fear.)
ael
fstat64(3, {st_dev=makedev(0, 3), st_ino=4026532018, st_mode=S_IFREG|0444,
st_nlink=1, st_uid=0, st_gid=0, st_blksize=1024, st_blocks=0, st_size=0,
st_atime=2011/09/13-21:29:17, st_mtime=2011/09/13-21:29:17,
st_ctime=2011/09/13-21:29:17}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb778c000
read(3, MemTotal:1540708 kB\nMemF..., 1024) = 1024
close(3)= 0
munmap(0xb778c000, 4096)= 0
open(/dev/ttyUSB0, O_RDWR)= 3
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x500, c_oflags=0x5,
c_cflags=0xcbd, c_lflags=0x8a3b, c_line=0,
c_cc=\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00})
= 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x500, c_oflags=0x5,
c_cflags=0xcbd, c_lflags=0x8a3b, c_line=0,
c_cc=\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00})
= 0
ioctl(3, SNDCTL_TMR_CONTINUE or TCSETSF, {c_iflags=0, c_oflags=0,
c_cflags=0xcbd, c_lflags=0, c_line=0, c_cc[VMIN]=1, c_cc[VTIME]=0,
c_cc=\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00})
= 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0, c_oflags=0,
c_cflags=0xcbd, c_lflags=0, c_line=0, c_cc[VMIN]=1, c_cc[VTIME]=0,
c_cc=\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00})
= 0
ioctl(3, TCFLSH, 0x2) = 0
write(3, \20\376\0, 3)= 3
write(3, , 0) = 0
write(3, \2\20\3, 3) = 3
time(NULL) = 1315945757
time(NULL) = 1315945757
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/11 ael law_ence@ntlworld.com:
On Thu, Sep 08, 2011 at 06:33:29PM +0200, Bart Hartgers wrote:
Op 8 sep. 2011 16:56 schreef Ben Hutchings b...@decadent.org.uk het
volgende:
[Previous messages are logged at http://bugs.debian.org/640391.
tl,dr: gpsbabel times-out when trying to read through ark3116.]
2.6.32-5 (working)
and
2.6.34-1 (failing).
Bart, what can ael do to help debug this? I suppose an strace log of
gpsbabel under Linux 3.0 would be helpful?
Hi Ben, ael,
I am reading this on my phone and will not be able to look into this
properly (ie access a computer) before next week.
In the mean time: strace logs would be very useful. And maybe the problen
has to do with the new driver doing real handshaking while the old one
effectively ignored hs signals iirc.
strace log attached. I didn't set any special switches, but I think it
captures the necessary. I did think of truncating the very long tail
of timeouts (the file is 291K long), but decided I had better let it
stand.
Hi ael,
Thanks for the strace. It seems that gpsbabel is treating the device
as a tty and not just a plain file. My main suspect is still a problem
with the cts/rts handshaking. Unfortunately, I cannot tell what
exactly gpsbabel does to the handshake signals because strace
truncated the termios data. Could you please rerun the strace with the
'-v' option?
You do not have to send the full log, just this part (lines 69-74)
open(/dev/ttyUSB0, O_RDWR)= 3
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B9600 opost isig icanon echo ...}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B9600 opost isig icanon echo ...}) = 0
ioctl(3, SNDCTL_TMR_CONTINUE or TCSETSF, {B9600 -opost -isig -icanon
-echo ...}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B9600 -opost -isig -icanon
-echo ...}) = 0
ioctl(3, TCFLSH, 0x2) = 0
Also the output of 'stty -a /dev/ttyUSB0' might give a clue.
Thanks.
Groeten,
Bart
--
Bart Hartgers - New e-mail: bart.hartg...@gmail.com
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cak7h4ydzkdnoufyknfbbamvbd7bvfapaq_y0tcdplhkjth2...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
Also the output of 'stty -a /dev/ttyUSB0' might give a clue. $ stty -a /dev/ttyUSB2 speed 9600 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = undef; eol2 = undef; swtch = undef; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110913204443.GB3051@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Thu, Sep 08, 2011 at 06:33:29PM +0200, Bart Hartgers wrote: Hi Ben, ael, I am reading this on my phone and will not be able to look into this properly (ie access a computer) before next week. In the mean time: strace logs would be very useful. And maybe the problen has to do with the new driver doing real handshaking while the old one effectively ignored hs signals iirc. That sounds very likely from what I can see. I don't think that gpsbabel is doing anything beyond opening the file trying to read it. /dev/ttyUSB* is just treated as any other file, I suspect. In passing, the serial port on the garmin satnav has a 4 wire connection. So any hardwired handshaking must be minimal. The garmin cable just takes those to the usual 9-pin RS232 serial plug - to which the USB converter connects. I might try statserial and strace that as well if I have time. Actually I seem to remember that statserial would only read serial files, and could not connect to /dev/ttyUSB*, so that probably won't work. As earlier in the report, I am away from home, using a small netbook with limited connectivity, so compiling and testing with a stock kernal isn't very practical for the moment. Thanks for all the help so far to both of you, ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110909083306.GA3336@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Tue, Sep 06, 2011 at 04:16:11AM +0100, Ben Hutchings wrote: Regression in the ark3116 (perhaps interaction with usbserial). available from http://snapshot.debian.org/package/linux-2.6/) to Probably the most useful one to test would be: http://snapshot.debian.org/package/linux-2.6/2.6.34-1~experimental.2/ I just checked in snapshot.debian.org/package/linux-2.6/ and I can't see any kernel to test between 2.6.32-5 (working) and 2.6.34-1 (failing). Is there any point in alerting upstream, presumably Bart Hartgers bart.hartgers+ark3...@gmail.com, to this bug report, or is he already aware? I doubt that it is a debian specific bug... ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110908130822.GA2820@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
[Previous messages are logged at http://bugs.debian.org/640391. tl,dr: gpsbabel times-out when trying to read through ark3116.] On Thu, 2011-09-08 at 14:08 +0100, ael wrote: On Tue, Sep 06, 2011 at 04:16:11AM +0100, Ben Hutchings wrote: Regression in the ark3116 (perhaps interaction with usbserial). available from http://snapshot.debian.org/package/linux-2.6/) to Probably the most useful one to test would be: http://snapshot.debian.org/package/linux-2.6/2.6.34-1~experimental.2/ I just checked in snapshot.debian.org/package/linux-2.6/ and I can't see any kernel to test between 2.6.32-5 (working) and 2.6.34-1 (failing). Is there any point in alerting upstream, presumably Bart Hartgers bart.hartgers+ark3...@gmail.com, to this bug report, or is he already aware? Right, the changes between 2.6.32 and 2.6.34 were mostly made by Bart. I asked you to test 2.6.34 in order to find out whether the regression was likely to be related to these or to later changes by other developers. I doubt that it is a debian specific bug... Indeed, probably not. Bart, what can ael do to help debug this? I suppose an strace log of gpsbabel under Linux 3.0 would be helpful? Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure. signature.asc Description: This is a digitally signed message part
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
Op 8 sep. 2011 16:56 schreef Ben Hutchings b...@decadent.org.uk het volgende: [Previous messages are logged at http://bugs.debian.org/640391. tl,dr: gpsbabel times-out when trying to read through ark3116.] On Thu, 2011-09-08 at 14:08 +0100, ael wrote: On Tue, Sep 06, 2011 at 04:16:11AM +0100, Ben Hutchings wrote: Regression in the ark3116 (perhaps interaction with usbserial). available from http://snapshot.debian.org/package/linux-2.6/) to Probably the most useful one to test would be: http://snapshot.debian.org/package/linux-2.6/2.6.34-1~experimental.2/ I just checked in snapshot.debian.org/package/linux-2.6/ and I can't see any kernel to test between 2.6.32-5 (working) and 2.6.34-1 (failing). Is there any point in alerting upstream, presumably Bart Hartgers bart.hartgers+ark3...@gmail.com, to this bug report, or is he already aware? Right, the changes between 2.6.32 and 2.6.34 were mostly made by Bart. I asked you to test 2.6.34 in order to find out whether the regression was likely to be related to these or to later changes by other developers. I doubt that it is a debian specific bug... Indeed, probably not. Bart, what can ael do to help debug this? I suppose an strace log of gpsbabel under Linux 3.0 would be helpful? Hi Ben, ael, I am reading this on my phone and will not be able to look into this properly (ie access a computer) before next week. In the mean time: strace logs would be very useful. And maybe the problen has to do with the new driver doing real handshaking while the old one effectively ignored hs signals iirc. Groeten, Bart Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure.
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Tue, Sep 06, 2011 at 04:16:11AM +0100, Ben Hutchings wrote: On Mon, 2011-09-05 at 19:46 +0100, ael wrote: On Mon, Sep 05, 2011 at 12:11:26PM +0100, Ben Hutchings wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Regression in the ark3116 (perhaps interaction with usbserial). I can maybe try perhaps one more kernel with my current limited connectivity if it would help. But at least I can recover my gps data for now. Probably the most useful one to test would be: http://snapshot.debian.org/package/linux-2.6/2.6.34-1~experimental.2/ Just downloaded and tried linux-image-2.6.34-1-686_2.6.34-1~experimental.2_i386.deb # uname -a Linux elf 2.6.34-1-686 #1 SMP Sun Jun 6 22:56:48 UTC 2010 i686 GNU/Linux It failed: $gpsbabel -t -i garmin -f /dev/ttyUSB0 -o gps -F 040911.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 In /var/log/messages: Sep 7 11:03:40 elf kernel: [ 120.632142] usb 2-1: new full speed USB device using uhci_hcd and address 2 Sep 7 11:03:41 elf mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 Sep 7 11:03:41 elf kernel: [ 120.792194] usb 2-1: New USB device found, idVendor=6547, idProduct=0232 Sep 7 11:03:41 elf kernel: [ 120.792212] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Sep 7 11:03:41 elf kernel: [ 120.792225] usb 2-1: Product: USB-UART Controller Sep 7 11:03:41 elf kernel: [ 120.792234] usb 2-1: Manufacturer: ArkMicroChips Sep 7 11:03:41 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 7 11:03:41 elf kernel: [ 120.992791] usbcore: registered new interface driver usbserial Sep 7 11:03:41 elf kernel: [ 120.992860] USB Serial support registered for generic Sep 7 11:03:41 elf kernel: [ 120.993565] usbcore: registered new interface driver usbserial_generic Sep 7 11:03:41 elf kernel: [ 120.993576] usbserial: USB Serial Driver core Sep 7 11:03:41 elf kernel: [ 120.999642] USB Serial support registered for ark3116 Sep 7 11:03:41 elf kernel: [ 120.999692] ark3116 2-1:1.0: ark3116 converter detected Sep 7 11:03:41 elf kernel: [ 121.010175] usb 2-1: ark3116 using RS232 mode Sep 7 11:03:41 elf kernel: [ 121.010658] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 7 11:03:41 elf kernel: [ 121.010900] usbcore: registered new interface driver ark3116 Sep 7 11:03:41 elf kernel: [ 121.010912] ark3116:v0.5:USB ARK3116 serial/IrDA driver Sep 7 11:03:41 elf kernel: [ 121.080195] usb 2-1: ark3116: don't know how to do software flow control Sep 7 11:03:41 elf kernel: [ 121.092180] usb 2-1: ark3116: don't know how to do software flow control Sep 7 11:03:41 elf kernel: [ 121.099170] usb 2-1: ark3116: don't know how to do software flow control Sep 7 11:03:41 elf kernel: [ 121.206183] usb 2-1: ark3116: don't know how to do software flow control = So just the same don't know how to do software flow control messages as in the most recent kernel. So I guess that helps nail the regression a bit more accurately. I can probably test another kernel in a day or two to help narrow the regression interval. Thanks again for all the help. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110907101402.GA2589@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sun, Sep 04, 2011 at 09:07:17PM +0100, Ben Hutchings wrote: On Sun, 2011-09-04 at 19:42 +0100, ael wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Regression in the ark3116 (perhaps interaction with usbserial). The hardware is a USB -serial port converter. It was last used on this machine running debian testing in December 2011. It ran successfully with the debian kernel at that time. Please can you test with an older kernel package (they are still available from http://snapshot.debian.org/package/linux-2.6/) to verify that this is definitely a difference between kernel versions. I was going to try that but I am away from home with limited connectivity. Just hope that I don't hit dependency hell... Any easy way to discover which binary was current back in December? The lack of a release date in debs I find awkward. Now the application reports: [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB2 (It is attempting to establish a connection to a garmin gps unit with serial interface.) [...] What is this application? gpsbabel. I use it all the time, but usually on desktops with real RS232 ports. I only need this USB -- RS232 converter when away from home which is why I have only just discovered the problem. -- Package: gpsbabel Status: install ok installed Priority: optional Section: utils Installed-Size: 1304 Maintainer: Bernd Zeimetz b...@debian.org Architecture: i386 Version: 1.4.2-3 --- Thanks for the quick response. I haven't yet looked on KML for anything relevant. I don't fancy compiling a stock kernel on this atom netbook.. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110905091545.GB3214@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sun, Sep 04, 2011 at 09:07:17PM +0100, Ben Hutchings wrote: On Sun, 2011-09-04 at 19:42 +0100, ael wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Regression in the ark3116 (perhaps interaction with usbserial). The hardware is a USB -serial port converter. It was last used on this machine running debian testing in December 2011. It ran successfully with the debian kernel at that time. Please can you test with an older kernel package (they are still available from http://snapshot.debian.org/package/linux-2.6/) to verify that this is definitely a difference between kernel versions. I have just downloaded and attempted to install linux-image-2.6.26-2-686_2.6.26-26lenny1_i386.deb I selected that on the basis of the timestamp in the snapshot pool. As anticipated, dependency hell started: dpkg -i linux-image-2.6.26-2-686_2.6.26-26lenny1_i386.deb Selecting previously deselected package linux-image-2.6.26-2-686. (Reading database ... 181698 files and directories currently installed.) Unpacking linux-image-2.6.26-2-686 (from linux-image-2.6.26-2-686_2.6.26-26lenny1_i386.deb) ... Could not find mkinitramfs-kpkg mkinitrd.yaird. at /var/lib/dpkg/tmp.ci/preinst line 234, STDIN line 9. Done. Setting up linux-image-2.6.26-2-686 (2.6.26-26lenny1) ... Running depmod. Failed to find suitable ramdisk generation tool for kernel version 2.6.26-2-686 on running kernel 3.0.0-1-686-pae in mkinitramfs-kpkg mkinitrd.yaird dpkg: error processing linux-image-2.6.26-2-686 (--install): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-image-2.6.26-2-686 I guess that I could use some of the -force switches, and I should be able to get grub2 to load the kernel, but I am not sure about the rest without of lot of time and effort. Any suggestions for a better way, or a better kernal test? I am not sure that a sort of manual git-bisect on the debian kernels is feasible given my limited time and bandwidth away from home. ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110905093537.GC3214@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Mon, 2011-09-05 at 10:15 +0100, ael wrote:
On Sun, Sep 04, 2011 at 09:07:17PM +0100, Ben Hutchings wrote:
On Sun, 2011-09-04 at 19:42 +0100, ael wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
The hardware is a USB -serial port converter.
It was last used on this machine running debian testing in December
2011. It ran successfully with the debian kernel at that time.
Please can you test with an older kernel package (they are still
available from http://snapshot.debian.org/package/linux-2.6/) to
verify that this is definitely a difference between kernel versions.
I was going to try that but I am away from home with limited
connectivity. Just hope that I don't hit dependency hell...
Any easy way to discover which binary was current back in December?
The lack of a release date in debs I find awkward.
[...]
In December, testing/unstable saw versions 2.6.32-{28,29,30} and
experimental saw 2.6.36-1~experimental.1 followed by various 2.6.37
release candidates. Maybe you should just test the current version from
squeeze.
Ben.
signature.asc
Description: This is a digitally signed message part
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Mon, Sep 05, 2011 at 12:11:26PM +0100, Ben Hutchings wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
Please can you test with an older kernel package (they are still
available from http://snapshot.debian.org/package/linux-2.6/) to
verify that this is definitely a difference between kernel versions.
In December, testing/unstable saw versions 2.6.32-{28,29,30} and
experimental saw 2.6.36-1~experimental.1 followed by various 2.6.37
release candidates. Maybe you should just test the current version from
squeeze.
Just installed 2.6.32-5-686 from squeeze:
linux-image-2.6.32-5-686_2.6.32-35_i386.deb
$ gpsbabel -t -i garmin -f /dev/ttyUSB2 -o gpx -F 040911.gpx
worked ok.
So the regression is quite recent. I can maybe try perhaps one more
kernel with my current limited connectivity if it would help.
But at least I can recover my gps data for now.
ael
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110905184659.GA3500@elf.conquest
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Mon, 2011-09-05 at 19:46 +0100, ael wrote:
On Mon, Sep 05, 2011 at 12:11:26PM +0100, Ben Hutchings wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: upstream
Regression in the ark3116 (perhaps interaction with usbserial).
Please can you test with an older kernel package (they are still
available from http://snapshot.debian.org/package/linux-2.6/) to
verify that this is definitely a difference between kernel versions.
In December, testing/unstable saw versions 2.6.32-{28,29,30} and
experimental saw 2.6.36-1~experimental.1 followed by various 2.6.37
release candidates. Maybe you should just test the current version from
squeeze.
Just installed 2.6.32-5-686 from squeeze:
linux-image-2.6.32-5-686_2.6.32-35_i386.deb
$ gpsbabel -t -i garmin -f /dev/ttyUSB2 -o gpx -F 040911.gpx
worked ok.
So the regression is quite recent.
Not so recent - 2.6.32 was released 21 months ago now.
I can maybe try perhaps one more
kernel with my current limited connectivity if it would help.
But at least I can recover my gps data for now.
Probably the most useful one to test would be:
http://snapshot.debian.org/package/linux-2.6/2.6.34-1~experimental.2/
Ben.
signature.asc
Description: This is a digitally signed message part
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Regression in the ark3116 (perhaps interaction with usbserial). The hardware is a USB -serial port converter. It was last used on this machine running debian testing in December 2011. It ran successfully with the debian kernel at that time. Now the application reports: [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB2 (It is attempting to establish a connection to a garmin gps unit with serial interface.) = /var/log/messages includes: Sep 4 19:04:19 elf kernel: [ 3502.996139] usb 2-1: new full speed USB device nu mber 3 using uhci_hcd Sep 4 19:04:19 elf kernel: [ 3503.156165] usb 2-1: New USB device found, idVend or=6547, idProduct=0232 Sep 4 19:04:19d elf kernel: [ 3503.156188] usb 2-1: New USB device strings: Mfr= 1, Product=3, SerialNumber=0 Sep 4 19:04:19 elf kernel: [ 3503.156202] usb 2-1: Product: USB-UART Controller Sep 4 19:04:19 elf kernel: [ 3503.156213] usb 2-1: Manufacturer: ArkMicroChips Sep 4 19:04:19 elf kernel: [ 3503.158626] ark3116 2-1:1.0: ark3116 converter de tected Sep 4 19:04:19 elf mtp-probe: checking bus 2, device 3: /sys/devices/pci:0 0/:00:1d.0/usb2/2-1 Sep 4 19:04:19 elf kernel: [ 3503.173159] usb 2-1: ark3116 using RS232 mode Sep 4 19:04:19 elf kernel: [ 3503.173696] usb 2-1: ark3116 converter now attach ed to ttyUSB2 Sep 4 19:04:19 elf mtp-probe: bus: 2, device: 3 was not an MTP device Sep 4 19:04:35 elf kernel: [ 3519.616743] usb 2-1: ark3116: don't know how to d o software flow control Sep 4 19:05:00 elf kernel: [ 3544.195822] usb 2-1: ark3116: don't know how to d o software flow control Sep 4 19:05:25 elf kernel: [ 3569.458610] usb 2-1: ark3116: don't know how to d o software flow control Sep 4 19:06:23 elf kernel: [ 3627.785287] usb 2-1: ark3116: don't know how to d o software flow control Sep 4 19:07:32 elf kernel: [ 3696.180832] usb 2-1: ark3116: don't know how to d o software flow control === Googling reveals many similar reports, but those all seem to be old, dating from before the time when it worked in Debian. Sorry for the lack of further detail, but it certainly looks like a regression... I am sending this report using a USB dongle attached to ports /dev/ttyUSB0 /dev/ttyUSB1 -- so those entries in the logs can be ignored. Removing the dongle does not resolve the problem, which is not surprising given the error message. -- Package-specific info: ** Version: Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-686-pae root=UUID=b0e0725b-0ebb-4a27-964d-75eb6e73e069 ro elevator=noop enable_mtrr_cleanup ** Not tainted ** Kernel log: [ 230.558740] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0 [ 230.558794] option 1-2:1.1: GSM modem (1-port) converter detected [ 230.559052] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1 [ 230.559167] usbcore: registered new interface driver option [ 230.559175] option: v0.7.2:USB Driver for GSM modems [ 231.279679] scsi 5:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 231.285588] scsi 5:0:0:0: Attached scsi generic sg1 type 5 [ 231.293062] scsi 6:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2 [ 231.302950] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 231.311795] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 231.334562] sr0: scsi-1 drive [ 231.334575] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 231.335009] sr 5:0:0:0: Attached scsi CD-ROM sr0 [ 275.627233] ip_tables: (C) 2000-2006 Netfilter Core Team [ 276.489237] Netfilter messages via NETLINK v0.30. [ 276.512980] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 276.715507] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 276.717318] NF_TPROXY: Transparent proxy support initialized, version 4.1.0 [ 276.717330] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd. [ 276.765464] ctnetlink v0.93: registering with nfnetlink. [ 276.928900] ip_set: protocol 6 [ 276.951233] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully [ 277.633633] xt_time: kernel timezone is - [ 278.325279] u32 classifier [ 278.325290] Performance counters on [ 278.325295] input device check on [ 278.325300] Actions configured [ 278.714795] PPP generic driver version 2.4.2 [ 3085.372149] usb 2-1: new full speed USB device number 2 using uhci_hcd [ 3085.532173] usb 2-1: New USB device found, idVendor=6547, idProduct=0232 [ 3085.532194] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 3085.532209] usb 2-1: Product: USB-UART Controller [ 3085.532219] usb 2-1:
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sun, 2011-09-04 at 19:42 +0100, ael wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Regression in the ark3116 (perhaps interaction with usbserial). The hardware is a USB -serial port converter. It was last used on this machine running debian testing in December 2011. It ran successfully with the debian kernel at that time. Please can you test with an older kernel package (they are still available from http://snapshot.debian.org/package/linux-2.6/) to verify that this is definitely a difference between kernel versions. Now the application reports: [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB2 (It is attempting to establish a connection to a garmin gps unit with serial interface.) [...] What is this application? Ben. signature.asc Description: This is a digitally signed message part
