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/pci0000:0
0/0000: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) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011
** 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-ROM HUAWEI 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 -0000
[ 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: Manufacturer: ArkMicroChips
[ 3085.761442] USB Serial support registered for ark3116
[ 3085.761565] ark3116 2-1:1.0: ark3116 converter detected
[ 3085.772154] usb 2-1: ark3116 using RS232 mode
[ 3085.772694] usb 2-1: ark3116 converter now attached to ttyUSB2
[ 3085.772820] usbcore: registered new interface driver ark3116
[ 3085.772838] ark3116:v0.6:USB ARK3116 serial/IrDA driver
[ 3085.856174] usb 2-1: ark3116: don't know how to do software flow control
[ 3085.868157] usb 2-1: ark3116: don't know how to do software flow control
[ 3085.876178] usb 2-1: ark3116: don't know how to do software flow control
[ 3085.983154] usb 2-1: ark3116: don't know how to do software flow control
[ 3098.015889] usb 2-1: ark3116: don't know how to do software flow control
[ 3374.873739] usb 2-1: ark3116: don't know how to do software flow control
[ 3392.458526] usb 2-1: ark3116: don't know how to do software flow control
[ 3420.733926] usb 2-1: ark3116: don't know how to do software flow control
[ 3455.386078] usb 2-1: ark3116: don't know how to do software flow control
[ 3472.273444] usb 2-1: ark3116: don't know how to do software flow control
[ 3488.239740] usb 2-1: ark3116: don't know how to do software flow control
[ 3497.464187] usb 2-1: USB disconnect, device number 2
[ 3497.464780] ark3116 ttyUSB2: ark3116 converter now disconnected from ttyUSB2
[ 3497.464885] ark3116 2-1:1.0: device disconnected
[ 3502.996139] usb 2-1: new full speed USB device number 3 using uhci_hcd
[ 3503.156165] usb 2-1: New USB device found, idVendor=6547, idProduct=0232
[ 3503.156188] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 3503.156202] usb 2-1: Product: USB-UART Controller
[ 3503.156213] usb 2-1: Manufacturer: ArkMicroChips
[ 3503.158626] ark3116 2-1:1.0: ark3116 converter detected
[ 3503.173159] usb 2-1: ark3116 using RS232 mode
[ 3503.173696] usb 2-1: ark3116 converter now attached to ttyUSB2
[ 3519.616743] usb 2-1: ark3116: don't know how to do software flow control
[ 3544.195822] usb 2-1: ark3116: don't know how to do software flow control
[ 3569.458610] usb 2-1: ark3116: don't know how to do software flow control
[ 3627.785287] usb 2-1: ark3116: don't know how to do software flow control
[ 3696.180832] usb 2-1: ark3116: don't know how to do software flow control
[ 4005.281955] usb 1-2: USB disconnect, device number 4
[ 4005.282299] option: option_instat_callback: error -108
[ 4005.282656] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 4005.282781] option 1-2:1.0: device disconnected
[ 4005.283470] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 4005.283591] option 1-2:1.1: device disconnected
[ 4015.071537] usb 2-1: ark3116: don't know how to do software flow control
[ 4023.202284] usb 2-1: ark3116: don't know how to do software flow control
[ 4089.772724] usb 2-1: ark3116: don't know how to do software flow control
[ 4267.236193] usb 1-2: new high speed USB device number 7 using ehci_hcd
[ 4267.382567] usb 1-2: New USB device found, idVendor=12d1, idProduct=1003
[ 4267.382590] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 4267.382604] usb 1-2: Product: HUAWEI Mobile
[ 4267.382614] usb 1-2: Manufacturer: HUAWEI Technology
[ 4267.389595] scsi7 : usb-storage 1-2:1.0
[ 4267.391103] usb 1-2: USB disconnect, device number 7
[ 4273.132167] usb 1-2: new high speed USB device number 8 using ehci_hcd
[ 4273.278260] usb 1-2: New USB device found, idVendor=12d1, idProduct=1003
[ 4273.278288] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 4273.278308] usb 1-2: Product: HUAWEI Mobile
[ 4273.278323] usb 1-2: Manufacturer: HUAWEI Technology
[ 4273.283147] option 1-2:1.0: GSM modem (1-port) converter detected
[ 4273.283860] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 4273.285406] option 1-2:1.1: GSM modem (1-port) converter detected
[ 4273.285740] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 4273.288387] scsi10 : usb-storage 1-2:1.2
[ 4273.291025] scsi11 : usb-storage 1-2:1.3
[ 4274.292524] scsi 11:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2
[ 4274.295974] sd 11:0:0:0: Attached scsi generic sg1 type 0
[ 4274.297371] scsi 10:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 4274.304555] sd 11:0:0:0: [sdb] Attached SCSI removable disk
[ 4274.314362] sr0: scsi-1 drive
[ 4274.314803] sr 10:0:0:0: Attached scsi CD-ROM sr0
[ 4274.315105] sr 10:0:0:0: Attached scsi generic sg2 type 5
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:d101 Suyin Corp. Acer CrystalEye Webcam
Bus 001 Device 008: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem
Bus 002 Device 003: ID 6547:0232 Arkmicro Technologies Inc. ARK3116 Serial
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.0.0-1-686-pae depends on:
ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy
ii initramfs-tools [linux-initra 0.99 tools for generating an initramfs
ii linux-base 3.3 Linux image base package
ii module-init-tools 3.16-1 tools for managing Linux kernel mo
Versions of packages linux-image-3.0.0-1-686-pae recommends:
ii firmware-linux-free 3 Binary firmware for various driver
ii libc6-i686 2.13-16 Embedded GNU C Library: Shared lib
Versions of packages linux-image-3.0.0-1-686-pae suggests:
ii grub-pc 1.99-11 GRand Unified Bootloader, version
pn linux-doc-3.0.0 <none> (no description available)
Versions of packages linux-image-3.0.0-1-686-pae is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.33 Binary firmware for various driver
ii firmware-linux-nonfree 0.33 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110904184215.4187.42390.reportbug@elf.conquest"> http://lists.debian.org/20110904184215.4187.42390.reportbug@elf.conquest
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.)
[...]
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 <bzed@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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110905091545.GB3214@elf.conquest">http://lists.debian.org/20110905091545.GB3214@elf.conquest
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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110905093537.GC3214@elf.conquest">http://lists.debian.org/20110905093537.GC3214@elf.conquest
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.
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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110905184659.GA3500@elf.conquest">http://lists.debian.org/20110905184659.GA3500@elf.conquest
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/
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/pci0000:00/0000: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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110907101402.GA2589@elf.conquest">http://lists.debian.org/20110907101402.GA2589@elf.conquest
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+ark3116@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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110908130822.GA2820@elf.conquest">http://lists.debian.org/20110908130822.GA2820@elf.conquest
[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+ark3116@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.