From: Manuel Hartl <mhartl@hartl-it.de>
To: linux-kernel@vger.kernel.org
Subject: USB module crash
Date: Fri, 25 Nov 2005 08:52:58 +0100 [thread overview]
Message-ID: <4386C2DA.6070002@hartl-it.de> (raw)
hi list,
last night (i think again) usb module(s) crashed. the running usb
devices are a avm fritz usb dsl 2 and a usb mouse. i do not think this
is avm related (cdslusb2 module), maybe an acpi/power management error?
please loook at the included stack trace.
can someone tell me (by looking at the trace), what could be the problem
here?
hardware:
asus a8v deluxe (via k8t800 chipset) / socket 939 / amd64 3000+
cool and quiet was active in bios, but no module was loaded
(powernow_k8), acpi/apic is enabled.
Nov 25 02:26:40 media kernel: [<c029b1ec>] kref_get+0x3c/0x40
Nov 25 02:26:40 media kernel: [<f89a2f9c>] usb_get_urb+0xc/0x10 [usbcore]
Nov 25 02:26:40 media kernel: [<f89a212a>] hcd_submit_urb+0xda/0x1f0
[usbcore]
Nov 25 02:26:40 media kernel: [<f89a31b6>] usb_submit_urb+0x216/0x3e0
[usbcore]
Nov 25 02:26:40 media kernel: [<f89a31b6>] usb_submit_urb+0x216/0x3e0
[usbcore]
Nov 25 02:26:40 media kernel: [<fa59e2cb>] LeaveCritical+0xb/0x10
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa60943e>] usb_write+0xee/0xf0 [fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa609494>] usb_read+0x54/0xa0 [fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa6095c1>] os_usb_submit_tx+0x61/0x80
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa609d65>] OSHWTxBuffer+0x65/0x80
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa5e7e00>] Block_TxHandler+0x0/0x10
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa5e7e71>] Block_TxSend+0x21/0x70
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa5e84cc>] Block_RxHandler+0x42c/0x500
[fcdslusb2]
Nov 25 02:26:40 media kernel: [<fa609110>] rx_handler+0xc0/0xd0 [fcdslusb2]
Nov 25 02:26:40 media kernel: [<c011b72a>] tasklet_action+0x3a/0x60
Nov 25 02:26:40 media kernel: [<c011b492>] __do_softirq+0x42/0x90
Nov 25 02:26:40 media kernel: [<c011b506>] do_softirq+0x26/0x30
Nov 25 02:26:40 media kernel: [<c0104a2e>] do_IRQ+0x1e/0x30
Nov 25 02:26:40 media kernel: [<c0103516>] common_interrupt+0x1a/0x20
Nov 25 02:26:40 media kernel: [<c02e1bf3>] acpi_processor_idle+0x0/0x27f
Nov 25 02:26:40 media kernel: [<c02e1cf4>] acpi_processor_idle+0x101/0x27f
Nov 25 02:26:40 media kernel: [<c0100ca2>] cpu_idle+0x42/0x60
Nov 25 02:26:40 media kernel: [<c04a281f>] start_kernel+0x16f/0x1b0
Nov 25 02:26:40 media kernel: [<c04a2380>] unknown_bootoption+0x0/0x1d0
greetings,
manuel.
next reply other threads:[~2005-11-25 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 7:52 Manuel Hartl [this message]
2005-11-25 7:58 ` USB module crash Arjan van de Ven
2005-11-25 18:57 ` Manuel Hartl
2005-11-25 23:34 ` 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=4386C2DA.6070002@hartl-it.de \
--to=mhartl@hartl-it.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.