Re: Shared memory - Was: 2 Queries
In any case, one major offender is imlib. Since I've recently gone
Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option
or things would go bad after a few minutes or hours of use.
That explains the errors when running xchat, but that doesnt explain
Netscape ;)
The annoying thing about this is that if a program decides to die because
of this error, it seems I've got a 50/50 chance that it's taken out for
good. I have to reboot to reclaim memory :(
It'd be nice if we had a utility that could clean out and reclaim the
shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and
obviously any other apps using shared memory), and get on with life :)
(anyone listening?)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
options SHMMAXPGS=4096
options SHMALL=16384
options SHMSEG=16
options SEMMNI=32
options SEMMNS=128
Tried those, same error :(
_XF86BigfontQueryFont: could not attach shm segment
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Try increasing SHMSEG to 128.
Appears to be working fine with SHMAXPGS=4097 and SHMSEG=128 - fingers
crossed ;) Thanks for your help everyone...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Shared memory - Was: 2 Queries
Just an update on this shared memory error. After running XFree86 for a
couple of hours, running various programs (I've not seen a pattern yet):
[dozprompt@guru]# xchat
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 84 error_code 10 request_code 142 minor_code 1
Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
serial 85 error_code 151 request_code 142 minor_code 5
Reckon this is due to a work in progress on the SYSV* section of the
kernel? Anyone know if that is being worked on right now?
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Do you have any plans to make XFree86-devel port of it? This let us to test
it and refine before XF-4.0 will be released.
I had no plans, personally, but then I'm not a ports
maintainer. Compiling the snapshot is pretty simple anyway.
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Thanks for pointing. What is your opinion about it (stability, compatability,
performance etc)?
Haven't had time to screw with it any more than just a basic twm setup. I'd
have to reinstall most of my X apps to use it (and I already have a nice
3.3.6 setup right now).
I made it so I could try it out seriously sometime.. right now my priority
is getting other things ready for 4.0-RELEASE.
I've been using it since the release of 3.9.1.7, and I've really enjoyed
using it. It's somewhat faster than 3.x, but that may just be because my
video card has better drivers this time around.
The release notes detail how XFree86 has become easier and easier to build
and install, and it's true. I've always scared away from editing the 3.x
config by hand - the config file format is well organised this time. As I
mentioned in a previous mail in this chain, compilation and installation
was a total breeze. Adding a single line to site.def, making
World/Install and that was that - it took a while, but it was plain
sailing.
Usage wise it's fast, it's smooth and it's been completely
reliable. Aside from a few teething problems with -current (which is to
be expected). If you're waiting for it's official release, you will be
pleasantly suprised :)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
I've got the same problem also, and can confirm it is a
-current/XFree86-3.9.18 problem. (Probabably mainly an XFree86
problem, I presume.) Apparently, the XFree86 build process isn't
perfect either, since certain options in xc/config/cf/host.def can
cause the "make install" to fail. One set of options I had in
host.def caused the make World to finish successfully. But when I did
the ensuing "make install", it began compiling the aout shared libs,
which it didn't do during the make World. (What the hell?)
Strange, the build process was wonderfully successful for me. The only
modification I made before the make World/install process was adding:
BuildAoutLibraries
to site.def... Since posting my last mail, I've also encountered a
similar message, thie time reported by Imlib. It's not the exact same
message, but it's the same meaning. They are both having trouble getting
a handle on shared memory (at least, this is my interpretation). I've got
SYSV* in my kernel, so it's not that...
It would be nice to know if it was a FreeBSD or XFree86 thing, perhaps
someone on the list not using a pre 4.0 XFree86 snapshot could help us out
here?
Of course, it could just be (and most likely is) just being triggered by a
change in FreeBSD 4.0, which the XFree86 code (obviously) hasnt caught up
on yet.
It's not urgent, there are no critical errors produced by this situation,
everything still works just fine.
Keep me posted on anything you encounter...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
More likely work in progress with broken gtk desktop voodoo. Dont you think that would be bit of a cooincidence? Since the messages are almost identical in nature to the ones I've been getting from other programs *not* gtk/gdk based ;) The link between them so far is shared memory... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Two queries [ KDE / XFree86 ]
Greetings, I'm just wondering if anyone has encountered the following, and
what solutions you may have come up with / ideas you may have.
This may not be a FreeBSD problem, since I am using the latest XFree86
pre-4.0 snapshot.
First:
Almost every time I load a page in Netscape (latest port), I get the
message:
"XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24"
Second:
Using KDM in place of XDM, XFree86 just dies immediately, resulting in
several attempts at launching, and then a 30 second pause. XFree86 works
perfectly otherwise.
The main reason I'm asking this here is so that if it is a known problem
with -current, I'll have no need to investigate further, and i can just
wait until it's fixed.
If it is not a known problem, then I shall report my findings to the
relevant parties.
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
