From: Riku Voipio <riku.voipio@iki.fi>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Oops in hci_usb
Date: Tue, 4 May 2004 20:22:52 +0300 [thread overview]
Message-ID: <20040504172251.GA27072@kos.to> (raw)
In-Reply-To: <1083686495.4666.39.camel@pegasus>
Hi Marcel,
> > > do you enabled CONFIG_BT_HCIUSB_SCO in your kernel? If yes, disable it
> > > and try again.
> > Getting rid SCO option and updating to 2.6.6-RC3 makes the bluetooth
> > on x40 work like a charm, no more oops and pairing worked first try.
> > I can try 2.6.6-RC3 with CONFIG_BT_HCIUSB_SCO if you want to track
> > the problem deeper.
> please do so, because actually I don't know why it happens.
With -RC3 and SCO enabled, I get the following Oops: (Tanted due to
madwifi)
Unable to handle kernel NULL pointer dereference at virtual address
00000068
printing eip:
c017a671
*pde = 00000000
Oops: 0002 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c017a671>] Tainted: P
EFLAGS: 00010282 (2.6.6-rc3)
EIP is at sysfs_hash_and_remove+0x15/0x7d
eax: 00000000 ebx: e006c3e0 ecx: 00000068 edx: ffff0001
esi: dafc3680 edi: e006c380 ebp: e006c3e0 esp: ccc55e58
ds: 007b es: 007b ss: 0068
Process khubd (pid: 7775, threadinfo=ccc54000 task=ccc3c3b0)
Stack: d3c87554 e0033d40 e006c3e0 c7804530 c01d2e4c dafc3680 c0293529 c01d31c4
c7804530 e006c3cc c7804400 c7804400 d7189400 d7189424 e00641eb c7804530
d3c87564 d3c87454 e0032d11 c7804400 d3c87554 e0033d40 d3c87c54 e0033d40
Call Trace:
[<c01d2e4c>] class_device_dev_unlink+0x1a/0x1e
[<c01d31c4>] class_device_del+0x75/0xae
[<e00641eb>] hci_unregister_dev+0x10/0x84 [bluetooth]
[<e0032d11>] hci_usb_disconnect+0x35/0x7c [hci_usb]
[<e00880e0>] usb_unbind_interface+0x7a/0x7c [usbcore]
[<c01d265d>] device_release_driver+0x64/0x66
[<c01d2781>] bus_remove_device+0x55/0x96
[<c01d184e>] device_del+0x5d/0x9b
[<c01d189f>] device_unregister+0x13/0x23
[<e008dcfb>] usb_disable_device+0x71/0xac [usbcore]
[<e0088bbd>] usb_disconnect+0x9b/0xe8 [usbcore]
[<e008abd3>] hub_port_connect_change+0x26f/0x274 [usbcore]
[<e008a5c4>] hub_port_status+0x45/0xb0 [usbcore]
[<e008aeab>] hub_events+0x2d3/0x346 [usbcore]
[<e008af4b>] hub_thread+0x2d/0xe4 [usbcore]
[<c0103b6e>] ret_from_fork+0x6/0x14
[<c01130ac>] default_wake_function+0x0/0x12
[<e008af1e>] hub_thread+0x0/0xe4 [usbcore]
[<c0101ffd>] kernel_thread_helper+0x5/0xb
Code: ff 48 68 78 63 89 34 24 8b 44 24 18 89 44 24 04 e8 66 ff ff
--
Riku Voipio | riku.voipio at iki.fi |
kirkkonummentie 33 | +358 44 5000343 --+--
02140 Espoo | |
dark> A bad analogy is like leaky screwdriver |
next prev parent reply other threads:[~2004-05-04 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 17:36 [Bluez-users] Oops in hci_usb Riku Voipio
2004-05-01 20:30 ` Nicholas A. Preyss
2004-05-01 21:22 ` Timothy Murphy
2004-05-03 12:26 ` Marcel Holtmann
2004-05-03 19:37 ` Riku Voipio
2004-05-04 16:01 ` Marcel Holtmann
2004-05-04 17:22 ` Riku Voipio [this message]
2004-05-04 17:30 ` Michal Semler
2004-05-04 17:41 ` Marcel Holtmann
2004-05-05 19:07 ` Riku Voipio
2004-05-05 19:29 ` Marcel Holtmann
2004-05-06 18:48 ` Riku Voipio
2004-05-06 19:28 ` Michal Semler
2004-05-06 21:03 ` Marcel Holtmann
[not found] ` <1083936143.8935.5.camel@metal.cisco.com>
2004-05-10 13:21 ` Marcel Holtmann
2004-05-10 14:04 ` Frederic Detienne
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=20040504172251.GA27072@kos.to \
--to=riku.voipio@iki.fi \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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