From: Andrew Morton <akpm@osdl.org>
To: Alexander Hoogerhuis <alexh@boxed.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm6
Date: Thu, 15 Apr 2004 00:41:37 -0700 [thread overview]
Message-ID: <20040415004137.437b679c.akpm@osdl.org> (raw)
In-Reply-To: <87d669hfaa.fsf@dorker.boxed.no>
Alexander Hoogerhuis <alexh@boxed.no> wrote:
>
> And the mandatory mail about what goes oops on a new kernel:
If I had a dollar for every usb->sysfs/kobject oops...
> [booting...]
> ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 6 ports detected
> usb 3-1: USB disconnect, address 2
> Unable to handle kernel NULL pointer dereference at virtual address 00000070
> printing eip:
> c017efc1
> *pde = 00000000
> Oops: 0002 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[<c017efc1>] Not tainted VLI
> EFLAGS: 00010246 (2.6.5-mm6)
> EIP is at sysfs_hash_and_remove+0x2b/0x90
> eax: 00000000 ebx: 00000070 ecx: 00000070 edx: 00000000
> esi: 00000000 edi: c02bc0f4 ebp: f5fd4e70 esp: f5fd4e60
> ds: 007b es: 007b ss: 0068
> Process khubd (pid: 5218, threadinfo=f5fd4000 task=f5efa3b0)
> Stack: f5925a80 f8962ac0 f5b27530 f8962a60 f5fd4e8c c01f6406 f8962ac0 f8962aac
> f5b27400 f5b27400 f5f6c690 f5fd4e98 f8959003 f5f6c280 f5fd4eb4 f8935c52
> f88deb59 f5f6d800 f5f6c680 f5f6c680 f8937240 f5fd4ec4 f88d90c6 f5f6c690
> Call Trace:
> [<c01f6406>] class_device_del+0x88/0xb9
> [<f8959003>] hci_unregister_dev+0xb/0x94 [bluetooth]
Apparently bluetooth is known-broken. Do you actually have any bluetooth
hardware there?
next prev parent reply other threads:[~2004-04-15 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 6:04 2.6.5-mm6 Andrew Morton
2004-04-15 7:27 ` 2.6.5-mm6 Alexander Hoogerhuis
2004-04-15 7:41 ` Andrew Morton [this message]
2004-04-15 12:11 ` 2.6.5-mm6 James Morris
2004-04-18 10:00 ` 2.6.5-mm6 raven
2004-04-18 15:38 ` 2.6.5-mm6 Andrew Morton
2004-04-18 15:50 ` 2.6.5-mm6 raven
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=20040415004137.437b679c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alexh@boxed.no \
--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 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®