Bug 105252 - GPU HANG: ecode 7:0:0x87f57ff8, in navigation application - Baytrail
Summary: GPU HANG: ecode 7:0:0x87f57ff8, in navigation application - Baytrail
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 13.0
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-26 11:02 UTC by James Thomas
Modified: 2018-03-14 23:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Card error (46.40 KB, text/x-log)
2018-02-26 11:02 UTC, James Thomas
Details
dmesg.log (24.60 KB, text/x-log)
2018-02-26 11:03 UTC, James Thomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Thomas 2018-02-26 11:02:47 UTC
Created attachment 137604 [details]
Card error

Anywhere between 1-2 hours of running a driving simulation using a proprietary Qt5 based navigation application we're observing the attached GPU hang.

Kernel: 4.14.19
CPU: Intel(R) Atom(TM) CPU  E3840 (Baytrail)
Other: Weston 1.0.6 (proprietary DRM rendering backend)
       Mesa 13.0.6 (stock i965 driver from this)

The issue wasn't previously seen on our 4.4.x based released, however we were using a mesa 9.x based proprietary user-space driver, and a similar driver in the kernel (though it was essentially a wrapper around i915)

Unfortunately due to the version of Weston we're using we won't be able to easily upgrade mesa from 13.0.6 (it's a binary blob)
Comment 1 James Thomas 2018-02-26 11:03:11 UTC
Created attachment 137605 [details]
dmesg.log
Comment 2 Chris Wilson 2018-02-26 11:13:07 UTC
Ugh, it does look to be an unhappy mesa batch. I think you find yourself caught between a rock and a hard place.
Comment 3 James Thomas 2018-02-26 11:47:26 UTC
(In reply to Chris Wilson from comment #2)
> Ugh, it does look to be an unhappy mesa batch. I think you find yourself
> caught between a rock and a hard place.

Thanks for the quick reply, is there anything I could take a look at here (short of moving forward to mesa 18 and a newer weston)?
Comment 4 Mark Janes 2018-02-26 17:38:46 UTC
James, can you at least test with Mesa 17.2 and 18.0rc4, to see if either of those branches resolves your issue?


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.