Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
Am 2008-05-01 16:32:52, schrieb Michael Elsdörfer: > Does anybody know what the issue might be? END OF REPLIED MESSAGE There are some cases where you have to enable PAE! Thanks, Greetings and nice Day Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
Michael Elsdörfer wrote: Have you used Linux on this machine before now? If not, the problem may be a hardware issue. You may have a broken BIOS which doesn't allow the kernel to do something it thinks it sould be able to do. Try booting with the kernel parameters acpi=off or noapic. Thanks for responding Mark. Yes, as I mentioned, I had a custom debian sarge kernel running on it previously for years. I'll give noacpi a try, but since this is a live machine and I'll have to schedule a downtime, I'd welcome any other suggestions anyone might have. Michael D'oh! Missed the mention of Sarge. I had some issues with certain motherboards when everyone was switching from 2.4 kernels to 2.6 kernels. Two ASUS consumer boards had broken APIC code. And recently, there appeared a virtual device driver issue in XP on another ASUS board after installing a new antivirus program. Something in the ACPI caused a conflict. The problem was a buggy BIOS. Disabling APM in the BIOS setup was the workaround. (Of course, a better solution would be to use a different antivirus. Even better: Putting Debian on the machine, and having done with Windows. Sigh. If wishes were horses...) -- Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
> Have you used Linux on this machine before now? If not, the problem may be > a hardware issue. You may have a broken BIOS which doesn't allow the kernel > to do something it thinks it sould be able to do. Try booting with the > kernel parameters acpi=off or noapic. Thanks for responding Mark. Yes, as I mentioned, I had a custom debian sarge kernel running on it previously for years. I'll give noacpi a try, but since this is a live machine and I'll have to schedule a downtime, I'd welcome any other suggestions anyone might have. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
Michael Elsdörfer wrote: This is an etch server machine with 3GB of RAM, and I seem unable to boot into any kernel that has HIGHMEM enabled, i.e.: zoidberg:/# dmesg | head Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. Specifically, the only kernel image that seems to work is linux-image-2.6.18-6-486 (or the OpenVZ version fzakernel-2.6.18-486) Everything else seems to fail with: Setting up standard PCI resources ACPI: Interpreter enabled ACPI: PCI Root Bridge [PCI0] (:00) CPU 0: Machine Check Exception: 0007 Bank 3: b400083b at 00fdfc000cfc Kernel panic - not syncing: Unable to continue Specifically, I tried at least the following images from the Debian and OpenVZ repositories: config-2.6.18-openvz-k7 linux-image-2.6.18-6-686 fzakernel-2.6.18-686 fzakernel-2.6.18-686-bigmem Now, Machine Check Exception seems to point towards a hardware error, but note only does the 486 kernel appear to work flawlessly, the server was perfectly happy running a self-compiled sarge kernel (with HIGHMEM) just a couple of days ago. Here's the processor info: zoidberg:/boot# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 244 stepping: 10 cpu MHz : 1794.546 cache size : 1024 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow ts fid vid ttp bogomips: 3591.45 Does anybody know what the issue might be? Michael Have you used Linux on this machine before now? If not, the problem may be a hardware issue. You may have a broken BIOS which doesn't allow the kernel to do something it thinks it sould be able to do. Try booting with the kernel parameters acpi=off or noapic. -- Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
This is an etch server machine with 3GB of RAM, and I seem unable to boot into any kernel that has HIGHMEM enabled, i.e.: zoidberg:/# dmesg | head Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. Specifically, the only kernel image that seems to work is linux-image-2.6.18-6-486 (or the OpenVZ version fzakernel-2.6.18-486) Everything else seems to fail with: Setting up standard PCI resources ACPI: Interpreter enabled ACPI: PCI Root Bridge [PCI0] (:00) CPU 0: Machine Check Exception: 0007 Bank 3: b400083b at 00fdfc000cfc Kernel panic - not syncing: Unable to continue Specifically, I tried at least the following images from the Debian and OpenVZ repositories: config-2.6.18-openvz-k7 linux-image-2.6.18-6-686 fzakernel-2.6.18-686 fzakernel-2.6.18-686-bigmem Now, Machine Check Exception seems to point towards a hardware error, but note only does the 486 kernel appear to work flawlessly, the server was perfectly happy running a self-compiled sarge kernel (with HIGHMEM) just a couple of days ago. Here's the processor info: zoidberg:/boot# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 244 stepping: 10 cpu MHz : 1794.546 cache size : 1024 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow ts fid vid ttp bogomips: 3591.45 Does anybody know what the issue might be? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
