Created attachment 15083 [details] xorg-logfile with crash Hi Today i updated the radeonhd to the latest version and immediately notices that starting urxvt (rxvt-unicode http://software.schmorp.de/pkg/rxvt-unicode.html ) with -depth 32 or URxvt*depth: 32 in .Xdefaults results in a SIG11 (at least i read that from the attached log) to the xserver
Created attachment 15084 [details] xorg.conf
Michael bisected: There are only 'skip'ped commit left to test. The first bad commit could be any of: aa7037a7418869da702bd2429b59fb51c9ee6e42 c9ccc4c474af39b583073ea083a61a7b0f711ad3 5596d06da56a299a42818a63ec15b72393703861 dfe3604858d8792a5d34ac6324baced24274135e 153331e806eedff5f73ccb212a7d68d0b691753d e5dddbc2f73bccc66a5ff00a2afb6e8a7ffa93e5 478bda793b7101834ce58bbe37f03a3ccf5036a4 6742f79e8e77add4d62893c1a84908c6c4a5d621 56a264f86762030bb4173b6fc0515918b0e3fc5e 807e525a277668b3006afb36596a9f89dad7ca48 8f499c3879cff399ec40db2403a0bf5626f13c03 fd6a7abfc2dce560092791706393ca073090e995 2e1f55b00d101274bebc51d7ce3a27d54f92d658 42d3201bb7dcfe2ec1755976641e0260f5eb4e91 52f04a7f8ff43fe79c140ba7d17d18bb78cdb1af We cannot bisect more! So the bug was introduced somewhere in there.
I get this with the radeon driver (7500 M7 card), but only when urxvt quits. The SEGV occurs when the gl driver tries to free something, so it seems to be a double free, and in the extension rather than in the driver.
(In reply to comment #3) > I get this with the radeon driver (7500 M7 card), but only when urxvt quits. > > The SEGV occurs when the gl driver tries to free something, so it seems to be a > double free, and in the extension rather than in the driver. This sounds like https://bugzilla.novell.com/show_bug.cgi?id=303952 Try adding Load "dri" in the "Module" section of your xorg.conf. Even if there's no 3d support available. If there is, but you do not want to use it, move the dri kernel module somewhere where it's not found. Michael, could you try this as well? If urxvt tries to do something with OpenGL that could be the case. Wonder why this has something to do with the radeonhd version, though.
well my log says (II) "dri" will be loaded by default.
Fair enough. So different issue.
noticed today that the crash only occurs when i comment out Option "Accelmethod" "xaa" in the configfile if it is enabled, no crsh occurs. so it seems that something in the setup of the default path (which is also xaa) is broken or at least doesn't behave the same way as the setting of the config-option does
(In reply to comment #7) > noticed today that the crash only occurs when i comment out > Option "Accelmethod" "xaa" > in the configfile > if it is enabled, no crsh occurs. > so it seems that something in the setup of the default path (which is also xaa) > is broken or at least doesn't behave the same way as the setting of the > config-option does That helps a lot - I'll look into that!
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Closing due to lack of response. Please reopen and move to the Driver/Radeon component if this issue persists with xf86-video-ati
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.