Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/18 ael <law_ence.dev@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.hartgers@gmail.com
Reply to: