Thread: [Ndiswrapper-general] centrino crash and slow
Status: Beta
Brought to you by:
pgiri
From: Navindra U. <nav...@cs...> - 2004-03-19 16:42:10
|
Hi, I upgraded my ndiswrapper from 0.4+CVS to 0.6+CVS on my Presario X1000 centrino laptop. Am I the only one who's noticed that the module is slower to load at boot? Also, if I boot with my radio off, and then turn on the radio with the button, the machine freezes. Otherwise it works fine. Thanks, Navin. |
From: Pontus F. <pon...@ta...> - 2004-03-19 16:49:47
|
On Fri, 2004-03-19 at 17:42, Navindra Umanee wrote: > Hi, > > I upgraded my ndiswrapper from 0.4+CVS to 0.6+CVS on my Presario > X1000 centrino laptop. > > Am I the only one who's noticed that the module is slower to load at > boot? Also, if I boot with my radio off, and then turn on the radio > with the button, the machine freezes. Otherwise it works fine. Yes. We have added a small delay because some cards needs otherwise setup will run before the card has initialized itself and cause the interface to not come up on boot. There is really no nice solution to this problem so if you don't like the delay you have to modify the source. Is the radio on/off button a problem that started with 0.6? Regarding the crash: Can you press the button which in console mode and see if you get an oops message then the machine freezes? Pontus |
From: Navindra U. <nav...@cs...> - 2004-03-19 17:47:28
|
Thanks for the quick replies! :-) Would it be easily possible to make the delay a module parameter? Unfortunately I don't think suspend/resume works for me yet partly due to the ATI/radeon driver. It's hard to generate an Oops. It's a hard-freeze and Alt-Sysrq barely works (it only allows reboots not syncs or unmounts). I got one Oops when the machine (surprisingly) didn't freeze at all but the Oops seems to be an after-effect of the bug and caused by another process (kdm_greet). I have tested 0.6 and it crashes as well although it seems to mostly happen when I'm using the modem. The good news is that on the occasions that it doesn't crash, I can boot up with my radio off, later turn it on and immediately get network connectivity! This wasn't possible before. I'm more than willing to test a patch although it'll be later today since I'll be away from my machine. Cheers, Navin. Here's the probably useless Oops: Unable to handle kernel paging request at virtual address e4159048 printing eip: e2046d60 *pde = 1d25d067 *pte = 00000000 Oops: 0002 [#1] CPU: 0 EIP: 0060:[__crc_inet_dgram_connect+1639998/11491207] Tainted: PF VLI EIP: 0060:[<e2046d60>] Tainted: PF VLI EFLAGS: 00010292 EIP is at 0xe2046d60 eax: fffc400d ebx: 00000000 ecx: dc685014 edx: dc685000 esi: e4159048 edi: 00000006 ebp: 00000821 esp: df3fbd90 ds: 007b es: 007b ss: 0068 Process kdm_greet (pid: 2078, threadinfo=df3fa000 task=df3fd940) Stack: e4067000 dc685000 dc685014 00000004 00000827 e2064364 e2046e40 e2064364 00000004 dc685000 e2063f40 00000000 e20640c0 00000000 e2040d5d e2064364 00000000 00000000 c0119c64 df3fbde8 df3fbe84 c010bf2a dc6e5a98 e2063f88 Call Trace: [__crc_inet_dgram_connect+1640222/11491207] 0xe2046e40 [<e2046e40>] 0xe2046e40 [__crc_inet_dgram_connect+1615419/11491207] 0xe2040d5d [<e2040d5d>] 0xe2040d5d [smp_apic_timer_interrupt+52/240] smp_apic_timer_interrupt+0x34/0xf0 [<c0119c64>] smp_apic_timer_interrupt+0x34/0xf0 [apic_timer_interrupt+26/32] apic_timer_interrupt+0x1a/0x20 [<c010bf2a>] apic_timer_interrupt+0x1a/0x20 [__crc_inet_dgram_connect+1669306/11491207] 0xe204dfdc [<e204dfdc>] 0xe204dfdc [destroy_inode+59/80] destroy_inode+0x3b/0x50 [<c01685ab>] destroy_inode+0x3b/0x50 [__crc_inet_dgram_connect+1606559/11491207] 0xe203eac1 [<e203eac1>] 0xe203eac1 [dput+33/480] dput+0x21/0x1e0 [<c0166ce1>] dput+0x21/0x1e0 [__fput+200/256] __fput+0xc8/0x100 [<c0153eb8>] __fput+0xc8/0x100 [filp_close+68/112] filp_close+0x44/0x70 [<c0152944>] filp_close+0x44/0x70 [put_files_struct+98/192] put_files_struct+0x62/0xc0 [<c0122f82>] put_files_struct+0x62/0xc0 [do_exit+290/736] do_exit+0x122/0x2e0 [<c0123af2>] do_exit+0x122/0x2e0 [do_group_exit+43/112] do_group_exit+0x2b/0x70 [<c0123d4b>] do_group_exit+0x2b/0x70 [get_signal_to_deliver+513/752] get_signal_to_deliver+0x201/0x2f0 [<c012bd21>] get_signal_to_deliver+0x201/0x2f0 [do_signal+77/240] do_signal+0x4d/0xf0 [<c010ad7d>] do_signal+0x4d/0xf0 [__pollwait+0/176] __pollwait+0x0/0xb0 [<c0163190>] __pollwait+0x0/0xb0 [sys_select+981/1232] sys_select+0x3d5/0x4d0 [<c0163a25>] sys_select+0x3d5/0x4d0 [do_notify_resume+59/64] do_notify_resume+0x3b/0x40 [<c010ae5b>] do_notify_resume+0x3b/0x40 [work_notifysig+19/21] work_notifysig+0x13/0x15 [<c010b03e>] work_notifysig+0x13/0x15 Code: b6 00 00 00 00 8d bf 00 00 00 00 8b 54 24 04 8b 42 10 39 e8 77 f5 29 eb 8d 43 fe 3d ff 3f 00 00 76 21 89 f6 8d bc 27 00 00 00 00 <c7> 06 00 10 fd ff 2d ff 3f 00 00 81 c6 fc ff 00 00 3d ff 3f 00 |
From: Giridhar P. <gi...@lm...> - 2004-03-19 18:09:58
|
On Fri, 19 Mar 2004 12:47:24 -0500, Navindra Umanee <nav...@cs...> said: Navindra> Would it be easily possible to make the delay a module Navindra> parameter? Unfortunately I don't think suspend/resume Navindra> works for me yet partly due to the ATI/radeon driver. Slightly off-topic, but if you want to get your ATI/radeon to work with suspend/resume, see my posts to acpi4linux list. I sent some patches there. It is possible to add delay as module parameter, but I think not that important. For now we have too much planned for the next release. Navindra> Here's the probably useless Oops: Could you compile ndiswrapper with DEBUG=1 and see if that gives any clue. I also notice you use APIC. As far as I understand, apic is known to cause problems with pci. So try with noapic boot flag or even better, leave it out, at least to test to see if that is the problem. -- Giri |
From: Navindra U. <nav...@cs...> - 2004-03-19 19:08:44
|
Giridhar Pemmasani <gi...@lm...> wrote: > Slightly off-topic, but if you want to get your ATI/radeon to work > with suspend/resume, see my posts to acpi4linux list. I sent some > patches there. Can't wait to check it out! > It is possible to add delay as module parameter, but I think not that > important. For now we have too much planned for the next release. I'll see if I can make a patch this weekend... > Could you compile ndiswrapper with DEBUG=1 and see if that gives any > clue. I also notice you use APIC. As far as I understand, apic is > known to cause problems with pci. So try with noapic boot flag or even > better, leave it out, at least to test to see if that is the problem. It's news to me that I'm using APIC, in fact I'm pretty sure that I am not. AFAIK ndiswrapper 0.4+CVS does not even work for me (crashes) with APIC enabled so I had no choice but to specify noapic in lilo.conf. I haven't changed anything in my kernel/config in ages. I see what you're referring to in the Oops though and I'm at just a loss as you are. I'll investigate this when I'm home. Cheers, Navin. |
From: Navindra U. <nav...@cs...> - 2004-03-24 01:54:13
|
Hi Giri, Giridhar Pemmasani <gi...@lm...> wrote: > Could you compile ndiswrapper with DEBUG=1 and see if that gives any Still nothing but hard crashes. > clue. I also notice you use APIC. As far as I understand, apic is > known to cause problems with pci. So try with noapic boot flag or even > better, leave it out, at least to test to see if that is the problem. Whether I leave out apic or specify noapic, it seems the kernel forces it back on: Kernel command line: auto BOOT_IMAGE=linux ro root=305 devfs=mount resume=/dev/hda2 splash=verbose noapic bootsplash: verbose mode. Local APIC disabled by BIOS -- reenabling. Found and enabled local APIC! Initializing CPU#0 [...] Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 1395.0250 MHz. ..... host bus clock speed is 99.0660 MHz. Any ideas? Thanks, Navin. |
From: Martin W. <mar...@nt...> - 2004-03-24 08:56:27
|
Try the boot option "nolapic". This stands for no local APIC. Just don't ask me what the difference is between "noapic" and "nolapic" - I'm just repeating suggestions I've read in various user forums :-) HTH Martin Navindra Umanee wrote: > Hi Giri, > > Giridhar Pemmasani <gi...@lm...> wrote: > >>Could you compile ndiswrapper with DEBUG=1 and see if that gives any > > > Still nothing but hard crashes. > > >>clue. I also notice you use APIC. As far as I understand, apic is >>known to cause problems with pci. So try with noapic boot flag or even >>better, leave it out, at least to test to see if that is the problem. > > > Whether I leave out apic or specify noapic, it seems the kernel forces > it back on: > > Kernel command line: auto BOOT_IMAGE=linux ro root=305 devfs=mount resume=/dev/hda2 splash=verbose noapic > bootsplash: verbose mode. > Local APIC disabled by BIOS -- reenabling. > Found and enabled local APIC! > Initializing CPU#0 > [...] > Using local APIC timer interrupts. > calibrating APIC timer ... > ..... CPU clock speed is 1395.0250 MHz. > ..... host bus clock speed is 99.0660 MHz. > > Any ideas? > > Thanks, > Navin. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > |
From: Navindra U. <nav...@cs...> - 2004-03-24 15:57:45
|
Hi Martin, Martin Whitaker <mar...@nt...> wrote: > Try the boot option "nolapic". This stands for no local APIC. Just don't ask me > what the difference is between "noapic" and "nolapic" - I'm just repeating > suggestions I've read in various user forums :-) Noticed that option in the documentation, haven't tried it yet. Martin, you have the same machine as I, have you noticed the same crashes with latest CVS when you turn the radio on? I guess you might not be using the modem, sometimes it only happens for me when the modem is active (especially with 0.6). Thanks, Navin. |
From: Martin W. <mar...@nt...> - 2004-03-24 20:31:36
|
Hi Navindra, Up until now I have stuck with 0.4, as it was working fine (providing I turned the wireless on before the device driver initialised). However, I have just upgraded to Mandrake 10.0, so will try the latest ndiswrapper once I've got the machine stable again. I'll let you know how I get on. I've never used the modem, though. Martin Navindra Umanee wrote: > Martin, you have the same machine as I, have you noticed the same > crashes with latest CVS when you turn the radio on? I guess you might > not be using the modem, sometimes it only happens for me when the > modem is active (especially with 0.6). > > Thanks, > Navin. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > |
From: Giridhar P. <gi...@lm...> - 2004-03-19 16:56:43
|
On Fri, 19 Mar 2004 11:42:00 -0500, Navindra Umanee <nav...@cs...> said: Navindra> Am I the only one who's noticed that the module is slower Navindra> to load at boot? Also, if I boot with my radio off, and There is now about 3 second delay when the module is loaded. This is because some drivers/cards need some time for the windows driver to be loaded. Since suspend/resume is working, hopefully one has to load the module only during booting, unless you are a developer and have to load/unload module countless times (not to mention rebooting due to crashing). Navindra> then turn on the radio with the button, the machine Navindra> freezes. Otherwise it works fine. Could you try with 0.6 release and see if you see the same problem? And if you are willing to test a simple patch, let me know. Pontus, I am wondering if resetting the card after initializing it would help in this case. -- Giri |