Summary: | [BDW] GPU HANG: ecode 8:0:0x86dffffd, in X [16418], reason: Ring hung, action: reset | ||
---|---|---|---|
Product: | Mesa | Reporter: | ragadinks |
Component: | Drivers/DRI/i965 | Assignee: | ragadinks |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | major | ||
Priority: | medium | CC: | intel-gfx-bugs, ragadinks |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | BDW | i915 features: | GPU hang |
Attachments: |
contents of /sys/class/drm/card0/error
output of /var/log/messages output of dmesg |
Description
ragadinks
2015-11-15 09:48:25 UTC
Please attach dmesg output also Created attachment 119703 [details]
output of /var/log/messages
I am sorry, I did not keep the output of dmesg, but I have saved the relevant part of the log file which might be indentical !?
Today after a reboot I found this in the output of dmesg: [ 30.428099] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)! Not sure if that has got something to do with the bug ? (In reply to ragadinks from comment #3) > Today after a reboot I found this in the output of dmesg: > > [ 30.428099] [drm:gen8_irq_handler] *ERROR* The master control interrupt > lied (SDE)! > > Not sure if that has got something to do with the bug ? It's not relevant here. Created attachment 119728 [details]
output of dmesg
Today it happened again and I was able to save the output of dmesg.
Very often the whole computer freezes and I cannot do nothing anymore except restarting it.
Bug scrub: Assigned to Jani Nikula (In reply to cprigent from comment #6) > Bug scrub: > Assigned to Jani Nikula Why? The fact that I ask questions or make relevant comments on a bug, which I by and large do more than most, does not mean that I would know *anything* about the actual bug behind the report. Here, I merely happened to know that comment #3 is another bug. Hi ragadinks@gmail.com : Can you provide the exact steps in order to reproduce this bug, in QA we have a Lenovo G50-80 with Intel(R) i5-5200U @2.2GHz and Intel HD Graphics 5500, i think that this hardware help us to reproduce this bug once we have the exact steps to reproduce it, as well did you do any extra configuration ? Thanks Sorry, I am just travelling and won't return till the end of this month. I also replaced the buggy kernel with an older one because it was impossible to work like this. Sometimes the problem arised when starting X and sometimes when opening a some program that seemed to put the graphic card under stress as it appeared to me.U will try to reproduce the error when back at home, but right now I don't have the laptop with me. Regards Arno On 1/6/16, bugzilla-daemon@freedesktop.org <bugzilla-daemon@freedesktop.org> wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=92958 > > --- Comment #8 from Humberto Israel Perez Rodriguez > <humberto.i.perez.rodriguez@intel.com> --- > Hi ragadinks@gmail.com : > > Can you provide the exact steps in order to reproduce this bug, in QA we > have a > Lenovo G50-80 with Intel(R) i5-5200U @2.2GHz and Intel HD Graphics 5500, i > think that this hardware help us to reproduce this bug once we have the > exact > steps to reproduce it, as well did you do any extra configuration ? > > Thanks > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. > There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. In parallel, assigning to Mesa product. Kernel: 4.3.0-gentoo001 Platform: Broadwell-U (pci id: 0x1616) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0x00fd2488, with 0x79000002 (3DSTATE_DRAWING_RECTANGLE) as IPEHR. Batch extract (around 0x00fd2488): 0x00fd2454: 0x78080003: 3DSTATE_VERTEX_BUFFERS 0x00fd2458: 0x0800400c: buffer 1: sequential, pitch 12b 0x00fd245c: 0x02a7d000: buffer address 0x00fd2460: 0x00000000: max index 0x00fd2464: 0xffffffff: mbz Bad length 7 in (null), expected 6-6 0x00fd2468: 0x7b000005: 3DPRIMITIVE: fail sequential 0x00fd246c: 0x00000000: vertex count 0x00fd2470: 0x00000003: start vertex 0x00fd2474: 0x000000fe: instance count 0x00fd2478: 0x00000001: start instance 0x00fd247c: 0x00000000: index bias 0x00fd2480: 0x00000000: MI_NOOP 0x00fd2484: 0x79000002: 3DSTATE_DRAWING_RECTANGLE 0x00fd2488: 0x00000000: top left: 0,0 0x00fd248c: 0x00570068: bottom right: 104,87 0x00fd2490: 0x00000000: origin: 0,0 0x00fd2494: 0x782f0000: 3DSTATE_SAMPLER_STATE_POINTERS_PS 0x00fd2498: 0x000018c0: dword 1 Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you. |
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.