From: Alex Riesen <fork0@users.sf.net>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: 2.5.42-ac1: modprobe uhci-hcd: sleeping function called from illegal context
Date: Sun, 13 Oct 2002 14:21:39 +0200 [thread overview]
Message-ID: <20021013122139.GA377@steel> (raw)
Just tried "modprobe uhci-hcd". Nothing evil observed besides that.
syslog:
Oct 13 13:04:08 steel kernel: drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.0
Oct 13 13:04:08 steel kernel: PCI: Found IRQ 10 for device 00:04.2
Oct 13 13:04:08 steel kernel: PCI: Sharing IRQ 10 with 00:04.3
Oct 13 13:04:08 steel kernel: PCI: Sharing IRQ 10 with 00:0f.0
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd-pci.c: uhci-hcd @ 00:04.2, VIA Technologies, Inc. USB
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd-pci.c: irq 10, io base 0000b400
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd.c: new USB bus registered, assigned bus number 1
Oct 13 13:04:08 steel kernel: drivers/usb/core/hub.c: USB hub found at 0
Oct 13 13:04:08 steel kernel: drivers/usb/core/hub.c: 2 ports detected
Oct 13 13:04:08 steel kernel: PCI: Found IRQ 10 for device 00:04.3
Oct 13 13:04:08 steel kernel: PCI: Sharing IRQ 10 with 00:04.2
Oct 13 13:04:08 steel kernel: PCI: Sharing IRQ 10 with 00:0f.0
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd-pci.c: uhci-hcd @ 00:04.3, VIA Technologies, Inc. USB (#2)
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd-pci.c: irq 10, io base 0000b000
Oct 13 13:04:08 steel kernel: drivers/usb/core/hcd.c: new USB bus registered, assigned bus number 2
Oct 13 13:04:08 steel kernel: drivers/usb/core/hub.c: USB hub found at 0
Oct 13 13:04:08 steel kernel: drivers/usb/core/hub.c: 2 ports detected
Oct 13 13:04:09 steel kernel: Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Oct 13 13:04:09 steel kernel: Call Trace:
Oct 13 13:04:09 steel kernel: [<c0116184>] __might_sleep+0x54/0x60
Oct 13 13:04:09 steel kernel: [<dc846f56>] .rodata+0x1056/0x1a74 [usbcore]
Oct 13 13:04:09 steel kernel: [<dc8419dd>] usb_hub_events+0x65/0x2b8 [usbcore]
Oct 13 13:04:09 steel kernel: [<dc846f56>] .rodata+0x1056/0x1a74 [usbcore]
Oct 13 13:04:09 steel kernel: [<dc841c65>] usb_hub_thread+0x35/0xe0 [usbcore]
Oct 13 13:04:09 steel kernel: [<dc841c30>] usb_hub_thread+0x0/0xe0 [usbcore]
Oct 13 13:04:09 steel kernel: [<c0114f60>] default_wake_function+0x0/0x34
Oct 13 13:04:09 steel kernel: [<dc84c9ec>] khubd_wait+0x4/0xc [usbcore]
Oct 13 13:04:09 steel kernel: [<dc84c9ec>] khubd_wait+0x4/0xc [usbcore]
Oct 13 13:04:09 steel kernel: [<c01054a9>] kernel_thread_helper+0x5/0xc
Oct 13 13:04:09 steel kernel:
Oct 13 13:04:09 steel kernel: drivers/usb/core/hub.c: new USB device 00:04.2-2, assigned address 2
some of /proc/pci:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT8605 [ProSavage PM133] (rev 129).
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP] (rev 0).
Master Capable. No bursts. Min Gnt=8.
Bus 0, device 4, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 34).
Bus 0, device 4, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 16).
Master Capable. Latency=32.
I/O at 0xb800 [0xb80f].
Bus 0, device 4, function 2:
USB Controller: VIA Technologies, Inc. USB (rev 16).
IRQ 10.
Master Capable. Latency=32.
I/O at 0xb400 [0xb41f].
Bus 0, device 4, function 3:
USB Controller: VIA Technologies, Inc. USB (#2) (rev 16).
IRQ 10.
Master Capable. Latency=32.
I/O at 0xb000 [0xb01f].
Bus 0, device 4, function 4:
Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 48).
next reply other threads:[~2002-10-13 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 12:21 Alex Riesen [this message]
2002-10-14 0:27 ` 2.5.42-ac1: modprobe uhci-hcd: sleeping function called from illegal context 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=20021013122139.GA377@steel \
--to=fork0@users.sf.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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