Bug 42172
Summary: | WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:267 radeon_fence_wait+0x39f/0x3d0() | ||
---|---|---|---|
Product: | Drivers | Reporter: | nissarin |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alexdeucher, niels_ole |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.1-rc3 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
nissarin
2011-09-01 15:35:49 UTC
This might be the same as bug 42162, which I bisected. You could try if commit b03e7495a862b028294f59fc87286d6d78ee7fa1 is the first bad commit... OK, after some "extensive" testing (as in glxgears x 20, duh) b03e7495a862b028294f59fc87286d6d78ee7fa1 "crashed" near 30 minute mark. Currently I'm running 5f66d2b58ca879e70740c82422354144845d6dd3, lets see what happens. As a side note, I've noticed you are also using Gigabyte mobo... I might be oversensitive here but I encountered some strange bugs before, bugs which can be annoying yet I didn't saw many ppl reporting it. More than 8 hours have passed without a single glitch (same as before.. glxgears, web browser, wesnoth, etc.) so yeah, it appears that b03e7495a862b028294f59fc87286d6d78ee7fa1 is most likely the cause. Yes, it seems to be the same issue. Currently I'm testing the patch, I'll notify you later if it worked for me. |