[Bug 110193] New: Kernel commit 7769db5883841b03de544a35a71ff528d4131c17 causes a Dell precision 5530 to no longer display a TTY

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 19 10:58:21 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=110193

            Bug ID: 110193
           Summary: Kernel commit 7769db5883841b03de544a35a71ff528d4131c17
                    causes a Dell precision 5530 to no longer display a
                    TTY
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: dcermak at suse.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Yesterday I updated to kernel 5.0.1 (and 5.0.2 and 5.1 rc1, the former two from
openSUSE Tumbleweed and the later from git) and my Dell Precision 5530's
internal display stopped working with these kernels.

The machine boots fine, but at some point during the boot process, the laptop
display turns off and starts flickering (the backlight turns very briefly on
and off again). The system gets up and running, so I can ssh into it, I just
don't see anything on the Laptop display. Please note, I don't boot into X,
just into a tty, so I cannot attach an X.org log.

I have tried the following:

- Attaching an external monitor via HDMI works, i.e. the external monitor turns
on and displays my tty. I can even startx there, but the X server is completely
unresponsive and does not start any applications. The logs are unfortunately
completely normal.

- Booting a 5.0.x kernel with nomodoset works and I get to see the tty on the
laptop display (unsurprisingly X does not start here).

- The system logs show absolutely nothing beside the following lines:
Mar 19 10:28:42 Boreas kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Mar 19 10:28:42 Boreas kernel: iTCO_wdt iTCO_wdt: can't request region for
resource [mem 0x00c5fffc-0x00c5ffff]
Mar 19 10:28:42 Boreas kernel: iTCO_wdt: probe of iTCO_wdt failed with error
-16


This led me to git bisect the kernel between the tags 4.20 and 5.0. I have used
the SUSE .config file and if changes were necessary, I have used the default
values. The result of the bisect is commit
7769db5883841b03de544a35a71ff528d4131c17

Unfortunately, that is part of a big patch chain of the i915 subsystem, so I
cannot easily revert it on top of v5.0.

For reference, I have originally reported this on the opensuse-factory
mailinglist: https://lists.opensuse.org/opensuse-factory/2019-03/msg00222.html


Cheers,

Dan

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190319/bf46bb4a/attachment.html>


More information about the intel-gfx-bugs mailing list