Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44198 - [linux] Graphical bug after suspend

Attached to Project: Arch Linux
Opened by martijn (martijn9612) - Sunday, 15 March 2015, 19:14 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 02 October 2017, 20:01 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
I am getting this really wierd graphical bug in arch + i3 when I suspend. All seems well when I open the lid/resume again, until I start doing things again. When my system resumes everthing is as I left it when I closed it, except for instance when I start doing things again the entire screen messes up (immediately after I open the lid nm-applet even disappears from i3status, after that the rest messes up. Maybe because networkmanager is trying to set up it's connections again and display a animation on the icon, I'm fairly sure about that from using nm-applet before). The screen only partially updates and not even in a normal way, only the border or something like that. And when I start doing mode things, like opening another terminal, the screen messes up more. Also upon closing i3 with $mod+shift+e (for some reason the message bar for closing i3 is ALWAYS visible) and clicking the button on the bar, the shell starts spazzing in a wierd way. All the text starts flickering and slowly moving to the right for some reason (sometimes even to the bottom) and wrapping around the screen to re-appear on the left agian.

Also when I do not log in in the shell upon startup and suspend, there is an error message showing: "[drm:hws_unclaimed_reg_detect] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem" (also 100% reproducable)

Additional info:
Sorry for including the entire version file, I have no idea what versions are needed for this.

Steps to reproduce:
The bug is 100% reproducable every time I close the lid/push the off button to suspend/type systemctl suspend.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 02 October 2017, 20:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  OP can no longer reproduce
Comment by martijn (martijn9612) - Sunday, 15 March 2015, 19:20 GMT
Also, forgot to mention, this is on a Thinkpad T450s with integrated graphics(5500) from intel(i5-5300u). I can provide pictures of the screen if requested!
Comment by Mateusz Lemusisk (MRLemux) - Sunday, 15 March 2015, 20:57 GMT
Can you reproduce,what is mentioned in this mailing-list thread:
http://www.spinics.net/lists/intel-gfx/msg60919.html

It seems like upstream is tracking down a similar bug
Comment by martijn (martijn9612) - Sunday, 15 March 2015, 21:47 GMT
I believe that my issues are almost or exactly identical to his issues, except the "stop_ring" error(maybe I did something wrong), I don't have that(maybe that is a different issue, I have no clue). I have my logs here from the dmesg with mmio_debug. Also the kernel logs of closing the lid and opening, I did that two times, idk why but maybe it helps. Also, like the guy in the other mail mentioned, if I run glxgears when closing the lid and opening it again, it just suspends and resumes like normal, with the lid and power button(altough I think that just is equal). I hope this helps!
Comment by Mateusz Lemusisk (MRLemux) - Monday, 16 March 2015, 06:32 GMT
Thanks,
it seems like you have found a new bug in the intel
graphics stack (Due to the nature that the hd graphics 5500 is fairly new)
Could you report it to the freedesktop bugtracker
(it's the intel-gfx subcomponent)
Comment by martijn (martijn9612) - Monday, 16 March 2015, 21:34 GMT
Sure, no problem, will do! I can't seem to find the intel gfx category in the freedesktop bugtracker, where is that exactly?
Comment by mattia (nTia89) - Monday, 02 October 2017, 17:59 GMT
is this issue still valid?
Comment by martijn (martijn9612) - Monday, 02 October 2017, 18:42 GMT
I have no clue if this issue is still valid, I am still using the same laptop, but a completely different install. I'm not experiencing any issues, so I think it could be assumed as resolved?

Loading...