https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c2 --- Comment #2 from Per Jessen 2014-08-07 07:50:42 UTC --- Created an attachment (id=601441) --> (http://bugzilla.novell.com/attachment.cgi?id=601441) serial log capture This is from a boot-up with maxcpus=0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c4 --- Comment #4 from Per Jessen 2014-08-07 09:18:22 UTC --- (In reply to comment #3)

...

[ 0.000000] Kernel command line: BOOT_IMAGE=openSUSE root=/dev/disk/by-id/cciss-3600508b100184155435050384d320013-part1 noresume maxcpus=0 console=ttyS0,115200,8n1 [...] [ 1.459732] Failed to execute /init [ 1.463297] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

I do not see initrd in the command line. Are you sure you don't need it?

With the kernel that works, the initrd isn't mentioned in the command line either: Kernel command line: BOOT_IMAGE=openSUSE root=/dev/disk/by-id/cciss-3600508b100184155435050384d320013-part1 noresume Looking at other systems, there is also no initrd mentioned in the command line arguments.

Also have you tried to follow recommendations from Documentation/init.txt (in the kernel source tree)?

Uh no - when one kernel works, and the other doesn't, it seems quite clear. Is there anything specific in Documentation/init.txt you believe will help? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c6 --- Comment #6 from Michal Hocko 2014-08-07 12:04:10 CEST --- Ohh, wait a second. I have completely overlooked this: [ 0.952231] Unpacking initramfs... [ 0.958647] NMI: PCI system error (SERR) for reason b1 on CPU 0. [ 0.960017] Dazed and confused, but trying to continue Which means that there was a critical error reported by a PCI device. It seems that the error was fatal because recoverable errors are usually reported by MCE. I am not familiar with PCI internals enough to tell you details though. I have no idea what b1 as a reason means. I have also no idea why the issue is seen only with pae kernel (maybe the memory layout is slightly different) or maybe there is a BIOS bug which results in an overlapping areas or a weird PCI setup when PAE is enabled. Will try to look deeper into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c8 --- Comment #8 from Michal Hocko 2014-08-07 16:13:23 CEST --- In the initial comment you've said that the -default kernel boots just fine. Was that a 32b -default kernel? I suppose so but wanted to be sure. Also have you tried to boot 64b kernel on that machine? Finally have you ever tried to install different PAE kernels on that machine? E.g. the current upstream vanilla? There is a HEAD repository in build service where you can find it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c10 --- Comment #10 from Per Jessen 2014-08-07 15:43:33 UTC --- (In reply to comment #9)

I am not certain, but I am pretty certain I have had 12.1 running with -pae on this machine earlier. I'll try out some older kernels and see what happens.

Have just installed and booted with 3.1.0-1.2-pae, works fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c12 --- Comment #12 from Per Jessen 2014-08-07 16:39:07 UTC --- Have now booted with 3.7.10-1.1-pae, also works fine. I'll get the console logs to you later today. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c14 --- Comment #14 from Per Jessen 2014-08-07 16:50:19 UTC --- (In reply to comment #13)

Sounds like you didn't get the hw error this time, assuming it is a hw error this NMI reports. How reproducible is this issue?

I doubt if the NMI is a hardware error, but that's just my gut feeling. The issue is easily reproducable, except right now when I booted 3.11.10-17-pae with all the debug options you requested - this time it worked, no NMI. I'll upload both console logs in a minute, then try 3.11.10 again without the debug options. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c16 --- Comment #16 from Per Jessen 2014-08-07 16:55:27 UTC --- Created an attachment (id=601570) --> (http://bugzilla.novell.com/attachment.cgi?id=601570) console log from booting with 3.11.10-pae and debug options. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c18 --- Comment #18 from Borislav Petkov 2014-08-07 19:02:44 UTC ---

I doubt if the NMI is a hardware error, but that's just my gut feeling.

The NMI is used to report a hw error.

I noticed it automagically pulled in kernel-firmware. Presumably this means kernel-pae did not. Packaging issue?

Do you start getting the error again if you forcibly remove kernel-firmware and reboot the PAE kernel? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=890702 https://bugzilla.novell.com/show_bug.cgi?id=890702#c19 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|per@computer.org | Resolution| |WORKSFORME --- Comment #19 from Per Jessen 2014-08-10 08:54:57 UTC --- (In reply to comment #18)

...

I doubt if the NMI is a hardware error, but that's just my gut feeling.

The NMI is used to report a hw error.

...

I noticed it automagically pulled in kernel-firmware. Presumably this means kernel-pae did not. Packaging issue?

Do you start getting the error again if you forcibly remove kernel-firmware and reboot the PAE kernel?

Removed kernel-firmware, rebooted, no problem. I mistook kernel-firmware for being the microcode updates, so I also removed ucode-intel, and rebooted. Again no problem. I am unable to reproduce the problem, I am closing for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.