From: wim delvaux <wim.delvaux@adaptiveplanet.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
Date: Mon, 12 Apr 2004 03:49:34 +0200 [thread overview]
Message-ID: <200404120349.34338.wim.delvaux@adaptiveplanet.com> (raw)
Hi all,
I have checked the devel list like greg pointed me out and after applying all
patches but with no help I turned back to 2.6.3.
However There I get bluetooth errors too.
hci_usb_isoc_rx_submit : hci0 isoc rx submit failed urb cec4e814 err -22
Two times
removing the usb dongle causes a kernel oops
call trace is (Typed over by hand)
EIP is at uhci_remove_pending_qhs+0x63/0xb8 [uhci_hcd]
...
process : hcid
calltrace :
uhci_irq+0x90/0x159 [uhci_hcd]
usb_hcd_irq+0x36/0x67 [usbbcore]
handle_IRQ_event+0x3a/0x64
do_IRQ+0x94/0x136
common_interrupt+0x18/0x20
That means that for I do not know what reason my two systems are completely
messed up because of usb/bluetooth problems (*** crying tears like rivers
***)
I tried with 2.4.25/2.4.26-rc2 2.6.3/2.6.5 and mm and even applied patches on
bluez download site
Then I can insert my dongle but when I unplug I get A WHOLE LOT of
'bad atomic while scheduling'
and a call trace with top function schedule
HELP
W
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-04-12 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 1:49 wim delvaux [this message]
2004-04-12 10:55 ` [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems Marcel Holtmann
2004-04-12 11:17 ` wim delvaux
2004-04-12 13:33 ` Marcel Holtmann
2004-04-12 14:21 ` wim delvaux
2004-04-12 14:55 ` Marcel Holtmann
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=200404120349.34338.wim.delvaux@adaptiveplanet.com \
--to=wim.delvaux@adaptiveplanet.com \
--cc=bluez-devel@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