[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

2017-05-16 Thread Thomas Nilefalk
Here's a link to my report of this to Freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=100992. ** Bug watch added: freedesktop.org Bugzilla #100992 https://bugs.freedesktop.org/show_bug.cgi?id=100992 -- You received this bug notification because you are a member of Kernel Package

[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

2017-05-16 Thread Thomas Nilefalk
This was actually on Elementary OS, but I've tried with a 4.2 kernel where the problem does not exist. I've now also tries 4.12.0-041200rc1 and this input hang does not occur. Booting with this kernel does render my WiFi inoperable, though. I suppose that might happen when trying non-offical kerne

[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

2017-05-10 Thread Thomas Nilefalk
Here's a partial dmesg log from a locked screen to the hang with drm:debug=0xe. ** Attachment added: "dmesg_drm_debug.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689651/+attachment/4874740/+files/dmesg_drm_debug.txt -- You received this bug notification because you are a membe

[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

2017-05-09 Thread Thomas Nilefalk
Don't know if the stack trace was actually attached: [ 2205.056641] [ cut here ] [ 2205.056675] WARNING: CPU: 1 PID: 1240 at /build/linux-FyIZxz/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b5/0x1c0 [drm]() [ 2205.056677] vblank wait timed out on crtc

[Kernel-packages] [Bug 1689651] [NEW] vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

2017-05-09 Thread Thomas Nilefalk
Public bug reported: After a screen lock, the screen hangs, with the attached stack dump in dmesg. I've seen multiple bug reports with similar effect, but the workaround has been "video=SVIDEO-1:d" as boot parameters, but this does not affect my case. Also, the other reports, such as https://bugs