[Bug 109209] New: i915 module results in total lockups without any dmesg trace on a NP900X5N Kaby Lake machine

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 2 12:34:20 UTC 2019


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

            Bug ID: 109209
           Summary: i915 module results in total lockups without any dmesg
                    trace on a NP900X5N Kaby Lake machine
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jv1 at home.nl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 142940
  --> https://bugs.freedesktop.org/attachment.cgi?id=142940&action=edit
dmesg

I installed various Kali linux versions up to Linux 4.20.0-rc7 (downloaded,
compiled and installed) on a Samsung NP900X5N laptop and have an issue with the
driver after loading.

My configuration:
- i7 7500
- 16 gb / 256 gb ssd
- nvidia 940MX (for 3D graphics)

Shortly after loading the module the screen goes black (af if screen saver) and
stays black. I tried to fix it myself.and 'studied' the behaviour for about 20
hours, I think it is a bug in the i915 module itself.

A summary of the test I performed.

- I tried several versions and distributions. They all result in the same
behavior. Screen goes black.I do not see any logging in the  logs. I enabled
ssh and the machine is unresponsive after the screen going black. The more
tests I do (rebooting via holding power key) the sooner the screen goes black.
I wonder if the gpu gets too hot locally. Btw, the processor is not hot as the
fan stays off.

- When I disable the driver in grub or in the modprobe.d dir I do not have
experience any hangs.

- With Windows 10 the machine does not results in lockups (kept the machine on
for more than 24 hours).

I added drm.debug=14 module parameter, attach /var/log/messages file from boot
to desktop to the bug. 

When the machines hangs, no ssh is possible. Copied the file afterwards. 
The syslog is attached

-- 
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/20190102/3261d4de/attachment.html>


More information about the intel-gfx-bugs mailing list