xorg-server-1.8.1 foss ati driver gives segmentation fault.

dufeu · l33t Joined: 30 Aug 2002 Posts: 924 Location: US-FL-EST

I upgraded from xorg-server-1.8.0 to xorg-server-1.8.1, reinstalled xf86-video-ati and I now get segmentation faults when I start kde4:

donmartio · Apprentice Joined: 11 Dec 2004 Posts: 258

I got the same Problem here. Downgraded to xorg-server-1.8.0.
Then everything got worse. xorg eats up one cpu and nothing works. I can't even kill X from
a remote console.

Now i downgraded to xorg-server-1.7.7.
I suspect it has something to do with hal and udev.
I compiled xorg-server without hal use flag but i have a lot off other stuff
with the hal use flag so i decided to leave it there.

Do i have to remove hal completely?

Or is this again an ati issue?
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

asturm · Posted: Wed May 19, 2010 9:10 am Post subject:

You didn't forget to rebuild x11-drivers/* after downgrading?

Absolutely no problem here (well, no additional ones) with 1.8.1 here (udev, xf86-video-intel). Running hal in addition doesn't affect X in any way.

Unmask xf86-video-ati-9999 and see if it is already fixed there.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

donmartio · Apprentice Joined: 11 Dec 2004 Posts: 258

Thanks for the reply. Well as i experiences few minutes ago this may is no ati-xorg-hal-udev problem.
After downgrading to xorg-server-1.7.7 i had the same problem when the screen-saver starts.

So there mus be something else since yesterday, which screws up my system.

I'l check it later.
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

donmartio · Apprentice Joined: 11 Dec 2004 Posts: 258

Well one point could be that i forget to comment this out after downgrading:

#Section "InputDevice"
# Identifier "Keyboard1"
# Driver "evdev"
## MatchIsKeyboard "on"
# Option "xkblayout" "de"
# Option "xkbvariant" "nodeadkeys"
#EndSection
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

ArKay · n00b Joined: 30 Nov 2003 Posts: 61

Same segfault here with layman ati git drivers. Went back to 1.8.0 which is stable.

Anon-E-moose · Posted: Wed May 19, 2010 11:44 am Post subject:

donmartio · Apprentice Joined: 11 Dec 2004 Posts: 258

Yep, nvidia works on my home machine too.
But here at work my Box has some kurious behaviour.

I recompiled everything like libdrm, libX-Stuff, xorg-server, xorg-drivers, mesa and so on.
After the reboot it needs 6 minutes to boot the machine.
2 Keyboards where found (which made it impossible to login, getting every character twice).

After a second reboot (the last one) everything seems ok so far.
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

dufeu · l33t Joined: 30 Aug 2002 Posts: 924 Location: US-FL-EST

A little bit of additional information:

I'm using the open source radeon driver:

frostschutz · Advocate Joined: 22 Feb 2005 Posts: 2972 Location: Germany

can't comment on the open source drivers, as they don't support my card, but the binary drivers work fine with xorg 1.8.1 and kernel 2.6.34 - if you apply the patches from bugs.gentoo.org

so if it crashes for you, it should be something in the open source driver

The Unabeefer · n00b Joined: 23 Dec 2008 Posts: 60 Location: Chicago, IL

Same here with the open source ati drivers. Fine on my home comp with nvidia card, but the laptop with ati crashes.

I found the crash by trying to type "Mr." into a register in KMyMoney. 1.8.0 I can do it, but ver 1.8.1 I never make it to the "r" before it kills the whole deal. I have been using that as a test to see if/when it gets fixed.

Still did it, even after upgrading to 1.8.1-r1.
_________________
I am a flying cow... worship me or DIE!!!

...and there he was, reigning supreme at number two...
The One... The Only... The Unabeefer

asturm · Posted: Thu May 20, 2010 12:23 pm Post subject:

Did you try the xf86-video-ati-9999 ebuild yet? Also, which kernel version are you on?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

codestation · Posted: Thu May 20, 2010 4:09 pm Post subject:

Using xorg-server-1.8.1 and xf86-video-ati-9999 (last updated 2 weeks ago) and no problems on my end. So whatever bug it had is fixed now but no in the portage tree yet.
_________________
Just feel the code...

asturm · Posted: Thu May 20, 2010 4:19 pm Post subject:

That's because 6.13 is still the latest upstream release. So, either only specific setups are affected or there has been a fix between release of 6.13 and two weeks ago: http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/log/

So, all those who want to keep running xorg-server-1.8.1 should try this:

wrc1944 · Posted: Fri May 21, 2010 7:17 pm Post subject:

genstorm & codestation,
If we go with the 9999 xorg-server, do we need to rebuild ALL xorg/x11 packages, or just the drivers we use?

BTW, I'm having this problem on 2.6.34-rc4 vanilla, 2.6.34 Final patched with bfs318, and 2.6.34-ck1.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p20230304
kernel-6.2.2 USE=experimental python3_11

asturm · Posted: Fri May 21, 2010 7:33 pm Post subject:

I didn't advocate taking the live xorg-server route - just upgrading the ati driver to 9999. xorg-server-9999 is already on the 1.9 branch, numerous additional -9999 dependencies might be needed which isn't reflected by the ebuild.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

wrc1944 · Posted: Fri May 21, 2010 9:49 pm Post subject:

Sorry- I misunderstood. I was preoccupied with xorg-server-1.8.1-r1 and went into a brain-lock. :roll:

So, stay at xorg-server-1.8.1-r1, and update to xf86-video-ati 9999 is the correct procedure? Do we need to do the same with evdev, mouse, keyboard, or any other driver currently installed, or jusy only do the ati driver?

EDIT: genstorm- Just emerged ati 9999 (and it pulled in libdrm 9999), and has this message:

wrc1944 · Posted: Fri May 21, 2010 11:53 pm Post subject:

OK- went ahead and just did the xf86-video-ati 9999 update, and rebooted OK- kde and X seemed normal.
However, minimizing konsole, and then restoring konsole still immediately crashes X back to kdm screen, so apparently the xf86-video-ati 9999 driver doesn't fix my problem. Same deal with dolphin- clicking on the minimized "dolphin" button in the task manager tray immediately crashes X. I would expect other apps will also crash X, as before.

_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p20230304
kernel-6.2.2 USE=experimental python3_11

asturm · Posted: Sat May 22, 2010 12:26 am Post subject:

That's very unfortunate. Seems you got xf86-video-ati right under heavy development in contrast to codestation two weeks ago. It could also just be in a temporarily broken state, so I would watch out for the next few commits which could already solve the problem.

Or you ati users now go bugfix hunting for the one commit that made it working for codestation.

Me, I'm also not using latest xf86-video-intel-9999 because nothing worked. Instead, I'm using a quickpkg version from some weeks ago. If your systems are similar enough, you could also try and exchange those.

@wrc1944: The libdrm message is just a warning, breakage could happen when not rebuilding mesa and xorg-server, but their -9999 builds are not strictly needed.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

The Unabeefer · n00b Joined: 23 Dec 2008 Posts: 60 Location: Chicago, IL

wrc1944 · Posted: Sat May 22, 2010 12:30 pm Post subject:

Here's something interesting on this problem:
When booted to xfce4, I can open the same kde apps that crash X by clicking to minimize/maximize from the system tray button as mentioned above WITHOUT crashing X. They all work normally.

When booted to kde, any kde app will crash X when trying to restore (maximize) the window from the sys tray.

I'm thinking this isn't really an X problem per se, but a kde/qt problem. I think I read somewhere on either the Arch or Gentoo forums that compositing might be the problem- I'll try booting back to kde and disabling it and see if the problem persists. Don't know why I didn't try that before.

EDIT: OK!

Disabled compositing and now X crashes no longer occur. Simple as that- obviously compositing wasn't enabled in xfce4. Guss I'll go back to the ~arch libdrm and xf86-video-ati drivers, and wait for the normal ~arch updates instead of keeping the 9999 versions and the x11 overlay.

Can anyone give more details as to what the actual problem(s) are with compositing causing X crashes? I'd like to keep an eye on the driver/qt/kde commits and see if I can spot the one that fixes this problem.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p20230304
kernel-6.2.2 USE=experimental python3_11

asturm · Posted: Sat May 22, 2010 12:53 pm Post subject:

I believe it wouldn't work with any kind of compositing, before blaming KDE/Qt someone should check ati drivers' behavior with e.g. compiz. Especially since kwin compositing works well with other GPUs.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

wrc1944 · Posted: Sat May 22, 2010 1:59 pm Post subject:

Here's a weird addendum:
The same X crash problem occurs on Arch Linux testing with libdrm-2.4.20-2 and ati-6.13.0 + compositing, but does NOT occur on Mandriva Cooker with compositing and the same version ati driver and libdrm. Mandriva has a patch that fixes it?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p20230304
kernel-6.2.2 USE=experimental python3_11

asturm · Posted: Sat May 22, 2010 2:09 pm Post subject:

same kernel version each?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

wrc1944 · Posted: Sat May 22, 2010 4:00 pm Post subject:

Mandriva Cooker is at 2.6.33.4-desktop-1mnb, Gentoo is with 2.6.34-rc4 vanilla, 2.6.34 Final patched with bfs318, and 2.6.34-ck1, mentioned above, and if I recall correctly, Arch is with various 2.6.33 versions.

On Arch, I'm running their testing/extras/core repos, and generally don't build kernels- just use theirs, and they remove the previous version. I'll check next time I boot Arch, but on Gentoo the kernels since various 2.6.33 versions and when this X problem begin didn't seem to make a difference.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-12.2.1_p20230304
kernel-6.2.2 USE=experimental python3_11