I just recently installed Archlinux on Samsung ultrabook series 9. I frequently bumps into this Processor context corrup that causes a kernel panic.
I am running kernel version 3.5.4-1 with UEFI boot.
Any idea guys?
Those errors are almost always due to hardware problems, the screenshot has messages like : run the above through mcelog --ascii
mcelog is in [community] repo.
Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them
gColossus, just want to say that I get the exact same error and it often takes me ~15 minutes to get booted up after many many attempts and kernel panics.
Sometimes it doesn't even get that far and freezes at loading initrd and blinking the caps lock. Once I get booted everything is fine mostly (until Gnome blanks my screen (which can't be disabled in Gnome 3!!? WTF?) and can't turn it back on forcing me to reboot and wait 15 more minutes!).
I have the same kernel (been waiting for a kernel update hoping this will go away since I got this laptop a few weeks ago!) also UEFI boot using instructions from https://wiki.archlinux.org/index.php/Installation_Guide and https://wiki.archlinux.org/index.php/Un … n_in_Linux.
Seeing the EXACT same error gives me hope my laptop hardware is ok.
@gojamiegirl: Same here. I freezes randomly, but mostly right after grub finishes loading initramfs.
However, I would not hold my hope up too high. My machine STOPPED working around 2 hours ago. It doesn't even go past POST (Power On Self-Test). The power light is on but the screen remains black the whole time. The laptop is too thin so it does't have any indicators thus I can't tell whether the machine is working or not. Just printed the UPS label to send it back for warranty. I just hope that I don't have to reinstall everything from scratch.
Best of luck with yours though. What laptop do you have?
@gColossus, forgot to say the most important part, which is that I also have a Samsung Series 9, just got it about 3 weeks ago.
@gojamiegirl: I don't have any other friends that are running UEFI on this samsung ultrabook. Did you update your BIOS firmware prior to installing Arch with UEFI? It seems like the problem is related to the crappy UEFI implementation that samsung has at the moment ...
Last edited by gColossus (2012-10-06 03:25:44)
I haven't updated my BIOS, I'll check that out.
Confirmed: The MCE only happens on kernel 3.4 +, the latest stable kernel I could use is:
Linux version 3.3.8-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.0 20120505 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012
You could grab that from Arch rollback machine. If you have made the switch to systemd, make sure you add i915 to the MODULES setting in mkinitcpio.conf and regenerate the initramfs.
I filed a bug report here for the issue: https://bugzilla.kernel.org/show_bug.cgi?id=49161
Last edited by gColossus (2012-10-20 21:45:39)
btw, I'm seeing this still in Linux 3.6.x and 3.7.x on my Samsung Series 9 NP900X3C. It seems to be a problem with the samsung-laptop kernel module when booting in UEFI mode. Blacklisting it fixes it (but causes rfkill and keyboard backlighting to stop working). More info on my blog and the kernel bugzilla.
Last edited by stickyboy (2012-12-21 18:21:22)
Anyone found a solution to this?
I've both blacklisted samsung-laptop and added i915 to modules in mkinitcpio.conf, and still have the kernel panics occuring.
Running kernel 3.16.3-1 on a Samsung new series 9 NP900X3D.
EDIT: I use BIOS, not UEFI
Last edited by deifyed (2014-09-24 15:41:30)
I boot with BIOS (not UEFI), and also have kernel panics happening once in a while. That's with the NP900X3C.