Hi,
I've this annoying problem of X crashing with the usual signall 11,
but the intersting thing is it always happens at either 1AM or 1PM!!
It's crashed 4 times in the last 2 weeks. I've checked all the cron tab
files. Any ideas?
BTW, this on : RHEL 2.4.21-27.EL i686 RELEASE: 7.4 3AS
Thanks
Mukesh
XFree86 Version 4.3.0 (Red Hat Enterprise Linux 3 release: 4.3.0-78.EL)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.9-1.751_ELsmp i686 [ELF]
Build Date: 30 November 2004
Build Host: tweety.build.redhat.com
Before reporting any problems, please make sure you are using the most
recent XFree86 packages available from Red Hat by checking for updates
at http://rhn.redhat.com/errata or by using the Red Hat Network up2date
tool. If you still encounter problems, please file bug reports in the
XFree86.org bugzilla at http://bugs.xfree86.org and/or Red Hat
bugzilla at http://bugzilla.redhat.com
Module Loader present
OS Kernel: Linux version 2.4.21-27.EL (bhcompile@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47)) #1 Wed Dec 1 22:08:15 EST 2004 PF
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul 7 13:57:28 2005
(==) Using config file: "/etc/X11/XF86Config"
(WW) VESA(0): Failed to set up write-combining range (0xc0000000,0x7b0000)
Typematic Rate set to 33.3 cps (delay = 500 ms)
Broken pipe
[FVWM][Echo]: 4
[FVWM][FlocaleGetFontSet]: (-adobe-times-bold-r-*-*-14-*-*-*-*-*-*-*) Missing font charsets:
JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0
[FVWM][Echo]: 1
[FVWM][Echo]: "final step"
+ evolution
+ xhost +
[FVWM][Echo]: DONE ALL
access control disabled, clients can connect from any host
+ xscreensaver
+ exit
[MyFvwmButtons][FlocaleGetFontSet]: (fixed) Missing font charsets:
ISO10646-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0
SetGrabKeysState - disabled
Waiting for component to die -- OAFIID:GNOME_Evolution_ExchangeStorage_ShellComponent (1)
waiting for X server to shut down X connection to :0.0 broken (explicit kill or server shutdown).
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 93 requests (90 known processed) with 19 events remaining.
MUKESH: Starting X---- Thu Jul 7 14:00:33 PDT 2005--------------------\n
XFree86 Version 4.3.0 (Red Hat Enterprise Linux 3 release: 4.3.0-78.EL)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.9-1.751_ELsmp i686 [ELF]
Build Date: 30 November 2004
Build Host: tweety.build.redhat.com
Before reporting any problems, please make sure you are using the most
recent XFree86 packages available from Red Hat by checking for updates
at http://rhn.redhat.com/errata or by using the Red Hat Network up2date
tool. If you still encounter problems, please file bug reports in the
XFree86.org bugzilla at http://bugs.xfree86.org and/or Red Hat
bugzilla at http://bugzilla.redhat.com
Module Loader present
OS Kernel: Linux version 2.4.21-27.EL (bhcompile@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47)) #1 Wed Dec 1 22:08:15 EST 2004 PF
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul 7 14:00:33 2005
(==) Using config file: "/etc/X11/XF86Config"
(WW) VESA(0): Failed to set up write-combining range (0xc0000000,0x7b0000)
Typematic Rate set to 33.3 cps (delay = 500 ms)
Broken pipe
[FVWM][Echo]: 4
[FVWM][FlocaleGetFontSet]: (-adobe-times-bold-r-*-*-14-*-*-*-*-*-*-*) Missing font charsets:
JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0
[FVWM][Echo]: 1
[FVWM][Echo]: "final step"
+ evolution
+ xhost +
[FVWM][Echo]: DONE ALL
access control disabled, clients can connect from any host
+ exit
[MyFvwmButtons][FlocaleGetFontSet]: (fixed) Missing font charsets:
ISO10646-1, JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
xterm: unable to open font "cour14", trying "fixed"....
*** loading the extensions datasource
*** loading the extensions datasource
s 0/ 0 0/ 0, g 5/ 26 5/26: +++ travelling traditional 0x081321c0 'VMware Workstation'
stty: standard input: Inappropriate ioctl for device
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
If you encounter a server crash, please report the problem by filing a bug
report in the XFree86.org bugzilla at http://bugs.xfree86.org and/or Red Hat
bugzilla at http://bugzilla.redhat.com/bugzilla. When filing your report, it
is very important that you explain your problem in as much detail as possible,
and include a complete description on how to reproduce the problem. After
submitting the bug report, attach the following files as uncompressed
individual file attachments using the bugzilla file attachment feature:
- X server log file: /var/log/XFree86.0.log
- X server config file: /etc/X11/XF86Config
- Kernel log file: /var/log/messages
X connection to :0.0 broken (explicit kill or server shutdown).
The application 'evolution' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
X connection to :0.0 broken (explicit kill or server shutdown).
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 52452 requests (19540 known processed) with 0 events remaining.
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
The application 'Gecko' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Gecko: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-br: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-cs: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-gw: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-gw: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-cs: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-cs: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-mr: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-mr: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-gg: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-gg: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-br: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-mr: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-cs: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm-cs: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xinit: connection to X server lost.
The application 'vmware' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
# XFree86 4 configuration created by redhat-config-xfree86
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection
Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "hp L1730"
DisplaySize 340 270
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "VESA driver (generic)"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
