Re: Oops apparently related to driverloader

Hi,

it seems that DriverLoader is the source of the problem. What was the 
previous version of DriverLoader you were using without these problems? 
Could you please send to [email protected] the output of 'dumpdiag'? 
Type the following in a root shell:

---
dldrconfig --dumpdiag
---

Just send us the generated file located in /tmp 
('driverloaderdiag.txt'). It'll help us solve the problem.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
[email protected]



Søren Boll Overgaard wrote:
> Hi,
> 
> Summary:
> My kernel has begun oopsing after I upgraded driverloader to version 2.33.
> 
> 
> The longer story:
> I recently upgraded to driverloader 2.33 via the Debian package available at
> http://linuxant.com:
> 
> [boll@andariel ~]$ dpkg -l|grep -i driverlo
> ii  driverloader                          2.33
> Linuxant DriverLoader for Wireless LAN devic
> 
> Since then I have experienced problems, in the sense that a few kernel oopses
> have occurred.
> 
> The output of these are at:
> http://soren.overgaard.org/stuff/oops
> http://soren.overgaard.org/stuff/oops2
> 
> I am by no means an expert in parsing oops output, but as far as I can tell,
> the error occurs somewhere inside the driverloader module.
> 
> Sporadic google searching has yielded no relevant information.
> 
> Any suggestions on how to fix this, or some way of debugging the problem would 
> be greatly appreciated.
>