Black Screen on 18.04 + Intel Graphics with Kernel > 4.15.0-47

Bug #1840889 reported by rz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,

we've been running 18.04 (w/ Xubuntu) + 4.15.0-47 kernel for a while now (on Minix Z83-4 devices w/ Intel X5-Z8350 CPUs), which is working fine.

After upgrading the kernel to a newer version (> 4.15.0-47), HDMI output is not available anymore, i915 reports an invalid EDID version via dmesg I dropped the full dmesg output on Pastebin: https://pastebin.com/jXTqAzkQ

As a start I'm blaming the Linux kernel since booting 4.15.0-47 kernel works just fine.

Known faulty kernel versions are:

- 4.15.0-58-generic
- 4.15.0-59-generic
- 5.0.0-25-generic

Not sure how to best collect logs and system information for you since I'm not used to debugging black screens. However, SSH access is possible. I am happy to provide more information, if needed. We can also install and test experimental kernel versions.

Note: This happens then attached via a standard HDMI cable as well as with a HDMI-DVI cable on different monitor setups.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-12 (220 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MINIX Z83-4
Package: linux (not installed)
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=7a004d84-9c8a-4004-acfc-261fff113040 ro quiet
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-58-generic N/A
 linux-backports-modules-4.15.0-58-generic N/A
 linux-firmware 1.173.9
Tags: bionic
Uname: Linux 4.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 06/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: CHT0A180
dmi.board.asset.tag: Default string
dmi.board.name: NEO Z83-4
dmi.board.vendor: MINIX
dmi.board.version: V1.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCHT0A180:bd06/29/2018:svnMINIX:pnZ83-4:pvrV1.1:rvnMINIX:rnNEOZ83-4:rvrV1.1:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: NEO
dmi.product.name: Z83-4
dmi.product.version: V1.1
dmi.sys.vendor: MINIX
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-12 (220 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MINIX Z83-4
Package: linux (not installed)
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=7a004d84-9c8a-4004-acfc-261fff113040 ro quiet
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-58-generic N/A
 linux-backports-modules-4.15.0-58-generic N/A
 linux-firmware 1.173.9
Tags: bionic
Uname: Linux 4.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 06/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: CHT0A180
dmi.board.asset.tag: Default string
dmi.board.name: NEO Z83-4
dmi.board.vendor: MINIX
dmi.board.version: V1.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCHT0A180:bd06/29/2018:svnMINIX:pnZ83-4:pvrV1.1:rvnMINIX:rnNEOZ83-4:rvrV1.1:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: NEO
dmi.product.name: Z83-4
dmi.product.version: V1.1
dmi.sys.vendor: MINIX
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-12 (225 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Package: linux (not installed)
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
Tags: bionic
Uname: Linux 5.3.0-050300rc6-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

Revision history for this message
rz (rzo1) wrote :

Added

description: updated
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 1840889

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: bionic
Revision history for this message
rz (rzo1) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
rz (rzo1) wrote : CRDA.txt

apport information

description: updated
Revision history for this message
rz (rzo1) wrote : AlsaInfo.txt

apport information

Revision history for this message
rz (rzo1) wrote : CRDA.txt

apport information

Revision history for this message
rz (rzo1) wrote : CurrentDmesg.txt

apport information

Revision history for this message
rz (rzo1) wrote : IwConfig.txt

apport information

Revision history for this message
rz (rzo1) wrote : Lspci.txt

apport information

Revision history for this message
rz (rzo1) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
rz (rzo1) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
rz (rzo1) wrote : ProcInterrupts.txt

apport information

Revision history for this message
rz (rzo1) wrote : ProcModules.txt

apport information

Revision history for this message
rz (rzo1) wrote : RfKill.txt

apport information

Revision history for this message
rz (rzo1) wrote : UdevDb.txt

apport information

Revision history for this message
rz (rzo1) wrote : WifiSyslog.txt

apport information

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

It's pretty interesting that "drm/i915: Fix PIPESTATE irq ack on i965/g4x" from series [1] wasn't applied to mainline linux.

[1] https://patchwork.freedesktop.org/series/44589/#rev2

Revision history for this message
rz (rzo1) wrote :

Hi @kaihengfeng,

it is the same with the latest mainline kernel.

I attached the dmesg output below.

description: updated
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Intel

Revision history for this message
rz (rzo1) wrote :

I filled an upstream bug report, reference: https://bugs.freedesktop.org/show_bug.cgi?id=111495

Revision history for this message
Linuxium (linuxium.com.au) wrote :

Since commit ca876c7483b6 ("gpiolib-acpi: make sure we trigger edge events at least once on boot") in the Linux mainline v4.18 kernel (and also in stable v4.14.68 as commit fbb37b72489d) the Linux kernel now calls _AEI edge handlers at boot.

Unfortunately the MINIX Neo Z83-4 mini PC has a DSDT bug where some copy and pasted code for dealing with Micro USB-B connector host/device role switching messes with the DDC data pin from the HDMI connector (switching it to GPIO mode) breaking HDMI support.

For Ubuntu Bionic the mainline kernel change "gpiolib-acpi: make sure we trigger edge events at least once on boot" is included in the Ubuntu-4.15.0-56.61 tag as commit 4ea03f3e93f8 and released in the 4.15.0-58.64 linux package.

Starting with the 4.15.0-58.64 linux package and subsequent linux packages including linux-hwe (4.18 and now 5.0 based) and linux-hwe-edge (5.0 and now 5.2 based) packages Ubuntu fails to boot
with working HDMI on MINIX Neo Z83-4 devices.

To fix this a proposed patch has already been submitted to the mainline kernel linux-gpio team that disables the running of _AEI edge event handlers at boot using a DMI based blacklist with the initial version of this blacklist contains the MINIX Neo Z83-4.

This patch is currently under review. However once accepted and mainlined (and incorporated into stable) it would be appreciated if it can be backported to Ubuntu.

Revision history for this message
Linuxium (linuxium.com.au) wrote :

This issue has been fixed in the linux-generic 4.15.0-66.75 and linux-generic-hwe-18.04 5.0.0-32.34~18.04.2 kernels.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.