[driverloader] kernel 2.6.11

[Linuxant support (Jonathan)]

Hi,

with the stack trace you have provided in your last post, we have 
located the source of the problem and it will be fixed in the next 
release of DriverLoader.

In the meantime, you could ignore this stack trace since it doesn't 
affect the stability of your system. Alternatively, you could re-compile 
your kernel without the 'CONFIG_PREEMPT' option enabled and re-compile 
the DriverLoader module with the 'dldrconfig -k' command in a root shell.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


Max wrote:
> While DriverLoader 2.25 is visually working fine, in the syslog I see a 
> whole bunch of messages like
> 
> BUG: using smp_processor_id() in preemptible [00000001] code: 
> kdldrd/wlan0/19351caller is driverloader157_+0x29/0x210 [driverloader]
>  [<c02842d1>] smp_processor_id+0xa1/0xb0
>  [<f99eace9>] driverloader157_+0x29/0x210 [driverloader]
>  [<f99eace9>] driverloader157_+0x29/0x210 [driverloader]
>  [<f99eb1d5>] driverloader155_+0x15/0x40 [driverloader]
>  [<f99e9504>] driverloader184_+0x14/0x30 [driverloader]
>  [<f99e44a2>] driverloader297_+0x52/0x3e0 [driverloader]
>  [<f99d93a6>] NdisWrapGetRssi+0x36/0x40 [driverloader]
>  [<f99c97f4>] netndis_stats_update+0x94/0x370 [driverloader]
>  [<c0118fc0>] __wake_up+0x40/0x60
>  [<c01012bf>] __switch_to+0x13f/0x1f0
>  [<c046803e>] _spin_unlock_irq+0xe/0x30
>  [<c0117707>] finish_task_switch+0x37/0x80
>  [<c0466845>] schedule+0x325/0x650
>  [<f99d1f2e>] dldr_thread+0x19e/0x210 [driverloader]
>  [<c0118ef0>] default_wake_function+0x0/0x20
>  [<c01028f2>] ret_from_fork+0x6/0x14
>  [<c0118ef0>] default_wake_function+0x0/0x20
>  [<f99d1d90>] dldr_thread+0x0/0x210 [driverloader]
>  [<c0100995>] kernel_thread_helper+0x5/0x10
> 
> What's going on?
> 
> Max
> 
> Linuxant support (Jonathan) wrote:
> 
>> Hi,
>>
>> a similar patch was applied to DriverLoader 2.25 to be able to use 
>> DriverLoader on the 2.6.11 kernel. DriverLoader 2.25 will be released 
>> soon, likely today.
>>
>> Regards,
>>
>>
>> Jonathan
>> Technical specialist / Linuxant
>> www.linuxant.com
>> support at linuxant.com
>>
>>
>> Max wrote:
>>
>>> Joern,
>>>
>>> I confirm that everything works fine.
>>> Thank you very much!
>>>
>>> Max
>>>
>>> Joern Heissler wrote:
>>>
>>>> Hi Max,
>>>> it's very easy to fix this:
>>>>
>>>> /usr/lib/driverloder/modules/GPL/oscompat.h  line 489
>>>>
>>>> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 10)) && 
>>>> !defined(irq_exit)
>>>> #define softirq_pending(cpu)      __IRQ_STAT((cpu), __softirq_pending)
>>>> #define irq_exit() \
>>>>
>>>> just add this second line (#define softirq_pending....)
>>>>
>>>> I'm not really sure this is correct, but wlan is working, no kernel
>>>> oopses etc.
>>>>
>>>> Joern
>>>>
>>>>
>>>> On Wed, Mar 02, 2005 at 08:33:26PM -0800, Max wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> driverloader 2.24 reports undefined symbol softirq_pending with 
>>>>> Linux kernel 2.6.11
>>>>>
>>>>> Max
>>>>> _______________________________________________
>>>>> driverloader mailing list
>>>>> driverloader at lists.linuxant.com
>>>>> https://www.linuxant.com/mailman/listinfo/driverloader
>>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> driverloader mailing list
>>> driverloader at lists.linuxant.com
>>> https://www.linuxant.com/mailman/listinfo/driverloader
>>
>>
>>
>>
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader