Thread: [Ndiswrapper-general] Kernel: scheduling while atomic messages
Status: Beta
Brought to you by:
pgiri
From: Hans D. <han...@ta...> - 2006-02-02 08:43:15
|
Hello, I have used ndiswrapper now for a few days and it works fine for most of = the time! Thank you for such a marvellous piece of software, without it my wifi-card would have been useless under linux. However, after an unspecified amount of time (sometimes after 24 hours, sometimes after 4 hours) I get the following errors in my = /var/log/messages: Feb 1 19:54:43 videoserver kernel: scheduling while atomic: wrapper_wq/0x00000100/8057 Feb 1 19:54:43 videoserver kernel: [dump_stack+30/32] dump_stack+0x1e/0x20 Feb 1 19:54:43 videoserver = kernel: [<c0103c8e>] dump_stack+0x1e/0x20 Feb 1 19:54:43 videoserver kernel: [schedule+1060/1248] schedule+0x424/0x4e0 Feb 1 19:54:43 videoserver kernel: [<c033bf24>] schedule+0x424/0x4e0 = Feb 1 19:54:43 videoserver kernel: [pg0+412893093/1068971008] KeWaitForMultipleObjects+0x5d5/0x800 [ndiswrap per] Feb 1 19:54:43 videoserver kernel: [<d8e4efa5>] KeWaitForMultipleObjects+0x5d5/0x800 [ndiswrapper] Feb 1 19:54:43 videoserver kernel: [pg0+422911377/1068971008] = 0xd97dcd91 Feb 1 19:54:43 videoserver kernel: [<d97dcd91>] 0xd97dcd91 Feb 1 = 19:54:43 videoserver kernel: scheduling while atomic: wrapper_wq/0x00000100/8057 = Feb 1 19:54:43 videoserver kernel: [dump_stack+30/32] dump_stack+0x1e/0x20 = Feb 1 19:54:43 videoserver kernel: [<c0103c8e>] dump_stack+0x1e/0x20 Feb 1 19:54:43 videoserver kernel: [schedule+1060/1248] schedule+0x424/0x4e0 Feb 1 19:54:43 videoserver kernel: [<c033bf24>] schedule+0x424/0x4e0 = Feb 1 19:54:43 videoserver kernel: [schedule_timeout+90/176] schedule_timeout+0x5a/0xb0 Feb 1 19:54:44 videoserver kernel: = [<c033c68a>] schedule_timeout+0x5a/0xb0 Feb 1 19:54:44 videoserver kernel: [pg0+412892428/1068971008] KeWaitForMultipleObjects+0x33c/0x800 [ndiswrap per] Feb 1 19:54:44 videoserver kernel: [<d8e4ed0c>] KeWaitForMultipleObjects+0x33c/0x800 [ndiswrapper] Feb 1 19:54:44 videoserver kernel: [pg0+412893718/1068971008] KeWaitForSingleObject+0x46/0x50 [ndiswrapper] Feb 1 19:54:44 videoserver kernel: [<d8e4f216>] KeWaitForSingleObject+0x46/0x50 [ndiswrapper] Feb 1 19:54:44 videoserver kernel: [pg0+422902845/1068971008] = 0xd97dac3d Feb 1 19:54:44 videoserver kernel: [<d97dac3d>] 0xd97dac3d Feb 1 = 19:54:44 videoserver kernel: scheduling while atomic: wrapper_wq/0x00000100/8057 = Feb 1 19:54:44 videoserver kernel: [dump_stack+30/32] dump_stack+0x1e/0x20 = Feb 1 19:54:44 videoserver kernel: [<c0103c8e>] dump_stack+0x1e/0x20 Etc. = etc., fills up my entire log... I learned from the internet this could be a problem with pre-emptive = kernel, so I checked: -kernel version 2.6.11-6mdk (Mandrake Official 10.1) -preempt=3Dno, smp=3Dno -CONFIG_4KSTACKS disabled -latest windows = drivers for my USB-device, Senao NUB362 ext (Atheros AR5523 chipset), since I read that this problem probably is caused by the windows-driver "mis-behaving" = under linux. Other drivers for this chipset (e.g. netgear wg111t) do not = recognize my Senao. -ndiswrapper cvs version 28/01/2006 I checked my logs, none of these messages before using ndiswrapper, and = I have no idea how to get rid of them. I think I can reproduce the = problem, because it also arises when I switch routers on my network and then get = a lot of "martian packets": then also, after some time, the atomic = messages arise (right after the kernel reports a martian packet). Is there anything I can do to help resolving this problem? Would it be useful to recompile in debug-mode and send you the logs? Best regards, Hans Dingemans. |
From: Giridhar P. <gi...@lm...> - 2006-02-03 18:32:29
|
On Thu, 2 Feb 2006 09:42:48 +0100, "Hans Dingemans" <han...@ta...> said: Hans> However, after an unspecified amount of time (sometimes after 24 Hans> hours, sometimes after 4 hours) I get the following errors in my Hans> /var/log/messages: Hans> Feb 1 19:54:43 videoserver kernel: scheduling while atomic: Try 1.9 release. If it happens again, submit debug trace with 'DEBUG=2 IO_DEBUG=1 EVENT_DEBUG=1 USB_DEBUG=1' (normally a higher debug level is needed but in this case the issue appears to be in IO or USB layer). Note that this will generate _a lot_ of messages and you may need to increase log_buf_len in kernel for system logger to log all messages. -- Giri |
From: Hans D. <han...@ta...> - 2006-02-04 10:54:31
|
(I hope this will not start a new thread but will add to the previous postings on this subject...). >Try 1.9 release.=20 I was scanning the download-list frequently, so yesterday evening a saw = the new release and I installed it immediately. Alas, new problem, kernel = Oops: cat /var/log/messages: Feb 4 10:22:54 videoserver kernel: ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded Feb 4 10:22:54 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:804): --UNIMPLEMENTED-- Feb 4 10:22:54 videoserver last message repeated 2 times Feb 4 10:22:54 videoserver kernel: Unable to handle kernel paging = request at virtual address fd050f80 Feb 4 10:22:54 videoserver kernel: printing eip: Feb 4 10:22:54 videoserver kernel: fd050f80 Feb 4 10:22:54 videoserver kernel: *pde =3D 00000000 Feb 4 10:22:54 videoserver kernel: Oops: 0000 [#1] Feb 4 10:22:54 videoserver kernel: Modules linked in: sr_mod scsi_mod = udf lirc_serial lirc_dev budget-ci evdev tda10 04x budget-core dvb-ttpci l64781 saa7146_vv video-buf saa7146 = v4l1-compat v4l2-common videodev ves1820 stv0299 dvb-co re tda8083 stv0297 sp8870 firmware_class ves1x93 ttpci-eeprom i2c-core = wcfxo ztdummy zaptel crc-ccitt mISDN_dsp hfcsu sb mISDN_isac mISDN_capi kernelcapi l3udss1 mISDN_l2 mISDN_l1 mISDN_core ndiswrapper md5 ipv6 af_packet ipt_TOS iptab le_mangle ipt_LOG ipt_state ipt_limit ipt_REJECT iptable_filter ipt_MASQUERADE iptable_nat ip_conntrack ip_tables uhc i-hcd usbcore ne 8390 8139too mii raw ide-cd loop supermount via-agp = agpgart xfs exportfs ext3 jbd Feb 4 10:22:54 videoserver kernel: CPU: 0 Feb 4 10:22:54 videoserver kernel: EIP: = 0060:[pg0+1018978176/1068971008] Tainted: P VLI Feb 4 10:22:54 videoserver kernel: EIP: 0060:[<fd050f80>] = Tainted: P VLI Feb 4 10:22:54 videoserver kernel: EFLAGS: 00010286 (2.6.11-6mdk) Feb 4 10:22:54 videoserver kernel: EIP is at 0xfd050f80 Feb 4 10:22:54 videoserver kernel: eax: fffffc18 ebx: fd050f80 ecx: ffffffff edx: d93751f0 Feb 4 10:22:54 videoserver kernel: esi: ffffffff edi: d937501c ebp: d6eddd38 esp: d6eddd20 Feb 4 10:22:54 videoserver kernel: ds: 007b es: 007b ss: 0068 Feb 4 10:22:54 videoserver kernel: Process khubd (pid: 2460, threadinfo=3Dd6edc000 task=3Dd75a9040) Feb 4 10:22:54 videoserver kernel: Stack: ca84f860 ca84f860 00000246 d9375150 00000000 d9375140 d93750d0 d936da12 Feb 4 10:22:54 videoserver kernel: d93751c8 fd050f80 ffffffff 00001388 d93751f0 d937501c c8f865e0 d93750d0 Feb 4 10:22:54 videoserver kernel: c8f866a8 00000100 00000000 d6eddd6c d6eddd6c d936dacb d937501c 00000000 Feb 4 10:22:54 videoserver kernel: Call Trace: Feb 4 10:22:54 videoserver kernel: [show_stack+127/160] show_stack+0x7f/0xa0 Feb 4 10:22:54 videoserver kernel: [<c0103c4f>] show_stack+0x7f/0xa0 Feb 4 10:22:54 videoserver kernel: [show_registers+342/464] show_registers+0x156/0x1d0 Feb 4 10:22:54 videoserver kernel: [<c0103de6>] = show_registers+0x156/0x1d0 Feb 4 10:22:54 videoserver kernel: [die+200/336] die+0xc8/0x150 Feb 4 10:22:54 videoserver kernel: [<c0103fe8>] die+0xc8/0x150 Feb 4 10:22:54 videoserver kernel: [do_page_fault+1146/1818] do_page_fault+0x47a/0x71a Feb 4 10:22:54 videoserver kernel: [<c011637a>] = do_page_fault+0x47a/0x71a Feb 4 10:22:54 videoserver kernel: [error_code+43/48] = error_code+0x2b/0x30 Feb 4 10:22:54 videoserver kernel: [<c01038eb>] error_code+0x2b/0x30 Feb 4 10:22:54 videoserver kernel: [pg0+418261522/1068971008] = 0xd936da12 Feb 4 10:22:54 videoserver kernel: [<d936da12>] 0xd936da12 Feb 4 10:22:54 videoserver kernel: Code: Bad EIP value. But this message has drawn my attention: [root@videoserver root]# grep UNIMPLEMENTED /var/log/messages Jan 29 10:16:26 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Jan 29 10:26:28 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:834): --UNIMPLEMENTED-- Jan 29 10:40:04 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 09:57:31 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 11:40:53 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 12:45:04 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 12:57:35 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 13:08:51 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 1 16:09:19 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 2 08:41:40 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 2 11:10:18 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Feb 4 10:22:54 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:804): --UNIMPLEMENTED-- Feb 4 10:25:23 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:804): --UNIMPLEMENTED-- Feb 4 10:31:01 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:804): --UNIMPLEMENTED-- Feb 4 10:36:01 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:804): --UNIMPLEMENTED-- Feb 4 10:40:09 videoserver kernel: ndiswrapper (RtlQueryRegistryValues:837): --UNIMPLEMENTED-- Could this be the source of the "atomic messages" scheduling?=20 Best regards, Hans. |
From: Hans D. <han...@ta...> - 2006-02-10 12:40:14
|
On the "scheduling while atomic" problem with my Senao SUB362(ext) USB wifi device, I finally managed to manage the extremely large amount of debug messages, even on level 2. I attached only 8 seconds of my /var/log/syslog, and the ndiswrapper-buginfo.gz . If someone needs more info, I have 13 Gb of log-messages to dig in... Anything else I can do? >Try 1.9 release. If it happens again, submit debug trace with 'DEBUG=2 IO_DEBUG=1 EVENT_DEBUG=1 USB_DEBUG=1' (normally a |
From: Giridhar P. <gi...@lm...> - 2006-02-10 16:34:09
|
Hans Dingemans wrote: > Anything else I can do? >>Try 1.9 release. If it happens again, submit debug trace with 'DEBUG=3D= 2 > IO_DEBUG=3D1 EVENT_DEBUG=3D1 USB_DEBUG=3D1' (normally a After compiling with debug, load module with 'insmod ./ndiswrapper.ko debug=3D0'; when 'scheduling while atomic' errors start (you can see disk activity due to system log messages), enable debug with 'echo 6 > /proc/net/ndiswrapper/debug' and submit a few thousand lines of log. In t= his case, the log messages should point to the cause, even if debug was not o= n when it first happens, since this seems to happen in a loop. Giri |