Thread: [Ndiswrapper-general] ndiswrapper/broadcom/amd64/nforce = kernel panic?
Status: Beta
Brought to you by:
pgiri
From: Olivier F. <fo...@xf...> - 2005-03-14 21:57:45
|
Hi, I've been fighting with this for a while (a couple of months), and just found the correct log. I'm using ndiswrapper-1.1 with a Broadcom Wireless built-in an 64 bit AMD64 laptop. Most of the time, when I "modprobe ndiswrapper", the whole system freeze with a kernel panic. The log gives: ---------------------------------------------------------------------------- modprobe ndiswrapper ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11 CPU 0: Machine Check Exception: 4 bank 4: b200000000070f0f TSC ba428433ac Kernel panic - not syncing: Machine check ---------------------------------------------------------------------------- At first, I thought it might be an issue with apic and nforce so I disabled apic (with "noapic" and also "acpi=noirq" at boot) but that makes no difference. I thought of a hardware issue, but everything seems fine under Windows XP. No freeze, and wireless works fine. This is on a Compaq R3480 AMD64 3400+ laptop, using a vanilla 2.4.11.3 kernel (but that was the same with older Fedora kernels) What is really odd is that it sometimes (rarely) works, and when that happen I'm able to used wifi w/out any problem. Maybe it's a IRQ conflict, but how can I fix this? I'm using the netbc564 driver (64bit version). 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Subsystem: Hewlett-Packard Company: Unknown device 12fa Flags: bus master, fast devsel, latency 64, IRQ 11 Memory at e0104000 (32-bit, non-prefetchable) [size=8K] ndiswrapper -l gives : Installed ndis drivers: netbc564 driver present, hardware present cat /proc/interrupts CPU0 0: 1018089 XT-PIC timer 1: 349 XT-PIC i8042 2: 0 XT-PIC cascade 7: 2 XT-PIC parport0 8: 0 XT-PIC rtc 9: 23 XT-PIC acpi 10: 1997 XT-PIC eth0, NVidia nForce3 Modem, ehci_hcd, ohci_hcd, yenta 11: 16449 XT-PIC NVidia nForce3, ohci_hcd, yenta, ohci1394, nvidia 12: 127 XT-PIC i8042 14: 18016 XT-PIC ide0 15: 7364 XT-PIC ide1 NMI: 154 LOC: 1017659 ERR: 0 MIS: 0 Please mail me directly as I'm not subscribed to any of the ndiswrapper lists... Thanks in advance, Cheers, Olivier. |
From: Jonathan B. <be...@gm...> - 2005-03-14 22:36:15
|
On Mon, 14 Mar 2005 22:57:16 +0100, Olivier Fourdan <fo...@xf...> wrote: > Hi, > > I've been fighting with this for a while (a couple of months), and just > found the correct log. > > I'm using ndiswrapper-1.1 with a Broadcom Wireless built-in an 64 bit > AMD64 laptop. Most of the time, when I "modprobe ndiswrapper", the whole > system freeze with a kernel panic. ndiswrapper 1.1 works fine for me with the latest Fedora kernel (2.6.10-1.770_FC3). I also have an R3000Z, only with the 64-bit 3200+ processor, so probably close to the same hardware. > The log gives: > > ---------------------------------------------------------------------------- > modprobe ndiswrapper > ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11 Is this with APIC disabled? Mine normally gets IRQ 16 or 17 or so, if I'm remembering right. 11 is already used quite a bit. > CPU 0: Machine Check Exception: 4 bank 4: b200000000070f0f > TSC ba428433ac > Kernel panic - not syncing: Machine check > ---------------------------------------------------------------------------- I've never seen anything like that before, the "Machine check" stuff, I mean. Is this new to the 2.6.11 kernel? > At first, I thought it might be an issue with apic and nforce so I > disabled apic (with "noapic" and also "acpi=noirq" at boot) but that > makes no difference. I thought of a hardware issue, but everything seems > fine under Windows XP. No freeze, and wireless works fine. I would not disable APIC. APIC should help spread the IRQs and possibly avoid conflicts, I would think. > This is on a Compaq R3480 AMD64 3400+ laptop, using a vanilla 2.4.11.3 > kernel (but that was the same with older Fedora kernels) As I said, works for me with the newest Fedora kernels. Can you try one in the 760-770 range? This seems like maybe it's a problem with the 2.6.11 kernel, especially with Michael's comments. > What is really odd is that it sometimes (rarely) works, and when that > happen I'm able to used wifi w/out any problem. Maybe it's a IRQ > conflict, but how can I fix this? That is quite strange. I don't know. What do things look like when it does work? > I'm using the netbc564 driver (64bit version). > > 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g > Wireless LAN Controller (rev 03) > Subsystem: Hewlett-Packard Company: Unknown device 12fa > Flags: bus master, fast devsel, latency 64, IRQ 11 > Memory at e0104000 (32-bit, non-prefetchable) [size=8K] How did you get these last three lines? (I assume "lspci" with some number of "-v"s) That last line looks suspicious with the "32-bit" stuff. I'm not in Linux right now to see what mine gives. I'll check when I get a chance. > ndiswrapper -l gives : > > Installed ndis drivers: > netbc564 driver present, hardware present This looks fine. > cat /proc/interrupts > CPU0 > 0: 1018089 XT-PIC timer > 1: 349 XT-PIC i8042 > 2: 0 XT-PIC cascade > 7: 2 XT-PIC parport0 > 8: 0 XT-PIC rtc > 9: 23 XT-PIC acpi > 10: 1997 XT-PIC eth0, NVidia nForce3 Modem, ehci_hcd, > ohci_hcd, yenta > 11: 16449 XT-PIC NVidia nForce3, ohci_hcd, yenta, > ohci1394, nvidia > 12: 127 XT-PIC i8042 > 14: 18016 XT-PIC ide0 > 15: 7364 XT-PIC ide1 > NMI: 154 > LOC: 1017659 > ERR: 0 > MIS: 0 As I said, I think you should use APIC. It should work fine. Without it, see how much stuff is already using IRQ 11. > Please mail me directly as I'm not subscribed to any of the ndiswrapper > lists... > > Thanks in advance, > > Cheers, > Olivier. Jonathan |
From: Olivier F. <fo...@xf...> - 2005-03-14 22:52:14
|
Hi Jonathan On Mon, 2005-03-14 at 16:36 -0600, Jonathan Berry wrote: > I've never seen anything like that before, the "Machine check" stuff, > I mean. Is this new to the 2.6.11 kernel? nope, it's for x86_64 kernels, can be decoded with mcelog - Though it doesn't help much here. http://www.x86-64.org/lists/discuss/msg06300.html ftp://ftp.x86-64.org/pub/linux/tools/mcelog/mcelog-0.3.tar.gz > As I said, works for me with the newest Fedora kernels. Can you try > one in the 760-770 range? This seems like maybe it's a problem with > the 2.6.11 kernel, especially with Michael's comments. Oh, I did, I had the same with all FC3 kernels up to now (including the latest one available) - That's why I thought it was a Fedora kernel issue at first. > That is quite strange. I don't know. What do things look like when > it does work? Works just fine :) But it's rare, and when it doesn't work, the whole system hard freeze which is fairly, humm, annoying :) > How did you get these last three lines? (I assume "lspci" with some > number of "-v"s) That last line looks suspicious with the "32-bit" > stuff. I'm not in Linux right now to see what mine gives. I'll check > when I get a chance. cat /proc/pci > As I said, I think you should use APIC. It should work fine. Without > it, see how much stuff is already using IRQ 11. actually, it makes no difference. Thanks, Olivier. |
From: <kar...@te...> - 2005-03-14 23:43:47
|
Olivier Fourdan <fo...@xf...> writes: > I've been fighting with this for a while (a couple of months), and just > found the correct log. > > I'm using ndiswrapper-1.1 with a Broadcom Wireless built-in an 64 bit > AMD64 laptop. Most of the time, when I "modprobe ndiswrapper", the whole > system freeze with a kernel panic. > > The log gives: > > ---------------------------------------------------------------------------- > modprobe ndiswrapper > ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11 > > CPU 0: Machine Check Exception: 4 bank 4: b200000000070f0f > TSC ba428433ac > Kernel panic - not syncing: Machine check > ---------------------------------------------------------------------------- Build ndiswrapper with DEBUG and try to capture the log. (if you have another linux machine, you can use netconsole to capture the log). Is this the only output you get? Or do you also get an OOPS before this message? Anyway, I would suggest you try running memtest86 overnight to make sure your memory isn't at fault.. as that error looks kind of fishy! http://www.memtest86.org > Please mail me directly as I'm not subscribed to any of the ndiswrapper > lists... http://dir.gmane.org/gmane.linux.drivers.ndiswrapper.general |
From: Olivier F. <fo...@xf...> - 2005-03-15 19:57:22
|
Hi Karl, On Tue, 2005-03-15 at 00:42 +0100, kar...@te... wrote: > Build ndiswrapper with DEBUG and try to capture the log. > (if you have another linux machine, you can use netconsole to capture the > log). I've rebuilt ndiswrapper with "make DEBUG=3" as per the wiki, and loaded the driver, but got nothing more that previously. I did also try to pass a debug option at load (as per modinfo params) but again, I got nothing more than the MCE mentionned before. > Is this the only output you get? Or do you also get an OOPS before this > message? Nope, nothing before.... > Anyway, I would suggest you try running memtest86 overnight to make sure > your memory isn't at fault.. as that error looks kind of fishy! I did that already, but nothing wrong with the RAM. Could it be the 64bit driver I use that is buggy maybe? Or maybe slightly incompatible with the Broadcom chip? Thanks, Olivier. |
From: Karl V. <kar...@te...> - 2005-03-15 21:56:15
|
On Tue, 2005-03-15 at 20:57 +0100, Olivier Fourdan wrote: > > Build ndiswrapper with DEBUG and try to capture the log. > > (if you have another linux machine, you can use netconsole to capture the > > log). > > I've rebuilt ndiswrapper with "make DEBUG=3" as per the wiki, and loaded > the driver, but got nothing more that previously. The logging will go to klogd (/var/log/messages), but it might be that due to the crash, it doesn't get logged. On your console, try: dmesg -n 8 which should cause kernel logging to be output to the console display. > Could it be the 64bit driver I use that is buggy maybe? Or maybe > slightly incompatible with the Broadcom chip? Well it seems to work on my machine (Acer Aspire 1510, Athlon64) and a few other people seem to be able to use it.. but that doesn't mean the broadcom driver is bug free.. although there isn't much we can do about that. |
From: Giridhar P. <gi...@lm...> - 2005-03-16 21:51:55
|
The logs don't show any oops trace. I assume that you have ruled out problem is elsewhere (when ndiswrapper is not being used you don't get freezes). If it freezes without any oops trace, it will be difficult to identify the problem. Have you tried to leave the machine with console, so if there is any oops message, you can see it on the screen? You could also try netconsole and set it up to send the logs to remote machine (see wiki Bugs). See if you can use kernel config from someone else that is known to work (Karl Vogel posted his configuration here sometime back). Of course, all this is to find out what causes problem; we need to fix the issue once we know what it is. Please try latest snapshot too; some things have been fixed in CVS since 1.1, but not sure if any affects issues you are facing. -- Giri |
From: Olivier F. <fo...@xf...> - 2005-03-26 09:20:59
|
Hi everybody, Some update on that issue. Here is what I did: 1) I switched to SuSE 9.2 64bit instead of FC3 64bit and reinstalled ndiswrapper 1.1, that worked 2) I upgraded to latest ndiswrapper CVS and the system freezed 3) I downgraded to ndiswrapper 1.1 and it seems to work (so far) - As per all random crashes, I can't guarantee this is a really scientific proof :) It's just observations. HTH Olivier. On Wed, 2005-03-16 at 16:51 -0500, Giridhar Pemmasani wrote: > The logs don't show any oops trace. I assume that you have ruled out problem > is elsewhere (when ndiswrapper is not being used you don't get freezes). If it > freezes without any oops trace, it will be difficult to identify the > problem. Have you tried to leave the machine with console, so if there is any > oops message, you can see it on the screen? You could also try netconsole and > set it up to send the logs to remote machine (see wiki Bugs). See if you can > use kernel config from someone else that is known to work (Karl Vogel posted > his configuration here sometime back). Of course, all this is to find out what > causes problem; we need to fix the issue once we know what it is. > > Please try latest snapshot too; some things have been fixed in CVS since 1.1, > but not sure if any affects issues you are facing. > |
From: Olivier F. <fo...@xf...> - 2005-03-16 20:04:27
|
Hi Karl, Yeap, dunno what I did wrong, but I got debug now. It doesn't crash when debug is enabled (AFAICT). I've placed the relevant log here: http://www.xfce.org/~olivier/ndis/ HTH Olivier. On Tue, 2005-03-15 at 22:56 +0100, Karl Vogel wrote: > On Tue, 2005-03-15 at 20:57 +0100, Olivier Fourdan wrote: > > > > Build ndiswrapper with DEBUG and try to capture the log. > > > (if you have another linux machine, you can use netconsole to capture the > > > log). > > > > I've rebuilt ndiswrapper with "make DEBUG=3" as per the wiki, and loaded > > the driver, but got nothing more that previously. > > The logging will go to klogd (/var/log/messages), but it might be that > due to the crash, it doesn't get logged. > On your console, try: > dmesg -n 8 > > which should cause kernel logging to be output to the console display. > > > Could it be the 64bit driver I use that is buggy maybe? Or maybe > > slightly incompatible with the Broadcom chip? > > Well it seems to work on my machine (Acer Aspire 1510, Athlon64) and a > few other people seem to be able to use it.. but that doesn't mean the > broadcom driver is bug free.. although there isn't much we can do about > that. > > > > > |