From: Janne Pikkarainen <jaba@mikrobitti.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: USB/BlueTooth oops in 2.6.5
Date: Wed, 07 Apr 2004 10:14:44 +0300 [thread overview]
Message-ID: <1081322083.12029.27.camel@cs95250.pp.htv.fi> (raw)
In-Reply-To: <877jwse1pl.fsf@enki.rimspace.net>
On Wed, 2004-04-07 at 09:33, Daniel Pittman wrote:
> When I try to turn on the BlueTooth interface in my laptop, it turns on
> a USB device. Doing that with 2.6.5 generates the following error.
Enabling "SCO (voice) support" under Device Drivers --> Networking
support --> Bluetooth support --> Bluetooth device drivers --> HCI USB
driver causes the same error for me, after disabling SCO everything
works ok. The SCO really is the root of all evil, you know... ;-)
And this is with my desktop box: AMD Athlon XP 2400+ and Asus A7V-133
motherboard, with some USB bluetooth dongle made by SCM.
I hope this little piece of information helps you.
> usb 3-1: new full speed USB device using address 2
> Unable to handle kernel NULL pointer dereference at virtual address 00000004
> printing eip:
> c02c43b2
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c02c43b2>] Not tainted
> EFLAGS: 00010296 (2.6.5-enki)
> EIP is at usb_disable_interface+0x14/0x46
> eax: d24ca780 ebx: 00000000 ecx: 00000282 edx: dff6f100
> esi: 00000002 edi: 00000000 ebp: d4dedc00 esp: dfdafd48
> ds: 007b es: 007b ss: 0068
> Process khubd (pid: 5, threadinfo=dfdae000 task=dff0e080)
> Stack: 00000002 0000000b 00000001 00000002 ce3dcdb0 d4dedc00 c02c4608 d4dedc00
> d24ca780 0000000b 00000001 00000002 00000001 00000000 00000000 00001388
> 00000000 d24ca780 00000000 d59f9880 d59f9938 d24cac80 c02f283d d4dedc00
> Call Trace:
> [<c02c4608>] usb_set_interface+0xb7/0x173
> [<c02f283d>] hci_usb_probe+0x22f/0x480
> [<c015a392>] alloc_inode+0x146/0x14b
> [<c01715f5>] sysfs_new_inode+0x5d/0xa2
> [<c02bf03b>] usb_probe_interface+0x61/0x6e
> [<c024b86d>] bus_match+0x3f/0x6a
> [<c024b8d9>] device_attach+0x41/0x91
> [<c024ba98>] bus_add_device+0x5b/0x9f
> [<c024aad4>] device_add+0xa1/0x120
> [<c02c4996>] usb_set_configuration+0x1d4/0x25f
> [<c02bfdc2>] usb_new_device+0x250/0x3c3
> [<c02c14f1>] hub_port_connect_change+0x177/0x274
> [<c02c1895>] hub_events+0x2a7/0x2fa
> [<c02c1915>] hub_thread+0x2d/0xe4
> [<c0116159>] default_wake_function+0x0/0x12
> [<c02c18e8>] hub_thread+0x0/0xe4
> [<c0104d1d>] kernel_thread_helper+0x5/0xb
>
> Code: 80 7b 04 00 74 24 31 f6 8b 43 0c 83 c7 01 0f b6 44 30 02 83
next prev parent reply other threads:[~2004-04-07 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 6:33 Daniel Pittman
2004-04-07 7:14 ` Janne Pikkarainen [this message]
2004-04-07 18:10 ` Greg KH
2004-04-09 17:55 Steven Walter
2004-04-09 18:22 ` 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=1081322083.12029.27.camel@cs95250.pp.htv.fi \
--to=jaba@mikrobitti.fi \
--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®