Hi Folks,
the second Bluetooth kernel patch for 2.6.0 is now available [1] and it
fixes some more HCI USB driver problems. But the important thing is that
it contains a kernel driver for loading the firmware into the Broadcom
Blutonium devices. Everyone who had problems with bluefw should give it
a try. Here is the changelog:
o Convert interrupt handlers to use irqreturn_t
o Support for Broadcom Blutonium
o Improve blacklist handling
Regards
Marcel
[1] http://www.holtmann.org/linux/kernel/patch-2.6.0-mh2.gz
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Edd,
> > we must hunt this bug, because from your screenshot I see that it is in
> > the HCI core layer and that is really bad. Do you know the platform of
> > the other guy? Maybe it is an endian bug.
>
> It happens on my Athlon and my PowerPC. He has an IBM Thinkpad Intel(R)
> Pentium(R) M processor 1500MHz.
>
> > And to sum this up. It only happens with 2.6 and it freezes your machine
> > without any oops?
>
> Run fron console, I see the oops at
> http://heddley.com/edd/2004/01/bluez-oops.jpg
>
> > Do the keyboard leds are blinking?
>
> No blinking.
do you have any supported PCMCIA card? I like to know if this also
happens without the USB subsystem involved.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Wed, 2004-01-07 at 04:57, Marcel Holtmann wrote:
> we must hunt this bug, because from your screenshot I see that it is in
> the HCI core layer and that is really bad. Do you know the platform of
> the other guy? Maybe it is an endian bug.
It happens on my Athlon and my PowerPC. He has an IBM Thinkpad Intel(R)
Pentium(R) M processor 1500MHz.
> And to sum this up. It only happens with 2.6 and it freezes your machine
> without any oops?
Run fron console, I see the oops at
http://heddley.com/edd/2004/01/bluez-oops.jpg
> Do the keyboard leds are blinking?
No blinking.
-- Edd
Hi Edd,
> > >From hcidump, the lockup appears to happen before ever I see any traffic
> > from the dump: so it's as the connection is established from the remote
> > device (yes, my trusty P800!). I've tried with and without PREEMPT set.
>
> This wasn't quite accurate.
> To clear this up, here's a screen capture (taken the only way I could :)
>
> http://heddley.com/edd/2004/01/bluez-crash.jpg
>
> The red outlined bit is what happens on the connection that locks up the
> system.
we must hunt this bug, because from your screenshot I see that it is in
the HCI core layer and that is really bad. Do you know the platform of
the other guy? Maybe it is an endian bug.
And to sum this up. It only happens with 2.6 and it freezes your machine
without any oops? Do the keyboard leds are blinking?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Tue, 2004-01-06 at 23:54, Edd Dumbill wrote:
> >From hcidump, the lockup appears to happen before ever I see any traffic
> from the dump: so it's as the connection is established from the remote
> device (yes, my trusty P800!). I've tried with and without PREEMPT set.
This wasn't quite accurate.
To clear this up, here's a screen capture (taken the only way I could :)
http://heddley.com/edd/2004/01/bluez-crash.jpg
The red outlined bit is what happens on the connection that locks up the
system.
-- Edd
On Tue, 2004-01-06 at 22:28, Marcel Holtmann wrote:
> at the moment I am not able reproduce it. Try to track the problem and
> give me reports on it. It must be some kind of strange bug that can't be
> easily found.
I can reliably reproduce it here (just tried again with 2.6.1-rc2 (+your
patches). Can you recommend any technique I might be able to use to
provide you with more information?
>>From hcidump, the lockup appears to happen before ever I see any traffic
from the dump: so it's as the connection is established from the remote
device (yes, my trusty P800!). I've tried with and without PREEMPT set.
-- Edd
Hi Edd,
> > I've also been able to repeat this by attempting multiple rfcomm
> > connections using dund, under 2.6.0-test11. After a few
> > connect/disconnects on my Linux iBook the same lockup happened
> > (interestingly the screen jumped to full brightness at the same time.)
>
> To keep on this: I found somebody else on IRC today who also experiences
> these lockups with 2.6 kernels, so it's not just me.
>
> Nobody else here having them?
at the moment I am not able reproduce it. Try to track the problem and
give me reports on it. It must be some kind of strange bug that can't be
easily found.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Sat, 2004-01-03 at 14:43, Edd Dumbill wrote:
> I've also been able to repeat this by attempting multiple rfcomm
> connections using dund, under 2.6.0-test11. After a few
> connect/disconnects on my Linux iBook the same lockup happened
> (interestingly the screen jumped to full brightness at the same time.)
To keep on this: I found somebody else on IRC today who also experiences
these lockups with 2.6 kernels, so it's not just me.
Nobody else here having them?
-- Edd
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
I've also been able to repeat this by attempting multiple rfcomm
connections using dund, under 2.6.0-test11. After a few
connect/disconnects on my Linux iBook the same lockup happened
(interestingly the screen jumped to full brightness at the same time.)
-- Edd
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
I'm able to lock up the machine using the test app from openobex and
kernel 2.6. I've verified this on 2.6.0-test9 and -test11, and
2.6.1-rc1 -- all with and without the -mh2 patches.
The obex_test app has a bug when a transfer is cancelled, which in turn
seems to make the kernel bug happen. I presume this is because it
leaves the bluetooth devices in an odd state.
To repeat this, put obex_test into server mode,
obex_test -b ff:ff:ff
> s
send a file, cancel the transfer, then
> s
again. Send another file, obex_test crashes. Repeat the whole thing
until you get a machine lockup.
Note there are no kernel errors, the system appears to go into a tight
loop. I attach my kernel .config. I've tried with both CSR and
Broadcom based USB dongles. I am not running SMP or PREEMPT.
-- Edd
