Segmentation fault at address 0x7

Antonio Olivares olivares14031 at
Tue Nov 16 03:55:43 UTC 2010

----- Original Message ----

From: Michal Jaegermann <michal at>
To: For testers of Fedora development releases <test at>
Sent: Mon, November 15, 2010 6:53:35 PM
Subject: Re: Segmentation fault at address 0x7

On Mon, Nov 15, 2010 at 04:36:02PM -0800, Antonio Olivares wrote:
> Cannot boot the 2.6.36 rawhide(f15) kernel.

What you are posting indicates nothing of that sort.

> This is a kernel bug with the 2.6.36 kernel?:
> [   27.768371] ------------[ cut here ]------------
> [   27.768756] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()

This is WARNING.  It says so.  In any case:

> xauth:  creating new authority file /home/olivares/.serverauth.1561

So here you are already running a user-space.  It means that you
already booted.

> Backtrace:
> 0: /usr/bin/X (xorg_backtrace+0x2d) [0x4831f1]
> 1: /usr/bin/X (0x400000+0x52cd2) [0x452cd2]
> 2: /lib64/ (0x7f36b3006000+0x34100) [0x7f36b303a100]
> 3: /usr/lib64/ (nouveau_channel_alloc+0x4d) 
> 4: /usr/lib64/xorg/modules/drivers/ (0x7f36b18de000+0xd43d) 
> 5: /usr/lib64/xorg/modules/drivers/ (0x7f36b18de000+0xde28) 
> 6: /usr/bin/X (AddScreen+0x144) [0x42b2bd]
> 7: /usr/bin/X (InitOutput+0xb53) [0x45f8f6]
> 8: /usr/bin/X (0x400000+0x213a5) [0x4213a5]
> 9: /lib64/ (__libc_start_main+0xfd) [0x7f36b3024e7d]
> 10: /usr/bin/X (0x400000+0x210c9) [0x4210c9]
> Segmentation fault at address 0x7
> Fatal server error:
> Caught signal 11 (Segmentation fault). Server aborting

OTOH your X server does not start.  That is a problem but another
> Please consult the Fedora Project support 
>      at
>  for help. 

Did you try that?  Does the bug you are seeing looks like
Although maybe rather like that one:
If yes then add comments; if not then file another report.

test mailing list
test at
To unsubscribe:

-----End of Original Message ----
Sorry to all, but this message sent from NEW yahoo mail and no >, are placed :(

Thanks Michal,


What you are posting indicates nothing of that sort.

Typo, mistake, I could not get anything done :(, I could not boot to this 
kernel, this time it booted, but X not working :(, is that a little bit better?

Thank you for your insight into these mentioned bugs :), I will see how I can 
comment/file new bug report.  I appreciate yours and other's help here.  I 
finally managed to apply rawhide's updates, only one machine boots to X, but 
takes a long time :(, but at least it boots  and works now :)




More information about the test mailing list