Bug#495718: marked as done (linux-image-2.6.26-1-686: ark3116 module doesn't work anymore)
Your message dated Tue, 02 Mar 2010 12:39:41 +0100
with message-id <87bpf79cle.fsf@tac.ki.iif.hu>
and subject line Re: not kernel version dependent
has caused the Debian Bug report #495718,
regarding linux-image-2.6.26-1-686: ark3116 module doesn't work anymore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
495718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495718
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6.26-1-686: ark3116 module doesn't work anymore
- From: Ferenc Wágner <wferi@niif.hu>
- Date: Wed, 20 Aug 2008 00:31:51 +0200
- Message-id: <20080819223151.5661.95264.reportbug@szonett.ki.iif.hu>
Package: linux-image-2.6.26-1-686
Version: 2.6.26-2
Severity: normal
Hi,
I'm using a mostly stock Etch system with unstable kernels. Up to
2.6.25-2-686 everything was OK, but after installing
linux-image-2.6.26-1-686 my data cable can't contact my mobile phone
anymore. Under 2.6.25-2 loading the ark3116 module with debug enabled
then connecting the USB connector gives:
[ 64.691907] usbcore: registered new interface driver usbserial
[ 64.691929] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[ 64.691945] usbcore: registered new interface driver usbserial_generic
[ 64.691948] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[ 64.704888] drivers/usb/serial/usb-serial.c: USB Serial support registered for ark3116
[ 64.704916] usbcore: registered new interface driver ark3116
[ 81.649776] hub 4-0:1.0: unable to enumerate USB device on port 3
[ 81.889344] usb 2-1: new full speed USB device using uhci_hcd and address 2
[ 82.044950] usb 2-1: configuration #1 chosen from 1 choice
[ 82.049932] ark3116 2-1:1.0: ark3116 converter detected
[ 82.052493] drivers/usb/serial/ark3116.c: 003 > ok
[ 82.053131] drivers/usb/serial/ark3116.c: 004 > ok
[ 82.054135] drivers/usb/serial/ark3116.c: 005 > ok
[ 82.055142] drivers/usb/serial/ark3116.c: 006 > ok
[ 82.056137] drivers/usb/serial/ark3116.c: 007 < 1 bytes [0x00]
[ 82.057144] drivers/usb/serial/ark3116.c: 008 > ok
[ 82.058120] drivers/usb/serial/ark3116.c: 009 > ok
[ 82.059123] drivers/usb/serial/ark3116.c: 010 > ok
[ 82.060121] drivers/usb/serial/ark3116.c: 011 > ok
[ 82.061125] drivers/usb/serial/ark3116.c: 012 < 1 bytes [0x00]
[ 82.062125] drivers/usb/serial/ark3116.c: 013 > ok
[ 82.063127] drivers/usb/serial/ark3116.c: 014 < 1 bytes [0x00]
[ 82.064126] drivers/usb/serial/ark3116.c: 015 > ok
[ 82.065127] drivers/usb/serial/ark3116.c: 016 < 1 bytes [0x00]
[ 82.066125] drivers/usb/serial/ark3116.c: 017 > ok
[ 82.067125] drivers/usb/serial/ark3116.c: 018 < 1 bytes [0x01]
[ 82.068124] drivers/usb/serial/ark3116.c: 019 > ok
[ 82.069128] drivers/usb/serial/ark3116.c: 020 < 1 bytes [0x30]
[ 82.070128] drivers/usb/serial/ark3116.c: 147 > ok
[ 82.071127] drivers/usb/serial/ark3116.c: 148 > ok
[ 82.072127] drivers/usb/serial/ark3116.c: 149 > ok
[ 82.073127] drivers/usb/serial/ark3116.c: 150 > ok
[ 82.074126] drivers/usb/serial/ark3116.c: 151 < 1 bytes [0x03]
[ 82.075128] drivers/usb/serial/ark3116.c: 152 > ok
[ 82.076127] drivers/usb/serial/ark3116.c: 153 < 1 bytes [0x00]
[ 82.077127] drivers/usb/serial/ark3116.c: 154 > ok
[ 82.077243] usb 2-1: ark3116 converter now attached to ttyUSB0
[ 82.077409] usb 2-1: New USB device found, idVendor=6547, idProduct=0232
[ 82.077413] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 82.077417] usb 2-1: Product: USB-UART Controller
[ 82.077420] usb 2-1: Manufacturer: ArkMicroChips
While loading the module under 2.6.26-1 results in negative byte
counts (-71):
[ 1744.937716] usbserial: USB Serial support registered for ark3116
[ 1744.937751] ark3116 3-1:1.0: ark3116 converter detected
[ 1744.939141] drivers/usb/serial/ark3116.c: 003 > ok
[ 1744.940114] drivers/usb/serial/ark3116.c: 004 > ok
[ 1744.940947] drivers/usb/serial/ark3116.c: 005 > ok
[ 1744.941864] drivers/usb/serial/ark3116.c: 006 > ok
[ 1744.942783] drivers/usb/serial/ark3116.c: 007 < -71 bytes [0x5F]
[ 1744.944757] drivers/usb/serial/ark3116.c: 008 > ok
[ 1744.945113] drivers/usb/serial/ark3116.c: 009 > ok
[ 1744.946110] drivers/usb/serial/ark3116.c: 010 > ok
[ 1744.947111] drivers/usb/serial/ark3116.c: 011 > ok
[ 1744.948096] drivers/usb/serial/ark3116.c: 012 < -71 bytes [0x5F]
[ 1744.949006] drivers/usb/serial/ark3116.c: 013 > ok
[ 1744.949921] drivers/usb/serial/ark3116.c: 014 < -71 bytes [0x5F]
[ 1744.950833] drivers/usb/serial/ark3116.c: 015 > ok
[ 1744.951761] drivers/usb/serial/ark3116.c: 016 < -71 bytes [0x5F]
[ 1744.952674] drivers/usb/serial/ark3116.c: 017 > ok
[ 1744.953565] drivers/usb/serial/ark3116.c: 018 < -71 bytes [0x5F]
[ 1744.954475] drivers/usb/serial/ark3116.c: 019 > ok
[ 1744.955391] drivers/usb/serial/ark3116.c: 020 < -71 bytes [0x5F]
[ 1744.956303] drivers/usb/serial/ark3116.c: 147 > ok
[ 1744.957219] drivers/usb/serial/ark3116.c: 148 > ok
[ 1744.958134] drivers/usb/serial/ark3116.c: 149 > ok
[ 1744.959050] drivers/usb/serial/ark3116.c: 150 > ok
[ 1744.959963] drivers/usb/serial/ark3116.c: 151 < -71 bytes [0x5F]
[ 1744.960876] drivers/usb/serial/ark3116.c: 152 > ok
[ 1744.961792] drivers/usb/serial/ark3116.c: 153 < -71 bytes [0x5F]
[ 1744.962706] drivers/usb/serial/ark3116.c: 154 > ok
[ 1744.962706] usb 3-1: ark3116 converter now attached to ttyUSB0
[ 1744.962706] usbcore: registered new interface driver ark3116
and when I try to use it via pppd, it complains:
[ 1884.547341] drivers/usb/serial/ark3116.c: ark3116_ioctl cmd 0x540{1,2,4} not supported
and I get no answer to any AT command. So it looks like a regression,
but at least an incompatibility with the Etch libc.
Thanks,
Feri.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.26-1-686 depends on:
ii debconf [debconf-2.0] 1.5.11etch2 Debian configuration management sy
ii initramfs-tools [linux-initr 0.85i tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.26-1-686 recommends:
ii libc6-i686 2.3.6.ds1-13etch7 GNU C Library: Shared libraries [i
--- End Message ---
--- Begin Message ---
- To: Moritz Muehlenhoff <jmm@inutil.org>
- Cc: 495718-done@bugs.debian.org
- Subject: Re: not kernel version dependent
- From: Ferenc Wagner <wferi@niif.hu>
- Date: Tue, 02 Mar 2010 12:39:41 +0100
- Message-id: <87bpf79cle.fsf@tac.ki.iif.hu>
- In-reply-to: <20100216214713.GA6261@galadriel.inutil.org> (Moritz Muehlenhoff's message of "Tue, 16 Feb 2010 22:47:13 +0100")
- References: <20080819223151.5661.95264.reportbug@szonett.ki.iif.hu> <handler.495718.B.121918513314859.ack@bugs.debian.org> <87fxozxpkm.fsf_-_@szonett.ki.iif.hu> <20100216214713.GA6261@galadriel.inutil.org>
Moritz Muehlenhoff <jmm@inutil.org> writes:
> Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists.
I've been running modern kernels recently, but mostly vanilla ones.
Let's close this now, it doesn't affect me anymore at least, and you've
got plenty of more important bugs to triage.
--
Thanks,
Feri.
--- End Message ---
Reply to: