Bug 1762313 - kernel 5.3.5-200.fc30 boot leaves monitor dead
Summary: kernel 5.3.5-200.fc30 boot leaves monitor dead
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1763374 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 13:50 UTC by Don Swaner
Modified: 2019-11-05 11:13 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-05 11:13:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel log (91.91 KB, text/plain)
2019-10-16 13:50 UTC, Don Swaner
no flags Details

Description Don Swaner 2019-10-16 13:50:30 UTC
Created attachment 1626498 [details]
kernel log

1. Please describe the problem:
When kernel 5.3.5-200-fc30 is booted, the monitor will not wake up. Moving
mouse, pressing ESC, pressing Ctl-Alt-F3 all leave monitor dead.

2. What is the Version-Release number of the kernel:
kernel-core-5.3.5-200.fc30

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
My system has been functioning normally, up until kernel-core-5.3.5-200.fc30.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Rebooting (5.3.5-200.fc30) results in same problem.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Unknown.  When I followed above instructions, I get error message:

Importing GPG key 0xCFC659B9:
 Userid     : "Fedora (30) <fedora-30-primary>"
 Fingerprint: F1D8 EC98 F241 AAF2 0DF6 9420 EF3C 111F CFC6 59B9
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-30-x86_64
Is this ok [y/N]: y
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for kernel-5.4.0-0.rc2.git2.1.fc32.x86_64.rpm is not installed. Failing package is: kernel-5.4.0-0.rc2.git2.1.fc32.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-30-x86_64
Public key for kernel-core-5.4.0-0.rc2.git2.1.fc32.x86_64.rpm is not installed. Failing package is: kernel-core-5.4.0-0.rc2.git2.1.fc32.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-30-x86_64
Public key for kernel-modules-5.4.0-0.rc2.git2.1.fc32.x86_64.rpm is not installed. Failing package is:
kernel-modules-5.4.0-0.rc2.git2.1.fc32.x86_64

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Masami Ichikawa 2019-10-16 15:04:16 UTC
It looks as if I have same issue. My bug report is https://bugzilla.redhat.com/show_bug.cgi?id=1758831 .
Also I have reported the issue to upstream. This issue has been fixed in drm-tip tree[1] and patch was sent to stable mailing list[2].


1:https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_bios.c?id=41e35ffb380bde1379e4030bb5b2ac824d5139cf
2:https://www.spinics.net/lists/stable/msg334633.html

Comment 2 Laura Abbott 2019-10-16 17:10:00 UTC
Once the patch hits Linus' tree we can see about bringing it in.

Comment 3 Patrick Johnston 2019-10-19 13:53:27 UTC
*** Bug 1763374 has been marked as a duplicate of this bug. ***

Comment 4 dc.hart 2019-10-26 17:53:11 UTC
This problem persists through 5.3.7-200. Moreover, I installed kernel-core-5.4.0-0.rc4.git2.1.fc32.x86_64 from rawhide. No joy. Making matters worse there are no log prints from attempts to boot the nonworking kernels. The boot process freezes everything right after the kernel is selected.

Suggestions? Questions? I concede that I do not know what I do not know.

BTW, anyone else with the problem should change the value in dnf.conf from 3 to, say, 5 so that you retain old kernels.

Comment 5 Don Swaner 2019-10-26 19:59:18 UTC
You also may want to add a /etc/dnf/protected.d member containing the latest working kernel package names (5.2.18-200).  I tried booting kernel 5.3.7 with "acpi=off" (won't boot) and with "noacpi" (boots, but won't wake).

Comment 6 Masami Ichikawa 2019-10-28 01:30:56 UTC
kernel 5.3.8 will have patch (https://www.spinics.net/lists/stable/msg337013.html) so I hope the fix available in Fedora soon.

Comment 7 Don Swaner 2019-10-29 19:25:36 UTC
Adding "nomodeset" to 5.3.7-200 kernel parms allows me to run with 800x600 resolution.  However, after logging out of gnome desktop, the monitor will not wake.  I can also run an F31 Live USB in basic graphics mode only.

Comment 8 Don Swaner 2019-11-05 11:13:20 UTC
kernel 5.3.8-200.fc30.x86_64 works for me.


Note You need to log in before you can comment on or make changes to this bug.