[Pkg-fglrx-devel] Bug#677667: fglrx-driver: xf86OpenConsole: Cannot find a free VT

[Paul Menzel]

forcemerge 675940 677667
forwarded 675940 http://ati.cchtml.com/show_bug.cgi?id=522

Am Samstag, den 16.06.2012, 13:58 +0200 schrieb Andreas Beckmann:
> On 2012-06-15 23:41, Paul Menzel wrote:
> >         [   240.105] 
> >         Fatal server error:
> >         [   240.105] xf86OpenConsole: Cannot find a free VT
> 
> > The X server seems to be restarted very quickly in succession.
> > 
> >         -rw-r--r-- 1 root root  5217 2012-06-15 23:29:08.157218849 +0200 /var/log/Xorg.172.log
> >         -rw-r--r-- 1 root root  4562 2012-06-15 23:29:08.149218919 +0200 /var/log/Xorg.61.log
> >         -rw-r--r-- 1 root root  4247 2012-06-15 23:29:08.145218954 +0200 /var/log/Xorg.29.log
> 
> http://bugs.debian.org/650183
> 
> Fabian reported there:
>   "I experienced a similar (the same?) issue and eventually got around
>    it by upgrading to the latest libgl1-mesa-dri package from sid,
>    8.0.2-2 at that time."

Interesting.

> The Xorg.*.log from gdm3 are not helpful as there seems to be the
> interesting part missing due to the frequent restarting.

I thought to have searched for the culprit string in the log file.

    $ zgrep -i segf /var/log/Xorg.*

But …

> Can you try kdm/xdm/... and see if the Xorg.*.log contains more
> information after the error?

… with your suggestion to install a different X display manager – I
chose SLiM – I can see the console and …

> And be aware of
>   #675940: fglrx crashs with Xserver 1.12 on 64bit architecture
> Backports has an older X stack available.

… I can verify that I get the same crash. Now I also find the
segmentation faults in the log files of the GDM 3 started sessions since
I have to search for `segm` and not `segf` (for segfault).

        $ zgrep -i segm /var/log/Xorg.*
        /var/log/Xorg.0.log:[     6.424] Segmentation fault at address 0x31b31742
        /var/log/Xorg.0.log:[     6.424] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.0.log.old:[  5276.852] Segmentation fault at address 0xffffffffcfb9f742
        /var/log/Xorg.0.log.old:[  5276.852] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.10.log.old:[    38.737] Segmentation fault at address 0x301a8742
        /var/log/Xorg.10.log.old:[    38.737] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.11.log:[    56.355] Segmentation fault at address 0xffffffff87a23742
        /var/log/Xorg.11.log:[    56.355] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.11.log.old:[    47.386] Segmentation fault at address 0x5894a742
        /var/log/Xorg.11.log.old:[    47.386] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.12.log:[    57.170] Segmentation fault at address 0x96b7742
        /var/log/Xorg.12.log:[    57.170] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.12.log.old:[    51.682] Segmentation fault at address 0xffffffffa3824742
        /var/log/Xorg.12.log.old:[    51.682] Caught signal 11 (Segmentation fault). Server aborting
        /var/log/Xorg.13.log:[    53.598] Segmentation fault at address 0xffffffffd91d9742
        /var/log/Xorg.13.log:[    53.598] Caught signal 11 (Segmentation fault). Server aborting
        […]

I am therefore merging the two reports. Also it seems that there is a
workaround for that issues in the upstream report [1] involving patching
libpciaccess [2]. But I have not tried it yet.


Thanks,

Paul


[1] http://ati.cchtml.com/show_bug.cgi?id=522
[2] http://ati.cchtml.com/show_bug.cgi?id=522#c3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-fglrx-devel/attachments/20120616/cda5765d/attachment-0001.pgp>