Launchpad has imported 3 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=197895.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-11-16T15:00:18+00:00 kernel.9566d wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/28 ------------------------------------------------------------------------ On 2019-04-23T00:57:03+00:00 mail+kernel-bugzilla wrote: 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 <m...@codeblueprint.co.uk> Date: Fri Feb 26 21:22:05 2016 +0000 efi: Refactor efi_memmap_init_early() into arch-neutral code Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/30 ------------------------------------------------------------------------ On 2019-04-23T01:03:59+00:00 mail+kernel-bugzilla wrote: I can also add that when the kernel is started via kexec instead of via normal hardware boot, the problem does not occur. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/comments/32 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is 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: Confirmed 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: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
