Re: Problems with USB-Serial adapter after upgrade to 2.6.26-1
We received the following problem about usb-serial in 2.6.26. Is this
a known issue?
* u7l11ey@mail.lrz-muenchen.de <u7l11ey@mail.lrz-muenchen.de> [2008-08-30 20:33]:
> Hi all,
>
> yesterday I did an "apt-get dist-upgrade" on my NSLU2 running Debian lenny
> (armel version). Now I have kernel 2.6.26-1-ixp4xx.
>
> I'm using an USB-to-Serial adapter based on the pl2303 chipset, which has
> been working flawlessly with all previous versions of Debian I had
> installed on that NSLU2. Now I get repeated errors on this interface, with
> error messages in syslog like these:
>
> Aug 30 20:20:06 slug kernel: [43051075.690000] ------------[ cut here
> ]------------
> Aug 30 20:20:06 slug kernel: [43051075.690000] WARNING: at
> drivers/usb/serial/usb-serial.c:322 serial_write_room+0x50/0x7c
> [usbserial]()
> Aug 30 20:20:06 slug kernel: [43051075.700000] Modules linked in: evdev
> pl2303 ixp4xx_beeper ixp4xx_eth ixp4xx_npe firmware_class ixp4xx_qmgr
> usbserial ext3 jbd mbcache sd_mod usb_storage scsi_mod ohci_hcd ehci_hcd
> usbcore
> Aug 30 20:20:06 slug kernel: [43051075.720000] [<c0029f74>]
> (dump_stack+0x0/0x14) from [<c003e6bc>] (warn_on_slowpath+0x4c/0x84)
> Aug 30 20:20:06 slug kernel: [43051075.730000] [<c003e670>]
> (warn_on_slowpath+0x0/0x84) from [<bf09d4d0>] (serial_write_room+0x50/0x7c
> [usbserial])
> Aug 30 20:20:06 slug kernel: [43051075.740000] r6:c0950400 r5:00000043
> r4:c1c4b000
> Aug 30 20:20:06 slug kernel: [43051075.740000] [<bf09d480>]
> (serial_write_room+0x0/0x7c [usbserial]) from [<c01531e8>]
> (tty_write_room+0x24/0x30)
> Aug 30 20:20:06 slug kernel: [43051075.750000] r4:c0950400
> Aug 30 20:20:06 slug kernel: [43051075.760000] [<c01531c4>]
> (tty_write_room+0x0/0x30) from [<c015107c>] (opost+0x1c/0x1b0)
> Aug 30 20:20:06 slug kernel: [43051075.760000] [<c0151060>]
> (opost+0x0/0x1b0) from [<c0151278>] (echo_char+0x68/0x70)
> Aug 30 20:20:06 slug kernel: [43051075.770000] r5:c0950400 r4:00000043
> Aug 30 20:20:06 slug kernel: [43051075.780000] [<c0151210>]
> (echo_char+0x0/0x70) from [<c0152720>] (n_tty_receive_buf+0xb88/0xe08)
> Aug 30 20:20:06 slug kernel: [43051075.780000] r5:c0950c00 r4:00000043
> Aug 30 20:20:06 slug kernel: [43051075.790000] [<c0151b98>]
> (n_tty_receive_buf+0x0/0xe08) from [<c014e70c>]
> (flush_to_ldisc+0xdc/0x174)
> Aug 30 20:20:06 slug kernel: [43051075.800000] [<c014e630>]
> (flush_to_ldisc+0x0/0x174) from [<c004ea70>] (run_workqueue+0xbc/0x150)
> Aug 30 20:20:06 slug kernel: [43051075.810000] r8:00000000 r7:00000000
> r6:c014e630 r5:c1c26000 r4:c1c01940
> Aug 30 20:20:06 slug kernel: [43051075.810000] [<c004e9b4>]
> (run_workqueue+0x0/0x150) from [<c004f524>] (worker_thread+0xa8/0xbc)
> Aug 30 20:20:06 slug kernel: [43051075.820000] r6:c004f47c r5:c1c01940
> r4:c1c01948
> Aug 30 20:20:06 slug kernel: [43051075.830000] [<c004f47c>]
> (worker_thread+0x0/0xbc) from [<c0052588>] (kthread+0x5c/0x94)
> Aug 30 20:20:06 slug kernel: [43051075.840000] r5:c1c01940 r4:c1c26000
> Aug 30 20:20:06 slug kernel: [43051075.840000] [<c005252c>]
> (kthread+0x0/0x94) from [<c00419b0>] (do_exit+0x0/0x6a4)
> Aug 30 20:20:06 slug kernel: [43051075.850000] r6:00000000 r5:00000000
> r4:00000000
> Aug 30 20:20:06 slug kernel: [43051075.850000] ---[ end trace
> 28dbfda44f8c329c ]---
> Aug 30 20:20:06 slug kernel: [43051075.860000] ------------[ cut here
> ]------------
> Aug 30 20:20:06 slug kernel: [43051075.860000] WARNING: at
> drivers/usb/serial/usb-serial.c:309 serial_write+0x74/0xac [usbserial]()
> Aug 30 20:20:06 slug kernel: [43051075.870000] Modules linked in: evdev
> pl2303 ixp4xx_beeper ixp4xx_eth ixp4xx_npe firmware_class ixp4xx_qmgr
> usbserial ext3 jbd mbcache sd_mod usb_storage scsi_mod ohci_hcd ehci_hcd
> usbcore
> Aug 30 20:20:06 slug kernel: [43051075.890000] [<c0029f74>]
> (dump_stack+0x0/0x14) from [<c003e6bc>] (warn_on_slowpath+0x4c/0x84)
> Aug 30 20:20:06 slug kernel: [43051075.900000] [<c003e670>]
> (warn_on_slowpath+0x0/0x84) from [<bf09d570>] (serial_write+0x74/0xac
> [usbserial])
> Aug 30 20:20:06 slug kernel: [43051075.910000] r6:c1c27e5f r5:00000001
> r4:c1c4b000
> Aug 30 20:20:06 slug kernel: [43051075.910000] [<bf09d4fc>]
> (serial_write+0x0/0xac [usbserial]) from [<c014cdc8>]
> (tty_put_char+0x40/0x48)
> Aug 30 20:20:06 slug kernel: [43051075.920000] r6:c0950400 r5:00000043
> r4:c0950400
> Aug 30 20:20:06 slug kernel: [43051075.930000] [<c014cd88>]
> (tty_put_char+0x0/0x48) from [<c01511e4>] (opost+0x184/0x1b0)
> Aug 30 20:20:06 slug kernel: [43051075.940000] [<c0151060>]
> (opost+0x0/0x1b0) from [<c0151278>] (echo_char+0x68/0x70)
> Aug 30 20:20:06 slug kernel: [43051075.950000] r5:c0950400 r4:00000043
> Aug 30 20:20:06 slug kernel: [43051075.950000] [<c0151210>]
> (echo_char+0x0/0x70) from [<c0152720>] (n_tty_receive_buf+0xb88/0xe08)
> Aug 30 20:20:06 slug kernel: [43051075.960000] r5:c0950c00 r4:00000043
> Aug 30 20:20:06 slug kernel: [43051075.960000] [<c0151b98>]
> (n_tty_receive_buf+0x0/0xe08) from [<c014e70c>]
> (flush_to_ldisc+0xdc/0x174)
> Aug 30 20:20:06 slug kernel: [43051075.970000] [<c014e630>]
> (flush_to_ldisc+0x0/0x174) from [<c004ea70>] (run_workqueue+0xbc/0x150)
> Aug 30 20:20:06 slug kernel: [43051075.980000] r8:00000000 r7:00000000
> r6:c014e630 r5:c1c26000 r4:c1c01940
> Aug 30 20:20:06 slug kernel: [43051075.990000] [<c004e9b4>]
> (run_workqueue+0x0/0x150) from [<c004f524>] (worker_thread+0xa8/0xbc)
> Aug 30 20:20:06 slug kernel: [43051076.000000] r6:c004f47c r5:c1c01940
> r4:c1c01948
> Aug 30 20:20:06 slug kernel: [43051076.000000] [<c004f47c>]
> (worker_thread+0x0/0xbc) from [<c0052588>] (kthread+0x5c/0x94)
> Aug 30 20:20:06 slug kernel: [43051076.010000] r5:c1c01940 r4:c1c26000
> Aug 30 20:20:06 slug kernel: [43051076.020000] [<c005252c>]
> (kthread+0x0/0x94) from [<c00419b0>] (do_exit+0x0/0x6a4)
> Aug 30 20:20:06 slug kernel: [43051076.020000] r6:00000000 r5:00000000
> r4:00000000
> Aug 30 20:20:06 slug kernel: [43051076.030000] ---[ end trace
> 28dbfda44f8c329c ]---
>
> These errors happen at irregular intervals, in between the serial
> communication works ok. I don't know how to interpret the error messages.
> Is this a known problem, and what can I do about it?
>
> Please let me know if more detailed information is necessary to track down
> this problem.
>
> Regards, Richard
>
>
> --
> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: