Summary: | [SNB] WARNING: CPU: 1 PID: 1630 at drivers/gpu/drm/i915/intel_uncore.c:224 __gen6_gt_wait_for_fifo+0xb5/0xc0 [i915] | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | samuel.rakitnican | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||
Version: | XOrg git | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | ReadyForDev | ||||||||
i915 platform: | SNB | i915 features: | GEM/Other | ||||||
Attachments: |
|
Description
samuel.rakitnican
2017-08-27 10:29:22 UTC
The GPU died completely, we could do with the logs earlier to this as well. Aug 25 16:25:16 hostname kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. Aug 25 16:25:16 hostname kernel: [drm:__gen6_gt_wait_for_thread_c0 [i915]] *ERROR* GT thread status wait timed out Aug 25 16:25:16 hostname kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. Aug 25 16:25:16 hostname kernel: [drm:__gen6_gt_wait_for_thread_c0 [i915]] *ERROR* GT thread status wait timed out But what caused those?... Created attachment 133813 [details]
journalctl --dmesg
Attached full kernel log for the current boot. Not sure if there is something else there except this two lines which seems the same so not sure what you are looking for.
Jul 28 23:31:10 hostname kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
Jul 28 23:31:10 hostname kernel: [drm:__gen6_gt_wait_for_thread_c0 [i915]] *ERROR* GT thread status wait timed out
Please note that this machine is mostly just sitting at GDM login screen is used mostly as server.
As what happened prior to segfault, I've logged in into GNOME desktop, and opened Vinagre and connected to a local VNC server, and maybe even opened gnome-terminal. This happened few seconds after. I am not sure if it is reproducible with these actions, probably not from my past experience. I was hoping it was preceded by a GPU hang -- but that report still be pending, do you also have the next couple of minutes of dmesg? The attached log at comment 2 is full log, there is nothing after that. Machine is still running. Hello Samuel, any change with latest stable or mainline?? https://www.kernel.org First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. I think this was solved by disabling semaphores: https://bugs.freedesktop.org/show_bug.cgi?id=54226#c264 I can't see the issue anymore on newer kernels. # uname -r 4.15.12-1.el7.elrepo.x86_64 OK, thanks you for fast response. Resolving with this information |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.