https://bugs.freedesktop.org/show_bug.cgi?id=47160
--- Comment #2 from Johannes Obermayr 2012-03-09
12:30:45 PST ---
Created attachment 58249
--> https://bugs.freedesktop.org/attachment.cgi?id=58249
valgrind output
gdb doesn't provide a backtrace.
Maybe valgrind output helps.
--
Configure
https://bugs.freedesktop.org/show_bug.cgi?id=47162
Bug #: 47162
Summary: Screen went black for seconds, 100% cpu usage on
dri2Throttle/sched_yield
Classification: Unclassified
Product: xorg
Version: 7.4 (2008.09)
Platf
https://bugs.freedesktop.org/show_bug.cgi?id=47160
--- Comment #1 from Alex Deucher 2012-03-09 09:35:56 PST ---
Can you install debugging symbols and get a proper backtrace with gdb
(http://wiki.x.org/wiki/Development/Documentation/ServerDebugging)? Also
please attach your dmesg output.
--
Con
https://bugs.freedesktop.org/show_bug.cgi?id=47160
Johannes Obermayr changed:
What|Removed |Added
Attachment #58244|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=47160
Bug #: 47160
Summary: r600: XServer crash on Fusion system
Classification: Unclassified
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
2012/3/9 Rafał Miłecki :
> W dniu 28 lutego 2012 07:13 użytkownik Rafał Miłecki
> napisał:
>> 2012/2/25 Jonathan Nieder :
>>> Alex Deucher wrote:
>>>
region 0 is always the frame buffer and region 2 is always mmio.
radeontool and avivotool should be cleaned up the same way radeonreg
>>>
W dniu 28 lutego 2012 07:13 użytkownik Rafał Miłecki napisał:
> 2012/2/25 Jonathan Nieder :
>> Alex Deucher wrote:
>>
>>> region 0 is always the frame buffer and region 2 is always mmio.
>>> radeontool and avivotool should be cleaned up the same way radeonreg
>>> is.
>>
>> Thanks, makes perfect se
