public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Oops in hci_usb
Date: Thu, 6 May 2004 21:28:42 +0200	[thread overview]
Message-ID: <200405062128.42044.cijoml@volny.cz> (raw)
In-Reply-To: <20040506184816.GA7468@kos.to>

Send us 

hciconfig -a
hciconfig hci0 revision.

Possibly it is not CSR based dongle. We prefer using CSR based dongles

Michal

On Thursday 06 of May 2004 20:48, Riku Voipio wrote:
> On Wed, May 05, 2004 at 09:29:12PM +0200, Marcel Holtmann wrote:
> > this is a wild guess, but maybe the linking of the USB device into the
> > /sys structure causes this problem. So please comment out this line
> >
> > 	SET_HCIDEV_DEV(hdev, &intf->dev);
> >
> > in the hci_usb driver and try again.
>
> Seemingly didn't help..
>
> usb 4-1: USB disconnect, address 2
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000000
>  printing eip:
> c019b4bf
> *pde = 00000000
> Oops: 0000 [#1]
> CPU:    0
> EIP:    0060:[<c019b4bf>]    Not tainted
> EFLAGS: 00010246   (2.6.6-rc-noprempt3)
> EIP is at get_kobj_path_length+0x1a/0x31
> eax: 00000000   ebx: 00000000   ecx: ffffffff   edx: d993cf38
> esi: 00000001   edi: 00000000   ebp: ffffffff   esp: dd235e00
> ds: 007b   es: 007b   ss: 0068
> Process khubd (pid: 514, threadinfo=dd234000 task=dd28c830)
> Stack: c01c4e80 dd8d1819 dd8d1800 dd382390 c019b65e c02d9900 d993cf38
> 00000100 e016f8a0 c014ece7 dd235e40 dd8d1800 00000000 c02a4ee0 e016c591
> 00000000 c027ef6f d993cf38 d993cf30 e016f840 e016f8a0 c019b7e2 c027de26
> c02d9900 Call Trace:
>  [<c01c4e80>] class_hotplug_filter+0x0/0x2c
>  [<c019b65e>] kset_hotplug+0x139/0x268
>  [<c014ece7>] lookup_hash+0x1f/0x23
>  [<c019b7e2>] kobject_hotplug+0x55/0x57
>  [<c019bafb>] kobject_del+0x1b/0x33
>  [<c01c50df>] class_device_del+0x88/0xae
>  [<e0167d5c>] hci_unregister_dev+0x13/0x74 [bluetooth]
>  [<e015e8d9>] hci_usb_disconnect+0x35/0x7c [hci_usb]
>  [<e00870e0>] usb_unbind_interface+0x7a/0x7c [usbcore]
>  [<c01c4565>] device_release_driver+0x64/0x66
>  [<c01c4689>] bus_remove_device+0x55/0x96
>  [<c01c3756>] device_del+0x5d/0x9b
>  [<c01c37a7>] device_unregister+0x13/0x23
>  [<e008c891>] usb_disable_device+0x71/0xac [usbcore]
>  [<e0087bbd>] usb_disconnect+0x9b/0xe8 [usbcore]
>  [<e0089ac3>] hub_port_connect_change+0x26f/0x274 [usbcore]
>  [<e00894b4>] hub_port_status+0x45/0xb0 [usbcore]
>  [<e0089d6f>] hub_events+0x2a7/0x2fa [usbcore]
>  [<e0089def>] hub_thread+0x2d/0xe4 [usbcore]
>  [<c0103982>] ret_from_fork+0x6/0x14
>  [<c0112200>] default_wake_function+0x0/0x12
>  [<e0089dc2>] hub_thread+0x0/0xe4 [usbcore]
>  [<c0101f7d>] kernel_thread_helper+0x5/0xb
>
> Code: f2 ae f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 ea 5b 89 f0 5e


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-05-06 19:28 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
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 [this message]
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=200405062128.42044.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --cc=bluez-users@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