Bugzilla – Bug 136677
radeon: X dies of SIGFPE
Last modified: 2008-04-19 06:06:47 UTC
In radeon_driver.c: 5530 /* FIXME: When we move to dynamic allocation of back and depth 5531 * buffers, we will want to revisit the following check for 3 5532 * times the virtual size of the screen below. 5533 */ 5534 int width_bytes = (pScrn->displayWidth * 5535 info->CurrentLayout.pixel_bytes); 5536 int maxy = info->FbMapSize / width_bytes; pScrn->displayWidth is zero, thus you'll get a div by 0. This appears to be dependent on the config, this happens with the one generated by SaX2, but not with a hand-crafted one derived from X -configure.
Created attachment 59701 [details] X config generated by SaX2
Hmm ... could you attach the hand-crafted as well? SaX2 seems to create a dualhead MergedFB configuration for 4 monitors, which looks correct to me.
Created attachment 59704 [details] hand-crafted X config
Your hand-crafted one seems to be a non mergedfb configuration. So you connected your 2 monitors to different boards, right?
Boards = cards? Yes.
Yes, boards=cards. Ok. This makes sense to me. So I think we see a MergedFB problem here. :-( I would like to know, whether it only occurs with two boards, since I didn't see it yet with one board active (at least not on i386/x86_64).
Removing Screen "Screen[1]" RightOf "Screen[0]" in the SaX2 generated config and connecting the two monitors to the first card should do the trick.
Is there a way to tell sax not to enable the MergedFB option?
Could you answer my question first?
Do you mean comment #7? It does not help. While the server does not crash any more, it doesn't display anything either.
Yes, comment #7. Thanks. I think you could use the Radeon_DualHead profile instead. sax2 -r -b /usr/share/sax/profile/Radeon_DualHead or something like this.
Doesn't help either. (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled (II) RADEON(0): MergedFB mode forced on. (WW) RADEON(2): Failed to detect secondary monitor, MergedFB/Clone mode disabled (II) RADEON(2): MergedFB mode forced on.
I hoped that SaX2 would create a config similar to your handcrafted one, but this seems to be wrong. Anyway, Marcus knows more about this multihead config stuff than I do.
I suggest to check this again with openSUSE >= 10.2 once the X Server works on openSUSE again.
(In reply to comment #14) > I suggest to check this again with openSUSE >= 10.2 once the X Server works > on openSUSE again. Not sure if we're already prepared for this though. But it might be worth a try.
Andreas, did you check this with openSUSE 10.2 again?
SaX does not work at all.
Andreas, any improvements with STABLE or is X.Org still broken on STABLE-IA64?
Stefan, is this the randr 1.2 enabled driver?
No. BTW, RANDR 1.2 for radeon driver still lives in a separate git branch.
SaX2 is not able to detect the monitor and only uses 800x600. Also I don't see a way to make it use both graphics cards.
There are still instances where something gets devided by the screen width. I don't see any sanity checks in the code so if this is gone it's gone because some upper layer code takes care of this. Andreas, would you please test this with the config attached in comment #1? I've got a similar machine I think but I'd need to update it first and I'm not set up for this right now.
The config no longer works at all.
Hmm. Could you attach the logfile for this config? Thanks.
Created attachment 138348 [details] Xorg.0.log
JFYI, Matthias. This is a bugreport, which is assigned to Egbert/me or with Egbert/me in CC or reported by Egbert/me.
The radeon driver has been reworked heavily. Andreas, is this bug still an issue? Stefan do you know if this server/driver in question of any relevance for an enterprise product?
Well, SLES10 is based on SUSE LINUX 10.1, so it might be relevant. But it seems the issue only occurs if you configure two seperate ATI gfx cards each one using MergedFB mode ==> 4 heads. For SLES11 we'll switch to the new radeon driver with RANDR >= 1.2 support, which obsoletes MergedFB, so *this* issue will disappear. I suggest to close this bugreport as WONTFIX. I'm not aware of anyone running into this problem than Andreas, and since he's using a valid workaround ... I'm rather sure we can still reproduce this issue on our SLI test machine with two ATI cards - at least on SLES10. But is it really that important? > Andreas, is this bug still an issue? I'm not sure, if Andreas can answer this question easily at the moment. STABLE and X might not be usable at all on IA64 at this time. :-(
I would like to know if this should eventually be fixed for the next SP for SLES10. If not I will close it with WONTFIX.
Looks like there's no need to fix it still for SLES10. ==> WONTFIX