Arch Linux

ith140

Member

From: Ottawa, ON

Registered: 2005-07-13

Posts: 32

Kernel Issue x86_64 2.26.28-2.1 [Solved]

I'm having big time trouble with the newest kernel.  For some reason, I randomly get kernel panics on boot.  To solve my problem, I've tried to use a system rescue cd, but that also gives me a kernel panic (it used to work fine) with a message about fixing some recursive error and needing a reboot.  After rebooting it reports the same error message (recursive indeed).  No matter what I try, the only way I have been able to get into my system is to use a Chakra CD. 

I'd like to post what happens when my computer crashes, but I do not get logging until after it is done with the boot image.  Is there any way I can enable logging to catch the error before my machine tells me its running Arch linux with the copyrights etc.

If there isn't a way to log this I seem to get a lot of ACPI error dumps out of the kernel, and I might be able to digitally photograph the image of the dump.

I'm running kdemod, nvidia 8600GTS with nvidia 180 drivers, Asus P5B mobo, 4GB XMMS2 Corsair RAM, 1 SATA drive, 1 PATA drive, 1 WD MyBook eSATA drive (if I can figure out how to get it working, I was trying this before my machine crashed:().

Last edited by ith140 (2009-02-02 03:50:44)

DonVla

Member

From: Bonn, Germany

Registered: 2007-06-07

Posts: 997

Re: Kernel Issue x86_64 2.26.28-2.1 [Solved]

try "hpet=disable" as kernel boot parameter.
if you´re using a usb mouse/keyboard, then switch to standard ps2.
hope this helps, worked for me.
dirty workarounds are awful.

vlad

ith140

Member

From: Ottawa, ON

Registered: 2005-07-13

Posts: 32

Re: Kernel Issue x86_64 2.26.28-2.1 [Solved]

Thanks for the tip.  That allowed me to boot into my system again.  Strange that this became a problem after many years.  I'll keep testing it a little bit, but you've been super helpful!

DonVla

Member

From: Bonn, Germany

Registered: 2007-06-07

Posts: 997

Re: Kernel Issue x86_64 2.26.28-2.1 [Solved]

yeah, it took me a week to find out what happened and what to do.
it seems to be a regression. this was also a bug in 2.6.24 or so.