From: Marcel Holtmann <marcel@holtmann.org>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Oops in hci_usb
Date: Wed, 05 May 2004 21:29:12 +0200 [thread overview]
Message-ID: <1083785352.4420.33.camel@pegasus> (raw)
In-Reply-To: <20040505190725.GB1339@kos.to>
Hi Riku,
> Here's an oops with SCO options enabled and without preempt. I wonder if
> symbols are resolved from some wrong place, thou. Anyway, these oops
> don't look like they are preempt-related.
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.
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-05-05 19:29 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 [this message]
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=1083785352.4420.33.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=riku.voipio@iki.fi \
/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