https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c1 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|X.Org |X.Org Version|Final |Factory InfoProvider| |estellnb@gmail.com AssignedTo|mhopf@novell.com |bnc-team-xorg-bugs@forge.pr | |ovo.novell.com Product|openSUSE 11.3 |openSUSE 11.4 Target Milestone|--- |Factory --- Comment #1 from Matthias Hopf 2010-12-20 11:44:30 UTC --- I doubt that the backtrace patch is the reason for the hang (because the script obviously finished), but you never know. Also, this seems to be either about the X11:XOrg repo, or the upcoming 11.4. Can you please - on a system with a hanging X - call /usr/bin/xorg-backtrace `pidof X` >/tmp/backtrace *manually* (use pidof Xorg if the script fails) and attach /tmp/backtrace? That way we can detect whether X is still stuck doing the backtrace, or rather in some other area. As the backtrace is only written out to the log *after* the backtrace script is completely finished, this is much more likely the case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c2 --- Comment #2 from Elmar Stellnberger 2010-12-22 10:56:52 UTC --- Created an attachment (id=405959) --> (http://bugzilla.novell.com/attachment.cgi?id=405959) backtrace of xorg hangup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c4 Elmar Stellnberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|estellnb@gmail.com | --- Comment #4 from Elmar Stellnberger 2010-12-22 10:58:22 UTC --- . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c5 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P4 - Low Status|NEW |ASSIGNED --- Comment #5 from Matthias Hopf 2010-12-27 16:56:53 UTC --- As assumed this indicates not a hang in the backtrace generator, but rather a LiveLock in DDC2Read and below. I must admit though, I do not understand why the Xserver can get into this codepath given that it already received a segfault. I guess we'll have to look at the mi code about "EQ overflowing.". Not a high priority, though, as the main culprit is the radeon driver in any case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=660166 https://bugzilla.novell.com/show_bug.cgi?id=660166#c7 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|UPSTREAM |FIXED --- Comment #7 from Matthias Hopf 2011-02-15 10:31:21 UTC --- It looks like the server potentially livelocks in fork() - though I'm completely baffled how this can happen (fork() is allowed in signal handlers, and doesn't allocate memory). We're dropping the patch for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.