Kernel 2.6.36 (sometimes) goes oops on ARCH, Is there a panic log somewhere?

masmddr · 01-09-2011, 06:42 AM

Hello.
I am using arch and recently reinstalled it and the first thing I did (after setting up the modem) was to update everything using pacman -Syu.
This updated to Kernel version 2.6.36-ARCH .

Problem is I some times get a Kernel panic, two actually.
I get a Kernel panic at boot and after a hard reboot I get a second panic also at boot.
It's always like this Panic #1 > reboot > Panic #2 > reboot > works fine.

I searched /var/log/ for anything about it but found nothing, probably because it happens before the file system is mounted, so I have pictures instead (sorry I'm a horrible photographer).

Panic #1
http://img836.imageshack.us/img836/4...0109134054.jpg

Panic #2
http://img258.imageshack.us/img258/2...0109134214.jpg

I should also note that I am somewhat of a newbie and have no idea what they mean.

From /boot/grub/menu.lst

Code:

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/42f77199-728b-454b-a6d7-96d542f729d8 ro vga=773
initrd /kernel26.img

root used to be root=/dev/sda2 but I changed it cause I thought the nodes might change but I still get the same panics.

Where do I go from here ?

andrewthomas · 01-09-2011, 07:14 AM

I would first make sure that your /etc/fstab refers to the uuid

Code:

UUID=42f77199-728b-454b-a6d7-96d542f729d8 / ext4    defaults,noatime        1 1

then, I would regenerate the initramfs

Code:

# mkinitcpio -k 2.6.36-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img

masmddr · 01-09-2011, 07:25 AM

Thank you.

I changed fstab to be :

Quote:

# /boot
UUID=a0b3faee-75ac-4180-a9c0-dfa82ebe70bc /boot ext3 defaults 0 1
# /
UUID=42f77199-728b-454b-a6d7-96d542f729d8 / ext3 defaults 0 1
# /home
UUID=36f6a699-4e7d-4805-91d7-e77d1798c531 /home ext3 defaults 0 1

and ran " pacman -S kernel26 " again and it regenerated initramfs.
As the panics happen randomly at boot I can't know if it will work until I reboot several times.

Edit:
That didn't work..
But I then did " pacman -S grub udev " to reinstall both and so far after 5 reboots I got no panics.

Edit 2:
I take that back.
It's panicking again at random.

H_TeXMeX_H · 01-09-2011, 10:18 AM

Use memtest just in case.

masmddr · 01-09-2011, 12:35 PM

Ran memtest, found no errors, neither has fsck.

aaazen · 01-10-2011, 12:37 AM

Quote:

Originally Posted by masmddr

Hello.
I am using arch and recently reinstalled it and the first thing I did (after setting up the modem) was to update everything using pacman -Syu.
This updated to Kernel version 2.6.36-ARCH .

Problem is I some times get a Kernel panic, two actually.
I get a Kernel panic at boot and after a hard reboot I get a second panic also at boot.

...
Panic #1
http://img836.imageshack.us/img836/4...0109134054.jpg

Panic #2
http://img258.imageshack.us/img258/2...0109134214.jpg

...

Where do I go from here ?

This is also happening to Slackware users who upgrade to the 32 bit current version.

http://www.linuxquestions.org/questi...-boxen-852843/

After trying out multiple new kernels with no effect I now think that the problem relates to udev-165.

When I downgraded udev to udev-164 then the kernel panics stopped.