Bug 6239 - X went beserk with gettimeofday and hung.
X went beserk with gettimeofday and hung.
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
Depends On:
  Show dependency treegraph
Reported: 1999-10-22 09:48 EDT by Telsa Gwynne
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-03 16:48:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Telsa Gwynne 1999-10-22 09:48:31 EDT
RH Linux 6.1, but with a kernel I built (removed a lot of
irrelevant-to-me stuff). Cyrix MediaGX chip. Possibly
relevant package list at end.

I leave X (and Gnome) running for long periods of time (days
to weeks) and this is usually fine. If it's relevant I can
probably come up with a list of all the things that were
running at the time: it was mostly a lot of gnome-terminals,
netscape and gnome's freecell when this happened:

X just hung. Attempting to switch "workspace" with window
maker (I thought it was the app I was using that had gone
bang) had no effect. Control-alt-F1, F2 etc had no effect.
Control-alt-backspace (!) had no effect. No disk activity.

Telnetted in from another machine and on 'top', X was
sitting at 99% of CPU fairly solidly. Lots and lots and
_lots_ of gettimeofday() requests zooming up the screen
with strace. Tried to shoot various apps to see if this
had any effect (nope) and then killed the X process: also
didn't work. Eventually shot it with kill SEGV. Want a
core file? :) (file reports it as a core of ld-linux.so.2
for some reason)

XFree86 package list.
[hobbit@aloss ~]$ rpm -qa | grep XFree
Comment 1 Preston Brown 2000-02-03 16:48:59 EST
bummer. :)  I have no idea what happened here.  We need to make the bug
reproducible to track it down.

Note You need to log in before you can comment on or make changes to this bug.