* [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
@ 2004-04-12 1:49 wim delvaux
2004-04-12 10:55 ` Marcel Holtmann
0 siblings, 1 reply; 6+ messages in thread
From: wim delvaux @ 2004-04-12 1:49 UTC (permalink / raw)
To: bluez-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
2004-04-12 1:49 [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems wim delvaux
@ 2004-04-12 10:55 ` Marcel Holtmann
2004-04-12 11:17 ` wim delvaux
0 siblings, 1 reply; 6+ messages in thread
From: Marcel Holtmann @ 2004-04-12 10:55 UTC (permalink / raw)
To: wim delvaux; +Cc: BlueZ Mailing List
Hi Wim,
> 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
please try 2.6.5-mh3.
Regards
Marcel
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
2004-04-12 10:55 ` Marcel Holtmann
@ 2004-04-12 11:17 ` wim delvaux
2004-04-12 13:33 ` Marcel Holtmann
0 siblings, 1 reply; 6+ messages in thread
From: wim delvaux @ 2004-04-12 11:17 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ Mailing List
I have tried with that version. (Applied the 2.6.5-mh3 patch)
However then I get these 'bad atomic' errors
I just retried with the 2.6.3 kernel and saw
'device not accepting address' messages error -110
And then
drivers/usb/host/uhci-hcd.c: uhci_result_control() failed with status 440000
[ceb01240] link (0eb011e2) element (0ecb9040)
0: [cecb9040] link (0ecb9080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0
EndPt=0 Dev=0, PID=2d(SETUP) (buf=0bd05e40)
1: [cecb9080] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0
Dev=0, PID=69(IN) (buf=00000000)
after a few inserts it gives
usb 1-1: new full speed USB device using address 10
usb 1-1: new device strings: Mfr=0, Product=0, SerialNumber=0
drivers/usb/core/usb.c: usb_hotplug
usb 1-1: registering 1-1:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
usb 1-1: registering 1-1:1.1 (config #1, interface 1)
drivers/usb/core/usb.c: usb_hotplug
usb 1-1: registering 1-1:1.2 (config #1, interface 2)
drivers/usb/core/usb.c: usb_hotplug
Bluetooth: HCI USB driver ver 2.4
hci_usb 1-1:1.0: usb_probe_interface
hci_usb 1-1:1.0: usb_probe_interface - got id
hci_usb 1-1:1.1: usb_probe_interface
hci_usb 1-1:1.2: usb_probe_interface
hci_usb 1-1:1.2: usb_probe_interface - got id
drivers/usb/core/usb.c: registered new driver hci_usb
hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
W
On Monday 12 April 2004 12:55, Marcel Holtmann wrote:
> Hi Wim,
>
> > 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
>
> please try 2.6.5-mh3.
>
> Regards
>
> Marcel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
2004-04-12 11:17 ` wim delvaux
@ 2004-04-12 13:33 ` Marcel Holtmann
2004-04-12 14:21 ` wim delvaux
0 siblings, 1 reply; 6+ messages in thread
From: Marcel Holtmann @ 2004-04-12 13:33 UTC (permalink / raw)
To: wim delvaux; +Cc: BlueZ Mailing List
Hi Wim,
> I have tried with that version. (Applied the 2.6.5-mh3 patch)
> However then I get these 'bad atomic' errors
where do you get them? In the hci_usb driver or in the USB subsystem?
> I just retried with the 2.6.3 kernel and saw
>
> 'device not accepting address' messages error -110
> And then
Know problem. Some broken device which needs a longer timeout value.
> drivers/usb/host/uhci-hcd.c: uhci_result_control() failed with status 440000
> [ceb01240] link (0eb011e2) element (0ecb9040)
> 0: [cecb9040] link (0ecb9080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0
> EndPt=0 Dev=0, PID=2d(SETUP) (buf=0bd05e40)
> 1: [cecb9080] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0
> Dev=0, PID=69(IN) (buf=00000000)
>
> after a few inserts it gives
>
> usb 1-1: new full speed USB device using address 10
> usb 1-1: new device strings: Mfr=0, Product=0, SerialNumber=0
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.0 (config #1, interface 0)
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.1 (config #1, interface 1)
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.2 (config #1, interface 2)
> drivers/usb/core/usb.c: usb_hotplug
> Bluetooth: HCI USB driver ver 2.4
> hci_usb 1-1:1.0: usb_probe_interface
> hci_usb 1-1:1.0: usb_probe_interface - got id
> hci_usb 1-1:1.1: usb_probe_interface
> hci_usb 1-1:1.2: usb_probe_interface
> hci_usb 1-1:1.2: usb_probe_interface - got id
> drivers/usb/core/usb.c: registered new driver hci_usb
> hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
> hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
Bug in the hci_usb driver. Disable CONFIG_BT_HCIUSB_SCO.
Regards
Marcel
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
2004-04-12 13:33 ` Marcel Holtmann
@ 2004-04-12 14:21 ` wim delvaux
2004-04-12 14:55 ` Marcel Holtmann
0 siblings, 1 reply; 6+ messages in thread
From: wim delvaux @ 2004-04-12 14:21 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ Mailing List
On Monday 12 April 2004 15:33, Marcel Holtmann wrote:
> Hi Wim,
>
> > I have tried with that version. (Applied the 2.6.5-mh3 patch)
> > However then I get these 'bad atomic' errors
>
> where do you get them? In the hci_usb driver or in the USB subsystem?
it scrolls by so fast that It is hardly visible on the console.
However I can detect that the call stack is only 3 entries deep
>
> > I just retried with the 2.6.3 kernel and saw
> >
> > 'device not accepting address' messages error -110
> > And then
>
> Know problem. Some broken device which needs a longer timeout value.
The device at hand is the Acer BT500 BT Dongle Where can I set that
timeout ?
>
> Bug in the hci_usb driver. Disable CONFIG_BT_HCIUSB_SCO.
OK
CU
W
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
2004-04-12 14:21 ` wim delvaux
@ 2004-04-12 14:55 ` Marcel Holtmann
0 siblings, 0 replies; 6+ messages in thread
From: Marcel Holtmann @ 2004-04-12 14:55 UTC (permalink / raw)
To: wim delvaux; +Cc: BlueZ Mailing List
Hi Wim,
> > where do you get them? In the hci_usb driver or in the USB subsystem?
>
> it scrolls by so fast that It is hardly visible on the console.
> However I can detect that the call stack is only 3 entries deep
try to use the netconsole support in 2.6.5.
> > Know problem. Some broken device which needs a longer timeout value.
>
> The device at hand is the Acer BT500 BT Dongle Where can I set that
> timeout ?
Look at the USB mailing list archive. I don't remember where it was, but
the Acer BT500 is one of these buggy dongles.
Regards
Marcel
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-04-12 14:55 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-12 1:49 [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems wim delvaux
2004-04-12 10:55 ` 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox