Bug 73531

Summary:	3.14 doesn't boot but results in reset to BIOS screen
Product:	EFI	Reporter:	Henrik Kuhn (henrik.kuhn)
Component:	Boot	Assignee:	EFI Virtual User (efi)
Status:	CLOSED INSUFFICIENT_DATA
Severity:	normal	CC:	alan, matt, rzr
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	3.14	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	hwinfo dump & sys/firmware/efi/efivars content

Description Henrik Kuhn 2014-04-04 17:45:46 UTC

Created attachment 131431 [details]
hwinfo dump & sys/firmware/efi/efivars content

I can not get to boot into any of the latest openSUSE default-3.14 kernels successfully. The boot loader in use is grub2-x86_64-efi-2.00-39.8.1.
The message 'loading initial ramdisk ...' is shown and then a hw reset occurs,
because the BIOS screen pops up again, ... 

The kernel is installed by use of zypper from a running openSuSE 13.1:
# uname -a
Linux chemxen1 3.11.10-7-default #1 SMP Mon Feb 3 09:41:24 UTC 2014 (750023e)
x86_64 x86_64 x86_64 GNU/Linux

# zypper ar http://download.opensuse.org/repositories/Kernel:/stable/standard
Kernel:stable
Adding repository 'Kernel:stable'
...................................................................................................................[done]
Repository 'Kernel:stable' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://download.opensuse.org/repositories/Kernel:/stable/standard

# zypper in --from Kernel:stable kernel-default
Building repository 'Kernel:stable' cache
...........................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  kernel-default-3.14.0-2.1.gfa168d7 

1 new package to install.
Overall download size: 43.9 MiB. After the operation, additional 177.8 MiB will
be used.
Continue? [y/n/? shows all options] (y): 
Retrieving package kernel-default-3.14.0-2.1.gfa168d7.x86_64                   
                                      (1/1),  43.9 MiB (177.8 MiB unpacked)
Retrieving: kernel-default-3.14.0-2.1.gfa168d7.x86_64.rpm
...............................................................................[done
(3.5 MiB/s)]
(1/1) Installing: kernel-default-3.14.0-2.1.gfa168d7
................................................................................................[done]
Additional rpm output:

Kernel image:   /boot/vmlinuz-3.14.0-2.gfa168d7-default
Initrd image:   /boot/initrd-3.14.0-2.gfa168d7-default
KMS drivers:     i915
Root device:    /dev/disk/by-id/ata-ST2000NM0033-9ZM175_Z1X0R702-part3
(/dev/sda3) (mounted on / as ext4)
Resume device:  /dev/disk/by-label/swap (/dev/sda2)
Microcode: Adding Intel microcode 06-3c-03
Kernel Modules: thermal processor fan scsi_dh scsi_dh_hp_sw scsi_dh_emc
scsi_dh_alua scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915
usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj
hid-generic hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat
hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung hid-apple
hid-belkin hid-cherry hid-ezkey hid-microsoft ehci-pci ohci-pci 
Features:       acpi intel_microcode kms plymouth block usb resume.userspace
resume.kernel

# reboot

Comment 1 Matt Fleming 2014-04-10 11:45:33 UTC

Henrik, are you able to compile an upstream kernel and install that? The easiest way to track down your issue is to use git bisect to find the offending commit, especially with these kinds of "my machine resets" issues.

Comment 2 Henrik Kuhn 2014-04-10 11:55:21 UTC

Matt, I've never compiled a kernel before. But with some guidance from you and http://kernelnewbies.org/KernelBuild I hope I can manage it. It's something I always wanted to do.

Comment 3 Philippe "RzR" Coval 2014-08-12 14:20:18 UTC

Hi,
While trouble shotting efi issues on 3.14.3 (3.14.2 did work flawlessly)

I came to this change :

http://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit/?h=urgent&id=7b2a583afb4ab894f78bc0f8bd136e96b6499a7e

can you please attach your .config file to check if the relocation feature is set...

Regards

Comment 4 Matt Fleming 2014-10-09 10:39:45 UTC

Closing due to lack of info. If you can provide the info request, please go ahead and reopen.