[Bug 932159] New: Configuring kdump gives a system where grub fails to boot it
http://bugzilla.opensuse.org/show_bug.cgi?id=932159 Bug ID: 932159 Summary: Configuring kdump gives a system where grub fails to boot it Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: tjcw@physics.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build Identifier: I configured kdump with 'yast kdump'. Next time I tried to boot the system, grub dropped in to a shell prompt instead of booting. I think there was a grub error message displayed, but the screen was cleared too quickly for me to read what it was. Maybe the grub configuration file was malformatted. Reproducible: Always Steps to Reproduce: 1.'yast2 kdump' and configure a 128MB crash kernel 2.reboot the system to bring the crash kernel online 3.observe the failure to boot, and the grub shell prompt Actual Results: I got a grub shell prompt Expected Results: The system should have booted with the crash kernel in place I was running with Tumbleweed 2015-05-21. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
--- Comment #2 from Chris Ward
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
--- Comment #4 from Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
--- Comment #5 from Chris Ward
linuxefi /boot/vmlinuz-4.0.4-1-desktop root=UUID=2d73da7c-daad-4ab0-a1b7-9f0db170efdf ro "" ${extra_cmdline} resume=/dev/disk/by-uuid/f39ff52c-61e0-46fd-a270-cec8aad57eb0 splash=silent quiet showopts
162c162 < linuxefi /boot/vmlinuz-4.0.4-1-desktop root=UUID=2d73da7c-daad-4ab0-a1b7-9f0db170efdf ro "" ${extra_cmdline} resume=/dev/disk/by-uuid/f39ff52c-61e0-46fd-a270-cec8aad57eb0 splash=silent quiet showopts crashkernel=256M-:128M ---
linuxefi /boot/vmlinuz-4.0.4-1-desktop root=UUID=2d73da7c-daad-4ab0-a1b7-9f0db170efdf ro "" ${extra_cmdline} resume=/dev/disk/by-uuid/f39ff52c-61e0-46fd-a270-cec8aad57eb0 splash=silent quiet showopts
179c179 < linuxefi /boot/vmlinuz-4.0.4-1-desktop root=UUID=2d73da7c-daad-4ab0-a1b7-9f0db170efdf ro "" ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe crashkernel=256M-:128M ---
linuxefi /boot/vmlinuz-4.0.4-1-desktop root=UUID=2d73da7c-daad-4ab0-a1b7-9f0db170efdf ro "" ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
linux-vx2f:/boot/grub2 # Nothing obvious to me in the diff of the grub.cfg files. Now let me try and boot the system and see what happens -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932159
Chris Ward
participants (1)
-
bugzilla_noreply＠novell.com