Summary: | HD 7450, R9-270, GPU locked when testing glmark2 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jack <zduo006> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | julien.isorce |
Version: | 11.2 | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jack
2016-05-24 12:03:53 UTC
Did this also happen with older versions of Mesa and/or the kernel? (In reply to Michel Dänzer from comment #1) > Did this also happen with older versions of Mesa and/or the kernel? I've done the test with Mesa 10.3.0 (xorg-server-1.16,libdrm-2.56) and kernel-3.14, the GPU lockup does not occur. I've also tried with Mesa 10.3.0 and kernel-4.4, the GPU lockup still not occurs. So It looks like it have a relationship with the mesa. Can you bisect Mesa? (In reply to Michel Dänzer from comment #3) > Can you bisect Mesa? I guess I may be to have a try, but not in the last few days as it will cost a lot of time. Are there any other reasons cause this problem? Thank you very much for your reply,Could you give me some advice or anything else about it? So after two days of testing, I found this bug is still present in mesa-11.1.2. The GPU lockup does not occur after i tested several times with 11.0.2 on my R9 270/HD 5450/HD 7450, but locked up on E6760. 11.1.2 or 11.2.0 + kernel-4.4 = lockup (HD7450,5450,r9-270) 11.0.2 + kernel-4.4 = No problems! That looks more like some patches from commit 51e0b06d9916e126060c0d218de1aaa4e5a4ce26(11.0.2) to commit 7bcd827806b0816d61122ba3d37dd40178d96d98(11.1.2) introduced this bug and triggered by 'glmark2 -b grid'. I want to use 'format-patch' to pick the patches from 11.0.2 to 11.1.2, can anyone provide a classification of the patches or some critical patches to me to locate. I don't have a in-depth understanding of the Mesa. Furthermore, I'll try the latest Mesa for some times and report back if I either get a gpu lockup, or don't. git bisect makes this a lot easier. If you don't know how to use it yet, search for "git bisect howto". Always use VRAM for PIPE_USAGE_STREAM buffers, the GPU lockup does not occur. Does setting the environment variable R600_DEBUG=nowc for the glmark2 process avoid the problem? I'll try. Is this still and issue for you on a more recent software stack? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1232. |
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.