Bug 39464
Summary: | Starting new programs doesn't work, running programs keep working OK | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <ben.verloop> | ||||||||
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 7.1 | CC: | alane | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i386 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2002-02-11 13:53:41 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Need Real Name
2001-05-07 20:00:17 UTC
Created attachment 17586 [details]
The /var/log/messages file might be usefull
Created attachment 17587 [details]
up2date log, error occured both before and after updating (I rebooted after updating)
This is likely a local configuration problem of some kind I believe, perhaps a conflict with some software you are using. Attach your XFree86 server log from after you've had a problem. Also, your XF86Config-4 file. Also, if you boot graphical login, change to a non graphical login by changing: initdefault:5 to initdefault:3 in /etc/inittab, then reboot. Start X with: startx > X.log 2>&1 Then wait until you experience the problem, then kill X, start it up again with just "startx" and attach the X.log file to the bug report. Interesting. I've been seeing similar behavior. At first I thought it was KDE 2.2alpha fscking up in strange and wondrous ways. But ... If you strace one of the clients, you see that it sends the "MAGIC-COOKIE" message to X, it gets back its response, and then, next read, it gets an EOF on the socket to X. This condition does not always seem to be permanent; it sometimes spontaeously reverts to working behavior. I just saw another message tonight, from Xv, that prompted me to come here and look: XIO: fatal IO error 105 (No buffer space available) on X server ":0.0" after 1330041 requests (1323083 known processed) with 743 events remaining. Ouch. Nothing looks terribly interesting in the log, but will be attached after this comment is added. Created attachment 20392 [details]
X server log gzipped
Ooh. This is unsavory. I've got *thousands* of these in my /var/log/messages over the last couple of hours: Jun 5 22:09:34 wwweasel kernel: __alloc_pages: 2-order allocation failed. Jun 5 22:09:34 wwweasel kernel: __alloc_pages: 3-order allocation failed. Jun 5 22:09:34 wwweasel kernel: __alloc_pages: 3-order allocation failed. Jun 5 22:09:34 wwweasel kernel: __alloc_pages: 2-order allocation failed. Jun 5 22:09:34 wwweasel kernel: __alloc_pages: 3-order allocation failed. This can't be good, huh? Ben.Verloop, please attach X server log and config file uncompressed as file attachments using bugzilla's link below. Closing bug. Please reopen after attaching requested information if problem persists. |