Kernel 4.4.0.145 (& subsequent) boots to black screen.

Bug #1832863 reported by 2CV67
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019.
On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite.
I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black.
I escaped using REISUO & retried several times with the same result.
If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black.
So the PC is not freezing, just no screen.
Trying Ctrl+Alt+F1 (or other F keys) produces nothing.

I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen.

On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145.

So I am unable to use this PC AT ALL with current kernels.

I asked about this problem on Ubuntu Forum
https://ubuntuforums.org/showthread.php?t=2415972
with no success & the suggestion was to raise this bug...
There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142).

chris@Netbk:~$ inxi -Fzr
System: Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit)
           Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial
Machine: System: ASUSTeK (portable) product: 1015PE v: x.x
           Mobo: ASUSTeK model: 1015PE v: x.xx
           Bios: American Megatrends v: 0801 date: 10/06/2010
CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB
           clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz
Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1024x600@60.00hz
           GLX Renderer: Mesa DRI Intel Pineview M
           GLX Version: 1.4 Mesa 18.0.5
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 1742 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4
InstallationDate: Installed on 2014-09-08 (1739 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUSTeK Computer INC. 1015PE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-142-generic N/A
 linux-backports-modules-4.4.0-142-generic N/A
 linux-firmware 1.157.21
Tags: xenial
Uname: Linux 4.4.0-142-generic x86_64
UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1832863

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: xenial
Revision history for this message
2CV67 (2cv67) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
2CV67 (2cv67) wrote : CRDA.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : CurrentDmesg.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : IwConfig.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : Lspci.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : Lsusb.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : ProcEnviron.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : ProcInterrupts.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : ProcModules.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : RfKill.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : UdevDb.txt

apport information

Revision history for this message
2CV67 (2cv67) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Would it be possible to try 4.4.0-143?

Revision history for this message
2CV67 (2cv67) wrote :

Sorry for the late reply!

I tried 4.4.0-143 and that does NOT give me a black screen.

Actually, I get a degraded screen, like in recovery mode, but maybe I did not install -143 correctly as I never tried to install an old version before?
I used Synapt & installed:
 linux-headers-4.4.0-143
 linux-headers-4.4.0-143-generic
 linux-image-4.4.0-143-generic
 linux-modules-4.4.0-143-generic

If there is a better way, I could try again.

Thanks for your interest!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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