[arch-general] Kernel panic with kernel26 2.6.32.2-2 from [core]

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I think I am in much better shape now.  I managed to upgrade all
kernel packages and speakup but had to modify my grub.cfg so all boots
now with latest packages.  What I have been using is kernel parameters
to give me the 128x160 console but then my system stopped booting with
the latest kernel upgrade.  I will paste in my grub.cfg entries below
so you can see what I had to comment out.  Basically i stopped the
insmod of the vbe module and removed the vga parms in the kernel
entry.

* Loading of modules
#insmod vbe

# Timeout for menu
set timeout=15

# Set default boot entry as Entry 0
set default=0
# (0) Arch Linux
menuentry "Arch Linux" {
set root=(hd1,1)
#linux /boot/vmlinuz26 root=/dev/sdb1 ro video=vesafb:mode=1024x768-32 vga=790
linux /boot/vmlinuz26 root=/dev/sdb1 ro 
initrd /boot/kernel26.img
}

You can see, I just commented out the entries that gave me the nice
screen but at least I can boot now.  Any ideas? Did something change
with the 2.6.32 kernel in the VESA frame buffer department?

On Thu, Dec 31, 2009 at 06:32:57PM +0100, Heiko Baums wrote:
> Am Thu, 31 Dec 2009 15:49:51 +0100
> schrieb Heiko Baums <lists at baums-on-web.de>:
> 
> > Forgot to say that the kernel panic happened with
> > kernel26-fallback.img, too. And the fallback image hasn't
> > autodetection.
> > 
> > I'm currently downgrading to [core] each package one by one and see if
> > and when the kernel panic reappears.
> > 
> > Another possibility is that something was broken before, wrong file
> > permission of a file, a file was overwritten or whatever which hadn't
> > had an impact before and that this was fixed by reinstalling/updating
> > the appropriate package. Probably just reinstalling the appropriate
> > package from [core], whatever package it was, would have helped, too.
> 
> I don't know what was going on here but now I downgraded my system to
> [core] again each package one by one and the system booted every time
> without a kernel panic. There was likely something broken but I can't
> imagine what, maybe some file permissions have been change or some
> files have been changed or deleted by whatever and these files were
> overwritten by the reinstalling/updating. Probably a reinstall of the
> involved package from [core] had been sufficient.
> 
> Greetings,
> Heiko
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAks+xQMACgkQWSjv55S0LfHahACgl1lQ84dWisIKC6vK2utI8DLB
JrsAniODlmxdGzTwxEfwPqHM6l02fP+j
=hc87
-----END PGP SIGNATURE-----