From: Bill Nottingham <notting@redhat.com>
To: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: oops when loading ehci_hcd
Date: Fri, 16 Apr 2004 04:23:11 -0400 [thread overview]
Message-ID: <20040416082311.GA2756@nostromo.devel.redhat.com> (raw)
With a 2.6.6-rc1 based kernel. Happened when loading ehci_hcd some
10 hours after booting, couldn't reproduce in initial attempts. I
suppose the question is also why it failed to init, but it certainly
didn't like the failure...
Bill
PCI: Enabling device 0000:00:1d.7 (0000 -> 0002)
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: illegal capability!
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: irq 11, pci mem 22946000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: init error -19ehci_hcd 0000:00:1d.7: remove, state 0
Unable to handle kernel NULL pointer dereference at virtual address 00000048
printing eip:
22a16b84
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<22a16b84>] Not tainted
EFLAGS: 00210002 (2.6.5-1.326)
EIP is at scan_async+0x36/0xf1 [ehci_hcd]
eax: 00000000 ebx: 1392c000 ecx: 228f75a8 edx: 00000000
esi: 00000000 edi: 1392c000 ebp: 00000000 esp: 1e977e3c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 28613, threadinfo=1e977000 task=186bf870)
Stack: 00000000 1392c000 00000000 03590444 c0000000 22a19736 1392c000 1392c07c
22a19540 00200206 00200206 0000002a 023b1e2a 00200246 c0000000 0211ed90
1e977e98 0211a5a7 00200206 00200206 00000029 023b1e29 00200246 00000000
Call Trace:
[<22a19736>] ehci_work+0x28/0x7d [ehci_hcd]
[<22a19540>] ehci_stop+0xe8/0x156 [ehci_hcd]
[<0211ed90>] printk+0x26a/0x2e3
[<0211a5a7>] __wake_up+0x8a/0xee
[<0225aa03>] usb_disconnect+0x16/0xd2
[<02262792>] usb_hcd_pci_remove+0x77/0x129
[<0226270c>] usb_hcd_pci_probe+0x3d7/0x3e6
[<0219de1e>] create_dir+0x7c/0x99
[<021ceb54>] pci_device_probe_static+0x2a/0x3d
[<021ceb82>] __pci_device_probe+0x1b/0x2c
[<021cebae>] pci_device_probe+0x1b/0x2d
[<0221ba49>] bus_match+0x27/0x45
[<0221bb15>] driver_attach+0x37/0x6a
[<0221bd27>] bus_add_driver+0x6a/0x81
[<0221c033>] driver_register+0x48/0x50
[<021ced0c>] pci_register_driver+0x84/0x9f
[<228e501b>] init+0x1b/0x22 [ehci_hcd]
[<02136583>] sys_init_module+0x1ef/0x2c6
Code: 8b 70 48 85 f6 74 71 8d 46 4c 39 46 4c 74 31 8b 87 7c 02 00
<6>USB Universal Host Controller Interface driver v2.2
next reply other threads:[~2004-04-16 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 8:23 Bill Nottingham [this message]
2004-04-16 18:14 ` [linux-usb-devel] " David Brownell
2004-04-16 18:42 ` Bill Nottingham
2004-04-17 3:08 ` Bill Nottingham
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=20040416082311.GA2756@nostromo.devel.redhat.com \
--to=notting@redhat.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
all inboxes | Powered by JetHome®