From: Greg KH <greg@kroah.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead
Date: Sun, 22 Jun 2008 11:42:53 -0700 [thread overview]
Message-ID: <20080622184253.GB18502@kroah.com> (raw)
In-Reply-To: <485E984B.1030306@aitel.hist.no>
On Sun, Jun 22, 2008 at 08:22:03PM +0200, Helge Hafting wrote:
> This is what I got:
> ------------[ cut here ]------------
> WARNING: at drivers/usb/serial/usb-serial.c:306 serial_write+0x62/0x89
> [usbserial]()
> Modules linked in: pl2303 usbserial sbs sbshc coretemp piix pcmcia ata_piix
> iTCO_wdt ata_generic bay hci_usb intel_agp
> Pid: 10, comm: events/1 Tainted: G W 2.6.26-rc2-hh1 #1
>
> Call Trace:
> [<ffffffff80236b54>] warn_on_slowpath+0x51/0x7a
> [<ffffffff8022c207>] __wake_up+0x38/0x4f
> [<ffffffff8024565c>] __queue_work+0x23/0x33
> [<ffffffff802456c8>] queue_work+0x37/0x40
> [<ffffffffa0045fa3>] :pl2303:pl2303_write+0xf2/0x101
> [<ffffffffa003c368>] :usbserial:serial_write+0x62/0x89
> [<ffffffff803a8e81>] tty_put_char+0x2b/0x2d
> [<ffffffff803ad3ca>] echo_char+0x47/0x60
> [<ffffffff803ade97>] n_tty_receive_buf+0x2b4/0xd76
> [<ffffffff8020a87e>] __switch_to+0xa2/0x396
> [<ffffffff8023028d>] hrtick_set+0x88/0xf6
> [<ffffffff80590b44>] thread_return+0x70/0xb4
> [<ffffffff8023f013>] lock_timer_base+0x26/0x4c
> [<ffffffff803a9abd>] flush_to_ldisc+0xf8/0x185
> [<ffffffff803a99c5>] flush_to_ldisc+0x0/0x185
> [<ffffffff8024520b>] run_workqueue+0x80/0x112
> [<ffffffff80245afe>] worker_thread+0xd9/0xe8
> [<ffffffff80248380>] autoremove_wake_function+0x0/0x2e
> [<ffffffff80245a25>] worker_thread+0x0/0xe8
> [<ffffffff80248264>] kthread+0x47/0x73
> [<ffffffff802318c1>] schedule_tail+0x28/0x5d
> [<ffffffff8020cf88>] child_rip+0xa/0x12
> [<ffffffff8024821d>] kthread+0x0/0x73
> [<ffffffff8020cf7e>] child_rip+0x0/0x12
>
> ---[ end trace 656e180042992f9e ]---
> I looked at the dmesg log because I have had lots of trouble with my gps
> lately. I first suspected the cable, but then I saw this.
>
> After this, I have to restart gpsd, and perhaps replug the cable to get
> things going again. Until it happens again. This is a 64-bit dualcore
> laptop.
Ick, that's not nice.
Can you enable debugging for the usb-serial core:
echo 1 > /sys/module/usbserial/parameters/debug
and then run whatever program you were running that causes this warning
and then send us the kernel log?
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-22 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 18:22 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead Helge Hafting
2008-06-22 18:42 ` Greg KH [this message]
2008-06-23 4:01 ` Andrew Morton
2008-06-25 11:00 ` Helge Hafting
2008-06-26 5:39 ` Greg KH
2008-06-25 11:30 ` Helge Hafting
2008-07-02 21:18 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080622184253.GB18502@kroah.com \
--to=greg@kroah.com \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox