On Thu, 16 Jan 2003, Vlado Potisk wrote:
Regarding: after few days: Caught signal 11. Server aborting
Have you checked http://www.bitwizard.nl/sig11/ ?
It might be bad hardware and not a real X server error.
-Peter
___
XFree86 mailing list
[EMAIL
On Thu, 16 Jan 2003, Vlado Potisk wrote:
It might be bad hardware and not a real X server error.
It might be, but it is not very probable if you consider:
- thorough check with memtest86 passed recently
You didn't write that in the original mail.
- no problem with 3.3.6 in
On Thu, 16 Jan 2003, Vlado Potisk wrote:
Maybe the question then becomes: what fonts do you have on your
system?
I have an external font server, If you want to see any font list, please
write what command I have to run to produce it.
_fs_load_glyphs() seems to be part of a module that
On Thu, 16 Jan 2003, Vlado Potisk wrote:
Can you recompile the X server with debug symbols on (-g) to get a
better backtrace ... or alternatively thru creative use of gdb
correlate the address in _fs_load_glyphs() from the backtrace with a
line number in xc/lib/font/fc/fserve.c ?
OK, I
On Thu, 16 Jan 2003, Vlado Potisk wrote:
Regarding: after few days: Caught signal 11. Server aborting
Email: [EMAIL PROTECTED]
XFree86 Version: 4.2.0 and also 4.2.1
OS: Linux RedHat 7.3 and also Mandrake 9
[SNIP]
Repeat By:
My X
On Thu, 16 Jan 2003, Vlado Potisk wrote:
Have you checked http://www.bitwizard.nl/sig11/ ?
It might be bad hardware and not a real X server error.
It might be, but it is not very probable if you consider:
- thorough check with memtest86 passed recently
Ugh.. I should have read the
On Thu, 16 Jan 2003, Mark Vojkovich wrote:
From what I've seen, most segfaults with the last official release
are due to bugs in the font renderers, or maybe just in the font
server. You could try explicitly putting font paths in the XF86Config
Not just in the font server -- a bad font
On Fri, 17 Jan 2003, Peter Finderup Lund wrote:
On Thu, 16 Jan 2003, Mark Vojkovich wrote:
From what I've seen, most segfaults with the last official release
are due to bugs in the font renderers, or maybe just in the font
server. You could try explicitly putting font paths in the
On Fri, 17 Jan 2003, Peter Finderup Lund wrote:
On Fri, 17 Jan 2003 [EMAIL PROTECTED] wrote:
just connecting and throwing /dev/urandom on it until xfs closed the
connection or crashed. Once it was running without problems for more than
3 days I gave up.
Brilliant!
I'm wondering
9 matches
Mail list logo
