ndiswrapper kernel messages filling my logs... TOO MUCH!

jkassemi · 11-06-2005, 08:45 PM

Hello everyone,

I've got ndiswrapper installed (and functional, mostly), for my linksys wmp54G... It worked just right with the 2.6.11 kernel, but I recompiled with the 2.6.13 kernel and now I'm having issues... I notice (infrequently and randomly), my CPU usage will top out... Taking a look at the output of top, I find that the klogd and the ndiswrapperwq processes are eating up my cpu. On top of that, my syslog increases in size until I restart (ndiswrapperwq process WILL NOT DIE! (kill -9 XXXX)).

Here's what's filling up the syslog:

Code:

Nov  6 18:29:30 localhost kernel: scheduling while atomic: ndiswrapwq/0xffffff01/3151
Nov  6 18:29:30 localhost kernel:  [<c03b4352>] schedule+0x612/0x620
Nov  6 18:29:30 localhost kernel:  [<c012af19>] worker_thread+0x269/0x290
Nov  6 18:29:30 localhost kernel:  [<dcc3bc80>] ndis_irq_bh+0x0/0xe0 [ndiswrapper]
Nov  6 18:29:30 localhost kernel:  [<c0117240>] default_wake_function+0x0/0x20
Nov  6 18:29:30 localhost kernel:  [<c0117240>] default_wake_function+0x0/0x20
Nov  6 18:29:30 localhost kernel:  [<c012acb0>] worker_thread+0x0/0x290
Nov  6 18:29:30 localhost kernel:  [<c012f265>] kthread+0xa5/0xb0
Nov  6 18:29:30 localhost kernel:  [<c012f1c0>] kthread+0x0/0xb0
Nov  6 18:29:30 localhost kernel:  [<c0101371>] kernel_thread_helper+0x5/0x14

Now. Is there a debugging option that I've got enabled that's making all of this get reported, or is this an ndiswrapper problem completely. Anybody else see anything similar? I haven't found anything on google....

Thanks everyone,
James

adz · 11-07-2005, 02:19 AM

I'm not sure about how to stop ndiswrapper from filling up your logs but did you try that kill command as root? That could be why it doesn't want to die.

jkassemi · 11-07-2005, 03:33 PM

Yep. Tried the kill command as root. The process just won't die. I have a big feeling this is definitely a kernel issue, or that kill command would definitely work...

-James

adz · 11-07-2005, 04:53 PM

Oh sorry I wasn't paying attention. In BSD, your command would work fine but in Linux, you have to use the command kill -s 9 <pid>. Note the "s" there.

jkassemi · 11-08-2005, 02:12 AM

Ah! That makes a little more sense... Maybe I was reading the man page from a BSD install... I don't know

I'll try again if this happens again. An upgrade to ndiswrapper 1.5 seems to have made a difference, but the problem was fairly irregular, and I don't know if I'll run into it once more.

Take it easy everybody,
James