kernel 4.10 fails to boot on AMD E-350D APU

Bug #1730069 reported by Patrick Mackinlay on 2017-11-04
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
High
Unassigned

Bug Description

I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 motherboard). This has always worked fine until the kernel was upgraded to 4.10 as part of the regular system upgrades. Since then the machine wont boot, there are no errors, the screen just stays blank. If I boot using a previous kernel (such as 4.8.0-58-generic) then it all works fine.

As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have tried have failed, currently this includes:

linux-image-4.10.0-30-generic
linux-image-4.10.0-32-generic
linux-image-4.10.0-33-generic
linux-image-4.10.0-38-generic
linux-image-4.13.0-16-generic

---
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pim 1369 F.... pulseaudio
 /dev/snd/controlC0: pim 1369 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
InstallationDate: Installed on 2017-03-11 (238 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
IwConfig:
 enp2s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=screen
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-58-generic N/A
 linux-backports-modules-4.8.0-58-generic N/A
 linux-firmware 1.157.13
RfKill:

Tags: xenial
Uname: Linux 4.8.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/18/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: E350N WIN8
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Patrick Mackinlay (patrick73u) wrote :

The package that first caused this problem was linux-image-4.10.0-32-generic (linux-image-4.10.0-33-generic doesnt work either)

Andreas Moog (ampelbein) on 2017-11-04
affects: xubuntu-meta (Ubuntu) → linux (Ubuntu)

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1730069

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: yakkety

apport information

tags: added: apport-collected xenial
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Patrick Mackinlay (patrick73u) wrote :

I have run the apport-collect command, obviously this was not executed when running any of the kernels that have this issue, it was running with a working kernel, 4.8.0-58-generic.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Kai-Heng Feng (kaihengfeng) wrote :

Please try -edge HWE stack: `sudo apt install linux-generic-hwe-16.04-edge`

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Patrick Mackinlay (patrick73u) wrote :

I am afraid it doesn't boot with linux-generic-hwe-16.04-edge either.

Kai-Heng Feng (kaihengfeng) wrote :

Sorry I missed your first comment. Does it boot with linux-image-4.10.0-30-generic?

Patrick Mackinlay (patrick73u) wrote :

All the linux kernels above 4.8 that I have tried have failed, currently this includes:

linux-image-4.10.0-30-generic
linux-image-4.10.0-32-generic
linux-image-4.10.0-33-generic
linux-image-4.10.0-38-generic
linux-image-4.13.0-16-generic

description: updated
Download full text (8.0 KiB)

> On 8 Nov 2017, at 6:53 AM, Patrick Mackinlay <email address hidden> wrote:
>
> All the linux kernels above 4.8 that I have tried have failed, currently
> this includes:

Then regression happens between v4.8 and v4.10.

Make sure mainline v4.8 from [1] doesn’t have the issue, and mainline v4.10 has the issue.
After that, can you try Linux v4.9?

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline

>
> linux-image-4.10.0-30-generic
> linux-image-4.10.0-32-generic
> linux-image-4.10.0-33-generic
> linux-image-4.10.0-38-generic
> linux-image-4.13.0-16-generic
>
>
> ** Description changed:
>
> - I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 motherboard). This has always worked fine until the kernel was upgraded to 4.10 as part of the regular system upgrades. Since then the machine wont boot, there are no errors, the screen just stays blank. If I boot using a previous kernel (such as 4.8.0-58-generic) then it all works fine.
> - ---
> + I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
> + motherboard). This has always worked fine until the kernel was upgraded
> + to 4.10 as part of the regular system upgrades. Since then the machine
> + wont boot, there are no errors, the screen just stays blank. If I boot
> + using a previous kernel (such as 4.8.0-58-generic) then it all works
> + fine.
> +
> + As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
> + tried have failed, currently this includes:
> +
> + linux-image-4.10.0-30-generic
> + linux-image-4.10.0-32-generic
> + linux-image-4.10.0-33-generic
> + linux-image-4.10.0-38-generic
> + linux-image-4.13.0-16-generic
> +
> + ---
> ApportVersion: 2.20.1-0ubuntu2.10
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC1: pim 1369 F.... pulseaudio
> - /dev/snd/controlC0: pim 1369 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC1: pim 1369 F.... pulseaudio
> + /dev/snd/controlC0: pim 1369 F.... pulseaudio
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
> InstallationDate: Installed on 2017-03-11 (238 days ago)
> InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
> IwConfig:
> - enp2s0 no wireless extensions.
> -
> - lo no wireless extensions.
> + enp2s0 no wireless extensions.
> +
> + lo no wireless extensions.
> MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
> Package: linux (not installed)
> ProcEnviron:
> - LANGUAGE=en_GB:en
> - TERM=screen
> - PATH=(custom, no user)
> - LANG=en_GB.UTF-8
> - SHELL=/bin/bash
> + LANGUAGE=en_GB:en
> + TERM=screen
> + PATH=(custom, no user)
> + LANG=en_GB.UTF-8
> + SHELL=/bin/bash
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
> ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
> PulseList:
> - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
> - No PulseAudio da...

Read more...

Patrick Mackinlay (patrick73u) wrote :

Trying the amd64 kernels at

http://kernel.ubuntu.com/~kernel-ppa/mainline/

The last 4.8 kernel (linux-image-4.8.17-040817-generic_4.8.17-040817.201701090438_amd64.deb) boots fine. None of the 4.9 kernels I tried (v4.9.1 and v4.9-rc1) boot.

So it seems that this regression was introduced in 4.9

Kai-Heng Feng (kaihengfeng) wrote :
Download full text (3.9 KiB)

> On 9 Nov 2017, at 7:04 PM, Patrick Mackinlay <email address hidden> wrote:
>
> Trying the amd64 kernels at
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> The last 4.8 kernel (linux-
> image-4.8.17-040817-generic_4.8.17-040817.201701090438_amd64.deb) boots
> fine. None of the 4.9 kernels I tried (v4.9.1 and v4.9-rc1) boot.
>
> So it seems that this regression was introduced in 4.9

Thanks for your testing.

Can you try v4.8? Not the v4.8.x but v4.8.

If you can confirm v4.8 works, we need to bisect between v4.8 and v4.9-rc1.

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1730069
>
> Title:
> kernel 4.10 fails to boot on AMD E-350D APU
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
> motherboard). This has always worked fine until the kernel was
> upgraded to 4.10 as part of the regular system upgrades. Since then
> the machine wont boot, there are no errors, the screen just stays
> blank. If I boot using a previous kernel (such as 4.8.0-58-generic)
> then it all works fine.
>
> As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
> tried have failed, currently this includes:
>
> linux-image-4.10.0-30-generic
> linux-image-4.10.0-32-generic
> linux-image-4.10.0-33-generic
> linux-image-4.10.0-38-generic
> linux-image-4.13.0-16-generic
>
> ---
> ApportVersion: 2.20.1-0ubuntu2.10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: pim 1369 F.... pulseaudio
> /dev/snd/controlC0: pim 1369 F.... pulseaudio
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
> InstallationDate: Installed on 2017-03-11 (238 days ago)
> InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
> IwConfig:
> enp2s0 no wireless extensions.
>
> lo no wireless extensions.
> MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
> Package: linux (not installed)
> ProcEnviron:
> LANGUAGE=en_GB:en
> TERM=screen
> PATH=(custom, no user)
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
> ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
> PulseList:
> Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
> No PulseAudio daemon running, or not running as session daemon.
> RelatedPackageVersions:
> linux-restricted-modules-4.8.0-58-generic N/A
> linux-backports-modules-4.8.0-58-generic N/A
> linux-firmware 1.157.13
> RfKill:
>
> Tags: xenial
> Uname: Linux 4.8.0-58-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> _MarkForUpload: True
> dmi.bios.date: 01/18/2013
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: F3
> dmi.board.asset.tag: T...

Read more...

Patrick Mackinlay (patrick73u) wrote :

I can confirm that 4.8.0-040800-generic works fine.

Kai-Heng Feng (kaihengfeng) wrote :

I can build kernel packages for you, but it'll be much faster if you build kernel locally:

$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good v4.8
$ git bisect bad v4.9-rc1
$ make localmodconfig
$ make -j`nproc` deb-pkg
Then install the newly built kernel.

If the issue still happens,
$ git bisect bad

Otherwise,
$ git bisect good

Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

Patrick Mackinlay (patrick73u) wrote :

I can do it, but the E-350D is not the fastest CPU out there (I dont have access to any other debian boxes at the moment). It took around 1.5 hours to build the first package and it looks like it will take up to 13 more steps, so it may be quite a few days before I have the broken commit.

Patrick Mackinlay (patrick73u) wrote :

I have found the broken commit, its 9479c7cebfb568f8b8b424be7f1cac120e9eea95

The git bisect process ended with:

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[9479c7cebfb568f8b8b424be7f1cac120e9eea95] efi: Refactor efi_memmap_init_early() into arch-neutral code

That revisions kernel fails, the one before that, ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac, works.

Kai-Heng Feng (kaihengfeng) wrote :

Huge thanks!

Please file an upstream bug at https://bugzilla.kernel.org/
Product: EFI
Component: Boot

I have a GA-E350N-WIN8 gigabyte motherboard, after kernel commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95 the amd64 kernel no longer boots (commit ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac) works.

This bug was found with ubuntu and reported at:
https://bugs.launchpad.net/bugs/1730069

Wit the broken kernel, ubuntu wont book, the screen just stays blank.

I can confirm this bug on different hardware (a Chromebook Samsung 500C).

It, too, gets a black screen on boot.

My kernel bisection has also identified this as the first bad commit:

    9479c7cebfb568f8b8b424be7f1cac120e9eea95 is the first bad commit
    commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95
    Author: Matt Fleming <email address hidden>
    Date: Fri Feb 26 21:22:05 2016 +0000

        efi: Refactor efi_memmap_init_early() into arch-neutral code

nh2 (nh2) wrote :

I can confirm this bug, on different hardware.

My kernel bisection resulted in the same commit (thus I found this bug).

I commented on https://bugzilla.kernel.org/show_bug.cgi?id=197895#c1

I can also add that when the kernel is started via kexec instead of via normal hardware boot, the problem does not occur.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.