FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 07-08-2012, 09:41 PM
Joseph
 
Default start X - Segmentation fault

After recent upgrade to Xorg-server-1.12.2 I get: Segmentation fault

I recompiled x11-drivers:
emerge $(qlist -IC x11-drivers)


but I still get an error:

[ 25.153] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fef12ef62ec]
[ 25.153] 15: /usr/bin/X (0x400000+0x24a69) [0x424a69]
[ 25.153]
[ 25.153] Segmentation fault at address 0x9c
[ 25.153]
Fatal server error:
[ 25.153] Caught signal 11 (Segmentation fault). Server aborting
[ 25.153]
[ 25.153]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 25.153] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 25.153]
[ 25.156] Output CRT1 disable success
[ 25.156] Blank CRTC 0 success
[ 25.156] Disable CRTC memreq 0 success
[ 25.172] Disable CRTC 0 success
[ 25.172] Blank CRTC 1 success
[ 25.172] Disable CRTC memreq 1 success
[ 25.172] Disable CRTC 1 success
[ 25.172] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 25.172] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0
[ 25.172] (II) RADEON(0): MC_AGP_LOCATION : 0x00000000
[ 25.183] (II) RADEON(0): avivo_restore !
[ 25.283] Enable CRTC 0 success
[ 25.283] Enable CRTC memreq 0 success
[ 25.283] Unblank CRTC 0 success
[ 25.286] Server terminated with error (1). Closing log file.

Upgrade to all other boxes went fine except this one (the last one).
I went back xorg-server-1.11.4-r1 but I still get the same error message.

This was a box in remote location, so the upgrade was done via ssh and I was able to login via NX but when I tried to login locally (at the box I get: Segmentation
fault


What should I try next?


--
Joseph
 
Old 07-08-2012, 09:48 PM
Michael Mol
 
Default start X - Segmentation fault

On Sun, Jul 8, 2012 at 5:41 PM, Joseph <syscon780@gmail.com> wrote:
> After recent upgrade to Xorg-server-1.12.2 I get: Segmentation fault
>
> I recompiled x11-drivers:
> emerge $(qlist -IC x11-drivers)
> but I still get an error:
>
> [ 25.153] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fef12ef62ec]
> [ 25.153] 15: /usr/bin/X (0x400000+0x24a69) [0x424a69]
> [ 25.153]
> [ 25.153] Segmentation fault at address 0x9c
> [ 25.153]
> Fatal server error:
> [ 25.153] Caught signal 11 (Segmentation fault). Server aborting
> [ 25.153]
> [ 25.153]
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> [ 25.153] Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
> [ 25.153]
> [ 25.156] Output CRT1 disable success
> [ 25.156] Blank CRTC 0 success
> [ 25.156] Disable CRTC memreq 0 success
> [ 25.172] Disable CRTC 0 success
> [ 25.172] Blank CRTC 1 success
> [ 25.172] Disable CRTC memreq 1 success
> [ 25.172] Disable CRTC 1 success
> [ 25.172] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
> [ 25.172] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0
> [ 25.172] (II) RADEON(0): MC_AGP_LOCATION : 0x00000000
> [ 25.183] (II) RADEON(0): avivo_restore !
> [ 25.283] Enable CRTC 0 success
> [ 25.283] Enable CRTC memreq 0 success
> [ 25.283] Unblank CRTC 0 success
> [ 25.286] Server terminated with error (1). Closing log file.
>
> Upgrade to all other boxes went fine except this one (the last one).
> I went back xorg-server-1.11.4-r1 but I still get the same error message.
>
> This was a box in remote location, so the upgrade was done via ssh and I was
> able to login via NX but when I tried to login locally (at the box I get:
> Segmentation fault
>
> What should I try next?

Re-emerge the drivers. I don't know a quick-and-easy way to scoop them
all up, though.

--
:wq
 
Old 07-08-2012, 10:08 PM
Joseph
 
Default start X - Segmentation fault

On 07/08/12 17:48, Michael Mol wrote:


Re-emerge the drivers. I don't know a quick-and-easy way to scoop them
all up, though.

--
:wq


I did:
emerge $(qlist -IC x11-drivers)

you can list the drivers by runing:
qlist -IC x11-drivers

It doesn't help.

--
Joseph
 
Old 07-09-2012, 12:00 AM
Joseph
 
Default start X - Segmentation fault

On 07/08/12 16:08, Joseph wrote:

On 07/08/12 17:48, Michael Mol wrote:


Re-emerge the drivers. I don't know a quick-and-easy way to scoop them
all up, though.

--
:wq


I did:
emerge $(qlist -IC x11-drivers)

you can list the drivers by runing:
qlist -IC x11-drivers

It doesn't help.


Since in make.conf I have:
VIDEO_CARDS="radeon vesa"

one of them should be able to start X after I recompile the drivers:
qlist -IC x11-drivers
x11-drivers/xf86-input-evdev
x11-drivers/xf86-video-ati
x11-drivers/xf86-video-vesa

but it deosn't. What else to check.

In the log I get:
[ 805.883] 15: /usr/bin/X (0x400000+0x24609) [0x424609]
[ 805.883] Segmentation fault at address 0x9c
[ 805.883]
Fatal server error:

[ 805.883] Caught signal 11 (Segmentation fault). Server aborting
[ 805.883]
[ 805.883]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 805.883] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 805.883]
[ 805.886] Output CRT1 disable success

[ 805.891] Blank CRTC 0 success
[ 805.891] Disable CRTC memreq 0 success
[ 805.891] Disable CRTC 0 success
[ 805.891] Blank CRTC 1 success
[ 805.891] Disable CRTC memreq 1 success
[ 805.891] Disable CRTC 1 success
[ 805.891] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 805.891] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0

[ 805.891] (II) RADEON(0): MC_AGP_LOCATION : 0x00000000
[ 805.902] (II) RADEON(0): avivo_restore !
[ 806.002] Enable CRTC 0 success
[ 806.002] Enable CRTC memreq 0 success
[ 806.002] Unblank CRTC 0 success
[ 806.005] Server terminated with error (1). Closing log file.

--
Joseph
 
Old 07-09-2012, 05:09 AM
Graham Murray
 
Default start X - Segmentation fault

Joseph <syscon780@gmail.com> writes:

> This was a box in remote location, so the upgrade was done via ssh and
> I was able to login via NX but when I tried to login locally (at the
> box I get: Segmentation fault
>
> What should I try next?

As you can log in remotely but get a segfault when logging in locally,
could it be one of the PAM modules (one which is called for local login
and starting X but not for ssh remote login) is segfaulting?
 
Old 07-09-2012, 12:15 PM
Nilesh Govindrajan
 
Default start X - Segmentation fault

On 07/09/2012 05:30 AM, Joseph wrote:
> On 07/08/12 16:08, Joseph wrote:
>> On 07/08/12 17:48, Michael Mol wrote:
>>
>>> Re-emerge the drivers. I don't know a quick-and-easy way to scoop them
>>> all up, though.
>>>
>>> --
>>> :wq
>>
>> I did:
>> emerge $(qlist -IC x11-drivers)
>>
>> you can list the drivers by runing:
>> qlist -IC x11-drivers
>>
>> It doesn't help.
>
> Since in make.conf I have:
> VIDEO_CARDS="radeon vesa"
>
> one of them should be able to start X after I recompile the drivers:
> qlist -IC x11-drivers
> x11-drivers/xf86-input-evdev
> x11-drivers/xf86-video-ati
> x11-drivers/xf86-video-vesa
>
> but it deosn't. What else to check.
>
> In the log I get:
> [ 805.883] 15: /usr/bin/X (0x400000+0x24609) [0x424609]
> [ 805.883] Segmentation fault at address 0x9c
> [ 805.883] Fatal server error:
> [ 805.883] Caught signal 11 (Segmentation fault). Server aborting
> [ 805.883] [ 805.883] Please consult the The X.Org Foundation
> support at http://wiki.x.org
> for help. [ 805.883] Please also check the log file at
> "/var/log/Xorg.0.log" for additional information.
> [ 805.883] [ 805.886] Output CRT1 disable success
> [ 805.891] Blank CRTC 0 success
> [ 805.891] Disable CRTC memreq 0 success
> [ 805.891] Disable CRTC 0 success
> [ 805.891] Blank CRTC 1 success
> [ 805.891] Disable CRTC memreq 1 success
> [ 805.891] Disable CRTC 1 success
> [ 805.891] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [
> 805.891] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0
> [ 805.891] (II) RADEON(0): MC_AGP_LOCATION : 0x00000000
> [ 805.902] (II) RADEON(0): avivo_restore !
> [ 806.002] Enable CRTC 0 success
> [ 806.002] Enable CRTC memreq 0 success
> [ 806.002] Unblank CRTC 0 success
> [ 806.005] Server terminated with error (1). Closing log file.
>

Did you by chance compile libc with gcc 4.7 and xorg with 4.6? I had did
something like this with gnome and dependent libraries causing segfaults
just like this.

--
Nilesh Govindrajan
http://nileshgr.com
 
Old 07-09-2012, 02:27 PM
Joseph
 
Default start X - Segmentation fault

On 07/09/12 06:09, Graham Murray wrote:

Joseph <syscon780@gmail.com> writes:


This was a box in remote location, so the upgrade was done via ssh and
I was able to login via NX but when I tried to login locally (at the
box I get: Segmentation fault

What should I try next?


As you can log in remotely but get a segfault when logging in locally,
could it be one of the PAM modules (one which is called for local login
and starting X but not for ssh remote login) is segfaulting?


No, in my case I have a "radeon" card and the xorg was looking KMS in the kernel.
cat .config |grep KMS
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_RADEON_KMS=y

After enabling KMS some might notice 1.5min delay when booting after kernel display the message:
Switching to clocksource tsc

Solution:
emerge: x11-drivers/radeon-ucode

in kernel .config:
Device Drivers:

- Generic Driver Options[*] Include in-kernel firmware blobs in kernel binary
(radeon/R600_rlc.bin) External firmware blobs to build into the kernel binary

(/lib/firmware) Firmware blobs root directory

Run "dmesg" to see exactly which driver is the kernel looking for.
In dmesg after: Switching to clocksource tsc
you will see the driver name.

--
Joseph
 

Thread Tools




All times are GMT. The time now is 12:23 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org