From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461)
Description of problem:
I can not start X session because of 'segmentation fault' in the 'panel'
module. It has started happening after I set kernel parameter 'bigpages=2048M'
Current system has 2 Xeon CPUs, ATI Rage XL, 4Gb of RAM and after restart it
has about 1Gb of free memory (regarding to the 'free' command). 'swap' shows no
usage of 8Gb swap at same time.
Very interesting thing about it that if I will try to 'startx' system will:
- hang for my session (from initlevel 3)
- I will not be able to use 'ps -elf' from any other terminal (it will hang
right away without any output)
- I will not be able to use 'top' from any other terminal (it will hang right
after the output of 'white page header')
- I will be able to 'telnet'
- Oracle will work fine
All of this at same time.
Version-Release number of selected component (if applicable):
the system is up-to-date on November 05, 2002 (regarding to RehHat network)
Steps to Reproduce:
1. set kernel parameter 'bigpages=2048M'
2. start oracle
Actual Results: startx will be very slow to start X session (on init screen
bottom panel (with Gnome-logo) will be shown as gray stripe across the screen
nautilus will not be started
I have to have X on my Oracle server to use Administrator tools (java-
Do not hesitate to contact me if you need more information.
Thanks in any advise,
Can you attach your X server config file, your X log file, your /var/log/messages
file, and the output of:
Created attachment 83867 [details]
Requested config files and system logs
Here is requested information about my system (DELL PowerEdge 4600) as an
Thanks in advance,
The problem in the subject of the bug happened on Nov 1 at 11:45am.
After that I've lost ability to use local keyboard and mouse, but telnet
sessions were Ok.
At noon I've restarted whole system by pressing 'Reset' button.
Hope, it will help with system logs.
Thanks for the info. One request though... in the future, please attach
all files as individual uncompressed file attachments one at a time. That
facilitates viewing them easily in a web browser.
Changing component to XFree86, as this is not a 3.3.6 bug report.
I've looked at your logs, and don't see anything noteable. Not even
a sign of an XFree86 crash in your X log. Are you sure this log is
from after a crash? If you start up X again after a crash, it will
wipe out the log, so you need to snag a copy of the log without starting
Also, I'm not sure what you are refering to as the "panel". Is this
the GNOME panel? If GNOME is crashing, that isn't an XFree86 bug.
I've CC'd a couple of our GNOME guys for comment also.
I am not sure that it is exactly XFree86 bug. Probably, it is not (because I
see blue background /*not black and white*/, some elements of desktop, etc...).
Sorry, my mistake.
The XFree86.0.log is exact log that has been written on crush time (Nov 1,
11:49am). Since then I did not start X again.
By "Panel" I refer to Gnome-panel ("with Gnome-logo" foot).
On a side note, separate from the bug report..
You do realize you can use X on a different machine, and run Oracle
tools via "ssh -X" remotely, without requiring an X server on the Oracle
Just thought I'd mention that in case you weren't aware. It could be
a useful workaround for now for you.
Owen, Havoc: Any comments? I don't see any XFree86 problem here, but
before reassigning to gnome-panel I wanted to get your opinions.
Thanks, It is really good idea!
But I feel bad about existance of the problem in new production system.
... and posting little yellow note on the rack:
"Do not 'startx' on this server or I will fire at will"
It's hard to tell here ... the useful file would be ~/.xsession-errors
user from the user that you tried in as.
It would be also useful to know if you could log in with a different
Is the 'bigpages' command and starting oracle relevant? If you reboot
and don't do that, can you log in OK? If so, then it's almost certainly
a kernel or possibly an X bug.
I was calling RedHat tech support.
It seems now as misconfiguration of shm. Probably, this is the cause of
the 'segmentation fault' error (shm was configured to be bigger than size of
physical memory + swap).
For now, I guess, we can close this bug and if problem reappears I will create
Thanks a lot,
P.S. Another misconfiguration of my system (regarding to RedHat tech. support)
was incorrect kernel. It is recommended to use the 'Enterprise' kernel in the
system with 4Gb+ of virtual memory /* not the 'SMP'-kernel */.
My system has 4Gb of RAM and 8Gb of swap.
You've indicated your system has been misconfigured, and that you've
now worked things out, so I'm closing this as NOTABUG.
Thanks for providing the updated information.
Let's close it as NOTABUG!
Thanks a lot,