LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > *BSD
User Name
Password
*BSD This forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.

Notices


Reply
  Search this Thread
Old 03-30-2003, 08:20 AM   #1
Enforcer
LQ Newbie
 
Registered: Apr 2002
Location: Sweden
Distribution: FBSD 4.10, FBSD 5.2.1 , OBSD 3.4
Posts: 27

Rep: Reputation: 15
XFree86 4.3.0 : Caught signal 11


Code:
Fatal server error:
Caught signal 11.  Server aborting
Hi!

I upgraded to 4.3.0 from ports (portupgrade) everything look great when I where going to start my X it just burp out that error message. I have made a new XF86Config w/ XFree86 -configure, no diff.. I check to see if X found my GPU and it did.. just fine. any tips?

Hope you understand my problem.. please any help..!

My System:
OS: FBSD 4.7
CPU: P2 400MHz
RAM: 128MB
GPU: Riva128
 
Old 03-30-2003, 08:30 AM   #2
acid2000
Member
 
Registered: Nov 2001
Location: Exeter, UK
Distribution: Gentoo 1.4
Posts: 243

Rep: Reputation: 30
Bad compiler options????
 
Old 03-30-2003, 11:49 AM   #3
Enforcer
LQ Newbie
 
Registered: Apr 2002
Location: Sweden
Distribution: FBSD 4.10, FBSD 5.2.1 , OBSD 3.4
Posts: 27

Original Poster
Rep: Reputation: 15
Quote:
Bad compiler options????
..donīt think so.. I did like this when I upgraded..

1. cvsup -g -L 2 portsupfile && portsdb-Uu && pkgdb -F
2. portversion -c > update.sh
3. chmod +x update.sh
4. added "#!/bin/sh" to the top of update.sh
5. ./update.sh

so.. If thereīs any "bad compiler options" it must be a general fault.. eg. someone else should have encountered it... ?????

btw. is there some where I could learn about this signal thing?? what do Signal 11 stand for?

Last edited by Enforcer; 03-30-2003 at 11:52 AM.
 
Old 03-31-2003, 09:28 AM   #4
llama_meme
Member
 
Registered: Nov 2001
Location: London, England
Distribution: Gentoo, FreeBSD
Posts: 590

Rep: Reputation: 30
Signal 11 is sent when an app segfaults. It just means X crashed, basically.

Alex
 
Old 03-31-2003, 02:44 PM   #5
Enforcer
LQ Newbie
 
Registered: Apr 2002
Location: Sweden
Distribution: FBSD 4.10, FBSD 5.2.1 , OBSD 3.4
Posts: 27

Original Poster
Rep: Reputation: 15
tnx alex..

for my problem I, maybe, got an solution.. a friend told me it could be a memory problem.. broken ram.. I didnīt get to happy to hear that.. but I will have to check it out...
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Caught signal 11. Server aborting Gosa Debian 4 02-27-2007 02:03 AM
Caught Signal 4 + only x as root. zvn Red Hat 0 10-29-2004 09:02 AM
Caught signal 11, X server aborting emphaze Linux - Software 3 02-24-2004 10:25 AM
Caught signal 11. _Server aborting Budha Linux - Software 3 12-20-2003 05:39 AM
Signal 11 Caught ixion Linux - General 0 02-11-2003 06:49 AM

LinuxQuestions.org > Forums > Other *NIX Forums > *BSD

All times are GMT -5. The time now is 02:41 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration