registry team mailing list archive

[Bug Watch Updater <123134@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 14 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=11237.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2007-06-11T14:02:55+00:00 Bugzi09-fdo-tormod wrote:

Originally I filed this in Debian, it's the same in Ubuntu.

After logging out from the X session and the server restarts (or resets)
with a couple of mode switching flashes, the virtual consoles are
broken.

Savage Twister, linux 2.6.22rc2, xorg-server 1.3, savage 2.1.2

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/0

------------------------------------------------------------------------
On 2007-06-11T14:26:41+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=10257)
Xorg.0.log after ctrl-alt-backspace

They also get corrupted if quit the session with ctrl-alt-backspace.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/1

------------------------------------------------------------------------
On 2007-06-11T14:28:23+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=10258)
xorg.conf (Debian sid/lenny)

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/2

------------------------------------------------------------------------
On 2007-06-14T12:24:43+00:00 Marc-gasnot wrote:

I have exactly the same problem with a SuperSavage chipset (IBM ThinkPad
T23) and Debian testing since xorg was updated to 7.2. There's no
special need to add my xorg.0.log and xorg.conf because they are quite
identical to those that are already presenred here - unless you really
need it.

My configuration:
SuperSavage, linux 2.6.18, xorg-server 1.3, savage 2.1.2

the drm.ko and savage.ko modules are already broken on 2.6.18 kernel
with xorg above 7.0, but I use a git recompiled version that worked
correctly with 7.1.

Another problem that came with this vesion is that X crashes when a program try to change the screen resolution, like fullscreen games. In this case, the X server is entierly restarted and the virtual consoles are also broken.
I don't know if it is another bug, but it seems to be related anyway.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/3

------------------------------------------------------------------------
On 2007-06-21T23:17:51+00:00 Marc-gasnot wrote:

I'm here for a little correction: I discovered that the X crash when
changing screen resolution doesn't always brake the virtual consoles, so
I think it is really another bug. Sorry  for the flood...

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/4

------------------------------------------------------------------------
On 2007-06-24T06:22:47+00:00 Bugzi09-fdo-tormod wrote:

I think it is related / a consequence that the X server starts up on a
new VT each time (vt7, vt8, vt9, vt10...).

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/5

------------------------------------------------------------------------
On 2007-06-28T14:25:13+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=10494)
gdb session when X server crashes at shutdown

I think the gdb output indicates some stale psav pointers.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/6

------------------------------------------------------------------------
On 2007-06-28T15:11:11+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=10495)
another gdb session

This trace was with NoTrapSignal, which avoided the second segfault
which came when the server aborted. I also printed more variables.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/7

------------------------------------------------------------------------
On 2007-07-05T13:36:24+00:00 Bugzi09-fdo-tormod wrote:

Some more instances of this in https://bugs.launchpad.net/bugs/123134
and its duplicates.

This could be related to bug #11354.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/12

------------------------------------------------------------------------
On 2007-07-06T02:16:17+00:00 Bugzi09-fdo-tormod wrote:

This is my analysis from looking at the source:

SavageCloseScreen() first calls SAVAGEDRICloseScreen() which zeroes out these variables:
   psav->ShadowVirtual = NULL;
   psav->ShadowPhysical = 0;

Then later it calls SavageWriteMode() ->  SavageGEReset() which through:
        if (!from_timeout)
            psav->WaitIdleEmpty(psav);

calls ShadowWait which fatally tries to access psav->ShadowVirtual

But I am not sure which steps are wrong and should be fixed...

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/13

------------------------------------------------------------------------
On 2007-07-06T02:30:23+00:00 Bugzi09-fdo-tormod wrote:

Small correction: Given the uninitialized value of r at the time of
crash, the calling line in SavageGEReset() is rather this one (I have to
trace on the machine when I get to it to confirm):

    } else
        psav->WaitIdleEmpty(psav);

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/14

------------------------------------------------------------------------
On 2007-07-07T02:42:53+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=10613)
workaround: checks for valid ShadowVirtual

This is a workaround, that keeps the server from crashing and borking the consoles. It returns from ShadowWait if there is no ShadowVirtual pointer. 
But I think ShadowWait should not have been called in the first place.

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/15

------------------------------------------------------------------------
On 2007-07-11T18:01:20+00:00 agd5f wrote:

thanks for tracking this down.  fixed.
7832dcd82046238d5accb55468c65241f0edc6d0

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/21

------------------------------------------------------------------------
On 2007-07-11T18:16:10+00:00 agd5f wrote:

*** Bug 11496 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/xorg-server/+bug/123134/comments/22


** Changed in: xorg-server
   Importance: Unknown => Medium

-- 
Xorg segfaults in ShadowWait at shutdown
https://bugs.launchpad.net/bugs/123134
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.