[driverloader] Driverloader and bluetooth cooperation problems

[Dimitris Stasinopoulos]

Hi everyone,

I have been stress testing driverloader for the last few days, with what I 
call "amazing results" so far. Great work guys! However, I have tracked 
an issue, which could affect other people as well, so I feel like 
reporting it.

I'm having kernel panics when I'm using driverloader for my Intel 2100/PRO 
miniPCI in conjuction with the built-in bluetooth module of this laptop. 
Specifically:

a) If I only use driverloader (ie. the hci_usb bluetooth kernel module is 
not inserted), all is well, the system is rock stable.
b) If I only use the bluetooth module (ie. the driverloader module is not 
inserted), all is again well, the system rocks.
c) If both modules are inserted and used, problems begin appearing after a 
while. Apps may quit unexpectably , apps simply don't start, and after a 
while, the kernel panics. If I'm quick enough to realise it's about to 
happen (the system starts becoming unresponsive), I switch from X to the 
system log console (Control+Alt+F10), where I can shortly see the kernel 
panic message, and the relevant info. Usually, the current process is 
init or some other child/thread of init with pid 0. Of course, at that 
stage I can't save the message, and copying it by hand is rather tedious 
to do.

So, my question is: What can I do to find out which is the cause of the 
problem: hci_usb or driverloader? I'm willing to help the Linuxant people 
in tracking this issue down, because this might not be just a bluetooth 
cooperation problem, but something more generic that could affect other 
people as well.

Info:
HP compaq nx7000
Intel 2100/PRO miniPCI
Built-in USB bluetooth module (gets "inserted" when the wireless button on 
the button is pressed. At that time, the radio of the Intel card is also 
activated)
Linux 2.4.22 compiled from clean sources (no ACPI patches)
Driverloader 1.44

Dimitris

-- 
Perhaps it IS a good day to die! I say we ship the software!