Hi Willy, On Mon, 2005-03-28 at 21:39 +0200, Willy Tarreau wrote: > Sorry, at first I only noticed ACPI in your mail, but after reading it > again, I also noticed APIC. So now, you can only try not to initialize > some peripherals (IDE, network, display, etc...) by removing their drivers > from the kernel. You may end up with a kernel panic, but that does not > matter is you boot it with "panic=5" so that it automatically reboots > 5 seconds after the panic. You should then finally identify the subsystem > which is responsible for your problems. Perhaps you'll even need to remove > PCI support :-(
Well, actually, the system runs (at least) unless I try to load "ndiswrapper" which leads to a kernel panic. I tried to bring the issue to the ndiswrapper ML but I doubt that ndiswrapper is faulty. I can reliably predict the crash. If the clock (and all other time based events) are too fast, then modprobing ndiswrapper will lead to a system crash, just like mounting a CDROM will fail. I think the clock speed and other effects are just signs, not the cause of the problem. What I'd like to determine is what would need to be done to avoid the root cause, or maybe if there is anything that can be done in Linux to avoid that? I just tried "acpi_fake_ecdt" but that leads to a immediate kernel panic. Ps: Given the crash (Machine check exception), the sleep option seems to have no effect. Thanks, Olivier. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/