Bug 101621
Summary: | Thinkpad X60s freezes | ||
---|---|---|---|
Product: | Drivers | Reporter: | Robert Alessi (alessi) |
Component: | Video(DRI - Intel) | Assignee: | intel-gfx-bugs (intel-gfx-bugs) |
Status: | RESOLVED CODE_FIX | ||
Severity: | high | CC: | alessi, intel-gfx-bugs, sjensen, zwpwjwtz |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 4.1.2 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
dmesg output
system logs Kernel crash at shutdown dmesg output system logs |
I enabled drm.debug=0x06 in GRUB. Also find attached the system logs at the moment my laptop last froze. Created attachment 182851 [details]
system logs
Created attachment 183591 [details]
Kernel crash at shutdown
The messages I get when kernel crashes at shutdown. Hope this helps.
Created attachment 183621 [details]
dmesg output
dmesg output
Created attachment 183631 [details]
system logs
system logs
Also using X60s. Using kernel 4.0.8 and 4.1.2 provided by Fedora. I found "Failed to find cpu0 device mode" message as well. However the freezing state does not appear. So I guess it may be due to linux-libre kernel. I think that the "Failed to find cpu0 device mode" message is unrelated to this particular issue. However, I mentioned it here because kernels older than 4.1 (namely 4.0.7) did not display it. Having said that, I am now running 4.1.3 for almost a week, and my X60s does not freezes any longer. "does not freeze". Sorry. Thanks for the follow-up. Closing. Please file any new bug reports at the freedesktop.org bugzilla [1]. Thank you. [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel |
Created attachment 182831 [details] dmesg output I noticed that my X60s freezes with linux-libre kernel (Parabola) > 4.0.7. Up to 4.0.7, everything was fine. From 4.1.1, I noticed the following: - during boot process, I have this: "Failed to find cpu0 device mode" - then after an hour or so, the laptop completely freezes. I am left with a snapshot of my desktop, and the only thing I can do is press and hold the power button. This is still present in 4.1.2. I am not sure that this malfunctioning is related to the graphics. Please find attached kernel logs at boot (dmesg output).