Alex W. Jackson
22nd January 2005, 11:28 AM
My X server is crashing seemingly at random once every couple of days, usually with nothing but Firefox and a gnome-terminal running. The crash message in /var/log/messages is as follows:
X [foo]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbfffed48 error 14
(Where [foo] is X's pid; it's different each time. However, the register values are exactly the same every time)
rip shouldn't ever be 0000000000000000, should it? It looks like it's trying to jump to address 0--either by dereferencing a null function pointer, or by doing a return with the stack in an invalid state (such that a 0 word gets pulled as the return address).
I'm using the X that ships with FC3, not updated or modified in any way, and the radeon driver (video card is a 9200SE).
I don't suppose some guru will be able to tell me from the crash message exactly what's going on. The sporadic-ness of the crashes makes me suspect a hardware problem, like flaky RAM, but i'd be relieved to find out that something else was the cause (I'm obviously not looking forward to RMAing my RAM)
X [foo]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbfffed48 error 14
(Where [foo] is X's pid; it's different each time. However, the register values are exactly the same every time)
rip shouldn't ever be 0000000000000000, should it? It looks like it's trying to jump to address 0--either by dereferencing a null function pointer, or by doing a return with the stack in an invalid state (such that a 0 word gets pulled as the return address).
I'm using the X that ships with FC3, not updated or modified in any way, and the radeon driver (video card is a 9200SE).
I don't suppose some guru will be able to tell me from the crash message exactly what's going on. The sporadic-ness of the crashes makes me suspect a hardware problem, like flaky RAM, but i'd be relieved to find out that something else was the cause (I'm obviously not looking forward to RMAing my RAM)
