Mailinglist Archive: opensuse-bugs (4243 mails)

< Previous Next >
[Bug 1017783] Boot issues with Tumbleweed and Kernel 4.9 (booting stops at Loading initial ramdisk; kernel 4.9 does not boot)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 05 Jan 2017 22:30:32 +0000
  • Message-id: <bug-1017783-21960-hgmbWWtuWv@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1017783
http://bugzilla.suse.com/show_bug.cgi?id=1017783#c16

--- Comment #16 from Borislav Petkov <bpetkov@xxxxxxxx> ---
(In reply to Robert Pretki from comment #14)
I have just sent to your e-mail address a link to the video (MKV, x264),
which includes:
(1) boot with the default settings;
(2) boot without "quiet";
(3) boot with "dis_ucode_ldr" (instead of "quiet");
(4) boot without "initrd" line;

Thanks for doing that. It doesn't tell us much but at least it doesn't
look like the initrd changes anything so it must be something happening
very early causing the machine to triple-fault.

The nasty thing is that debugging such an issue on a laptop is always a
PITA as we can't log serial console.

One thing I could think of is to try booting with "nosmp nomodeset"
so that we init only one CPU and thus avoid a whole lot of init code
and see whether that works. The "nomodeset" should switch off the gfx
modesetting so that we can maybe see more output from the kernel.

Before you reboot though, edit /etc/default/grub and change
GRUB_TERMINAL to "console":

GRUB_TERMINAL="console"

Then do:

# grub2-mkconfig -o /boot/grub2/grub.cfg

and reboot. When you're back in the grub menu, remove "quiet" and add
"nosmp nomodeset ignore_loglevel" and then press F10. And upload the
video again.

Hopefully, we'll be able to see more output.

Thanks.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References