You are not logged in.
Hi
since the last Kernel update (I think it was the 2.6.34.2-2) I can't boot my laptop (Acer extensa 2900 (i686 )).
Here is the output:
init[1] segfault at 3 ip 00000003 sp bf991994 error 4
Kernel panic - not syncing: Attempted to kill init
I tried to reinstall sysvinit and reinstall the kernel but nothing helped! Not even fallback is working or the lts kernel
So any idea what I should do?
Thanks
Chris
Offline
Here a few more informations:
My root and swap partition is encrypted.
This is the call trace after the kernel panic:
Call Trace:
...
...
...
do_signal
printk
bad_area_nosemaphore
bad_area
do_page_fault
do_page_fault
do_notify_resume
work_notifysig
These are the last packages I updated (they where in /var/cache/pacman....)
-rw------- 1 root root 693772 Aug 2 12:41 akonadi-1.4.0-1-i686.pkg.tar.xz
-rw------- 1 root root 3751440 Jul 23 21:32 avidemux-cli-2.5.3-3-i686.pkg.tar.xz
-rw------- 1 root root 719664 Jul 23 21:32 avidemux-gtk-2.5.3-3-i686.pkg.tar.xz
-rw------- 1 root root 26608 Jul 25 21:43 cabextract-1.3-1-i686.pkg.tar.xz
-rw------- 1 root root 14185744 Jul 28 13:50 chromium-5.0.375.125-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 74624 Aug 6 20:27 consolekit-0.4.1-3-i686.pkg.tar.xz
-rw------- 1 root root 180176 Aug 5 17:04 farsight2-0.0.21-1-i686.pkg.tar.xz
-rw------- 1 root root 3216956 Jul 23 21:32 ffmpeg-24460-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 3216708 Aug 6 21:55 ffmpeg-24460-2-i686.pkg.tar.xz
-rw-r--r-- 1 root root 76720 Aug 6 11:14 ffmpegthumbnailer-2.0.3-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 4516 Aug 7 11:37 filesystem-2010.07-1-any.pkg.tar.xz
-rw------- 1 root root 778360 Jul 23 21:32 firefox-3.6.8-1-i686.pkg.tar.xz
-rw------- 1 root root 9555264 Aug 1 15:05 gimp-2.6.10-1-i686.pkg.tar.xz
-rw------- 1 root root 2003496 Jul 28 18:04 git-1.7.2.1-1-i686.pkg.tar.xz
-rw------- 1 root root 2001864 Jul 22 18:37 git-1.7.2-1-i686.pkg.tar.xz
-rw------- 1 root root 1387884 Aug 2 08:01 gnupg2-2.0.16-1-i686.pkg.tar.xz
-rw------- 1 root root 23416 Aug 1 02:26 gsopcast-0.4.0-3-i686.pkg.tar.xz
-rw------- 1 root root 166612 Jul 23 21:32 gstreamer0.10-ugly-0.10.15-2-i686.pkg.tar.xz
-rw------- 1 root root 81672 Jul 23 21:32 gstreamer0.10-ugly-plugins-0.10.15-2-i686.pkg.tar.xz
-rw-r--r-- 1 root root 197660 Aug 7 11:37 iana-etc-2.30-1-any.pkg.tar.xz
-rw------- 1 root root 23274696 Aug 4 21:32 kernel26-2.6.34.2-2-i686.pkg.tar.xz
-rw------- 1 root root 3908608 Aug 4 21:32 kernel26-headers-2.6.34.2-2-i686.pkg.tar.xz
-rw-r--r-- 1 root root 21897400 Aug 6 20:30 kernel26-lts-2.6.32.17-2-i686.pkg.tar.xz
-rw------- 1 root root 158324 Jul 23 07:28 libast-0.7-3-i686.pkg.tar.xz
-rw------- 1 root root 90800 Aug 2 19:41 libdrm-2.4.21-2-i686.pkg.tar.xz
-rw------- 1 root root 212024 Jul 25 19:15 libgdiplus-2.6.7-1-i686.pkg.tar.xz
-rw------- 1 root root 246712 Aug 5 16:56 libnice-0.0.13-1-i686.pkg.tar.xz
-rw------- 1 root root 4740052 Jul 21 22:34 libpurple-2.7.2-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 114428 Aug 6 21:55 libva-1.0.4-1-i686.pkg.tar.xz
-rw------- 1 root root 188344 Jul 28 07:13 lua-5.1.4-6-i686.pkg.tar.xz
-rw------- 1 root root 297556 Jul 26 04:08 module-init-tools-3.12-1-i686.pkg.tar.xz
-rw------- 1 root root 30262880 Jul 25 19:15 mono-2.6.7-1-i686.pkg.tar.xz
-rw------- 1 root root 8622796 Jul 23 21:32 mplayer-31774-1-i686.pkg.tar.xz
-rw------- 1 root root 31436036 Jul 30 19:55 openjdk6-6.b18_1.8.1-1-i686.pkg.tar.xz
-rw------- 1 root root 1172212 Jul 22 05:07 p7zip-9.13-2-i686.pkg.tar.xz
-rw------- 1 root root 12608184 Aug 2 17:17 perl-5.12.1-2-i686.pkg.tar.xz
-rw------- 1 root root 148544 Aug 2 17:30 perl-xml-parser-2.36-7-i686.pkg.tar.xz
-rw------- 1 root root 1111124 Jul 21 22:34 pidgin-2.7.2-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 26096 Aug 7 11:37 rpcbind-0.2.0-2-i686.pkg.tar.xz
-rw-r--r-- 1 root root 345252 Aug 6 20:30 sqlite3-3.7.0.1-1-i686.pkg.tar.xz
-rw------- 1 root root 345204 Jul 26 16:02 sqlite3-3.7.0-1-i686.pkg.tar.xz
-rw------- 1 root root 701396 Jul 22 09:35 syslinux-4.02-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 76431 May 6 2009 sysvinit-2.86-5-i686.pkg.tar.gz
-rw------- 1 root root 9063412 Aug 5 18:06 thunderbird-3.1.2-1-i686.pkg.tar.xz
-rw------- 1 root root 21457 Feb 24 2009 tsocks-1.8beta5-2-i686.pkg.tar.gz
-rw------- 1 root root 1739340 Jul 30 13:04 ttf-thai-0.4.14-1-any.pkg.tar.xz
-rw------- 1 root root 180472 Jul 31 12:19 tzdata-2010k-1-i686.pkg.tar.xz
-rw------- 1 root root 5206648 Jul 26 09:32 virtuoso-6.1.2-1-i686.pkg.tar.xz
-rw------- 1 root root 7026544 Jul 23 21:32 vlc-1.1.1-3-i686.pkg.tar.xz
-rw------- 1 root root 6956100 Jul 30 06:43 vlc-1.1.2-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root 6949200 Aug 6 21:55 vlc-1.1.2-2-i686.pkg.tar.xz
-rw------- 1 root root 12423868 Jul 29 21:13 wine-1.2-3-i686.pkg.tar.xz
-rw------- 1 root root 12677320 Jul 31 00:08 wine-1.3.0-1-i686.pkg.tar.xz
-rw------- 1 root root 8180920 Aug 1 15:05 wireshark-1.2.10-1-i686.pkg.tar.xz
-rw------- 1 root root 8185904 Aug 2 09:36 wireshark-1.2.10-2-i686.pkg.tar.xz
-rw------- 1 root root 331952 Jul 23 21:32 x264-20100722-1-i686.pkg.tar.xz
-rw------- 1 root root 2763408 Jul 28 19:29 xine-lib-1.1.19-1-i686.pkg.tar.xz
-rw------- 1 root root 14161000 Jul 23 21:32 xulrunner-1.9.2.8-1-i686.pkg.tar.xz
I rolled back the following packages:
kernel26 to: kernel26-2.6.33.4
kernel26-headers: kernel26-headers-2.6.33.4-1
filesystem: filesystem-2010.02-4
sysvinit: sysvinit-2.86-5
with the same result.
Booting from the CD works just fine. Chrooting into the encrypted root works also fine..... so I don't think it's an HW issue.
Anyway any help is appreciated!
Thanks
Chris
Edit @6:19pm ESDT
So I suspect that it has something todo with the initramfs I just used the Kernel and initramfs .img from the arch boot CD and it's kind of working but the CD lacks the encrypted support so he can't find my hdd....
My questions now: Where can I get a working initramfs image with encrypted HDD support? How do I fix my initramfs problem? and how did this happen? Thanks!!
Last edited by smayer (2010-08-07 22:24:31)
Offline
Hi,
ok my suspicion with the initramfs was right. When I build an image within the live system of the CD I can boot my machine with that image. BUT for some reason he won't create the corresponding mapper device. So when he tries to check the filesystem of the unencrypted device "/dev/mapper/root" he can't find it and stops the boot process. I get a shell and a read only mounted unencrypted root device. When I now remount the device as readable I can start with init 5 my normal system. But this is obviously no solution...
What I don't understand is:
What is wrong with my system that it's generates faulty initram images? And of course how can i fix it?
When I boot with the CD generated initram image: Why won't he create my root device in /dev/mapper? But since I can access the filesystem..... from which device was it mounted then (the filesystem)? /etc/mtab says that /dev/mapper/root is mounted. "df -h" shows under /dev/mapper/root the filesystem with the correct size and used parameters. But in /dev/mapper there is only the control file.
Here are the kernel parameters fro booting my device:
kernel /vmlinz26 cryptdevice=/dev/sda3:root root=/dev/mapper/root ro
initrd /cdimage.img
And i'm still using the 2.6.33.4 kernel. Did they change the syntax to 2.6.34? I couldn't find anything....
Again any help is appreciated!
Thanks,
Chris
Offline
sorry it's me again.....
Still found no solution - and I don´t know what else I could try.
Whould be nice if somebody could upload his 2.4.34.2-2 Kernel initram img. Maybe it's working with an image that wasn´t build with my machine.
If you have any other idea - please let me know.
Thanks,
Chris
Offline
I've been having this problem as well, since kernel 2.6.34, - 2.6.34.1
I am going to try 35, mine is 64bit, i think its a bug
Offline
Hi olo,
I already tried the 35er kernel. Bulit it from source - but it didn´t help anything.....
Offline
Try downgrading module-init-tools.
I don't know a solution to your problem, but the important thing to understand here is that 'init' segfaulted. The kernel panic is a result of this, since it doesn't make sense to continue.
Now the question is what exactly failed. From what you describe, my guess is that the 'init' script from the initial ramdisk dies. You can find this script in /lib/initcpio. You'll also see that it is 'echo'ing some status messages, so carefully look into the messages leading to the segfault to see how far the script came before it died. For debugging, you can include further messages into the script and rerun 'mkinitcpio' (see its wiki page for more information). You can also extract the initial ramdisk into some directory and modify it there (again, see the wiki page).
Also, you can modify the script to directly launch you into a shell. For this, just call 'launch_interactive_shell' right after the 'msg ":: Loading Initramfs"'. You can then go over the script line-by-line and try it out.
However, before spending too much time with this, I'd double-check that your RAM isn't faulty. Just let memcheck86+ do a few passes over night.
Offline
interesting point with the faulty RAM.... because memtest hangs everytime I try to start it. I switched the modules but nothing changed. I don't have any extra modules to replace them or at least test them.
I have 2 modules and even if I remove one memtest still will hang.
And if the memory is faulty why can I use the machine when I boot from CD or use an old kerenl.img (built with the CD)? And why did it happen right after the kernel upgrade...... ?! I don't know.
What about you olo any news? Have you tried memtest?
Thanks
Chris
Offline
Make sure you are using the most up to date version of memtest, i.e. Memtest+ V4.10 which you can download here:
Offline
And if the memory is faulty why can I use the machine when I boot from CD or use an old kerenl.img (built with the CD)? And why did it happen right after the kernel upgrade...... ?! I don't know.
That's the thing with RAM errors - they behave pretty unpredictable. If one of the chips is completely fried, you will usually not get past the BIOS screen. But if for instance there are just a few bits which cannot be flipped anymore, it all depends on how that region of the RAM is used. Anyway, if you already switched the RAM and get the same segfault, that shouldn't be the issue.
However, the hanging memtest is strange. As kilgore wrote, make sure you're using the newest version. Also, load setup defaults in the BIOS, and if all else fails update the BIOS, just to be sure you're not dealing with a bug there. Have you tried downgrading module-init-tools?
Offline
Just to close this thread up:
I had finally time to reinstall arch - and now it's working fine again on the same Hardware.... so I don't know what the problem was - i still suspect that the RAM isn't working probably... (when I use firefox the whole system freezes hard sometimes...)
So anyway I'm good for now.
Thanks
Chris
Offline