| Summary: | r600g : lock in desktop display durring piglit test | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | XoD <xoddark> |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
dmesg
Xorg.log syslog_radeon possible fix |
||
|
Description
XoD
2011-06-15 11:53:21 UTC
which piglit test(s) cause this? Also what hardware are you using? Can you attach your dmesg output? Created attachment 48012 [details]
dmesg
Created attachment 48013 [details]
Xorg.log
Created attachment 48250 [details]
syslog_radeon
I add syslog file were only lines with radeon are keep.
I have launch 2 times piglit test, each time we can see some drm errors.
Created attachment 48291 [details] [review] possible fix Does this patch help? (In reply to comment #6) > Created an attachment (id=48291) [details] > possible fix > > Does this patch help? this path doen't fix the problem sorry. but i have note that I have the problem with kernel 3.6.39.1, but I haven't the problem with kernel 3.0-rc4. It seem to be fixed by kernel 3.0. Peraps a modification in drm need to be merged in 2.6.39 branch. (In reply to comment #7) > > It seem to be fixed by kernel 3.0. > Peraps a modification in drm need to be merged in 2.6.39 branch. Can you bisect to see what patch fixed the issue? (In reply to comment #8) > (In reply to comment #7) > > > > It seem to be fixed by kernel 3.0. > > Peraps a modification in drm need to be merged in 2.6.39 branch. > > Can you bisect to see what patch fixed the issue? Peraps, but i probably need help. I don't know how bissect only drm patch, because bissect all patch on kernel 3.0 seems to be very long. And I need to find how package kernel without rebuild all. For now when i build a kernel, i launch a command who make the build and the packaging. But this command rebuild all each time. I have finish the bisect of kernel 3.0 : the submit who fix lock i encounter is : 11b0a5b89adbfaf4e7d31f2482f49471dd983692 is the first good commit commit 11b0a5b89adbfaf4e7d31f2482f49471dd983692 Author: Alex Deucher <alexdeucher@gmail.com> Date: Thu Jun 16 10:06:17 2011 -0400 drm/radeon/kms: set DP link config properly for DP bridges DP clock and lanes were not set properly for DP bridges. Signed-off-by: Alex Deucher <alexdeucher@gmail.com> Signed-off-by: Dave Airlie <airlied@redhat.com> :040000 040000 f6ead6b480453a9e2d2c1b60bcfe69df0c26ee22 7f73649711cf4c5133845dd98fa6c53af690dce2 M drivers peraps it have sense to push this patch in branch 2.6.39 At the beginning of bisect, display lock during the first piglit test. But in a second part, display lock only in the second test, when chromium is launch (with some opened page). Unfortunately that patch is not related to your chip at all (there are no redwoods with dp bridge chips). I think it's a false positive. (In reply to comment #7) > It seem to be fixed by kernel 3.0. Closing this bug. |
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.