Summary: | Tonga Oopses with uvd + agd5f drm-next-4.3-wip | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Andy Furniss <adf.lists> | ||||||||
Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | medium | ||||||||||
Version: | DRI git | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Created attachment 117731 [details]
Oops 2 long
Created attachment 117732 [details]
Oops 3 - current tree
Not reproducible with current kernels. |
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.
Created attachment 117730 [details] Oops 1 Tried the newly updated agd5f drm-next-4.3-wip today and got some oopses with uvd. These are provoked by repeatedly starting a vid with mpplayer - a known issue, but the change for me on Tonga is getting the Oopses. On other kernels amdgpu/amd-staging/drm-fixes the same test would provoke a ring 9 lock (rarely ring 0) and a failed reset, which at least would leave me alive enough to get a VT. I notice GPU stall detection has now been disabled - but testing various 4.3-wips over some weeks I have never got one anyway. Doing something like this test or running valley would just lock the display and log nothing. SysRq worked OK as it still does - just now I get some logging (though not for the one Unigine Valley lock I just provoked). I am now running mesa/drm mesa/mesa Git Xorg with DRI3 enabled. While testing I noticed the tree got another update - retested and still get the same. The first 2 are from the older tree, the second long as secondary Oopses were provoked. The third is current.