From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] System hangup w/ X taking 100% cpu
Date: 13 Dec 2001 21:38:22 +0200 [thread overview]
Message-ID: <1008272303.3441.16.camel@nosferatu.lan> (raw)
In-Reply-To: <0GOA00914L3IVX@mxout2.netvision.net.il>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On Thu, 2001-12-13 at 19:11, Dan Armak wrote:
> Hi all,
>
> On my new r12 system I've had a hangup in X11. No apparent cause. The system
> stopped accepting any input and the screen didn't even complete a redraw. The
> mouse went on moving as it was in h/w, but clicks were no good. Magic sysrq
> wasn't responding either.
>
> I logged in via ssh, and top showed X was taking 100% cpu. I tried killall X,
> no effect. I tried kill -9 <X pid>, the remote login hung up and i couldn't
> ssh to it again. I had to do a hard reboot.
>
> Then I expirienced the same effect twice on an old rc5 system which underwent
> absolutely no updates or config changes for a few months now. Only this was
> standalone not on a net, so I couldn't login via ssh.
>
> Both rc6 lockups were when running kmail, both rc5 lockups while running
> ksirc.
>
> Trying to send this message, I had another lockup on the rc6 system, hope
> this reaches you.
>
> I'm absolutely mystified. Ideas? Anyone seen this kind of thing before?
>
> --
>
Hi Dan
What version kernel, nvidia driver and filesystem are you
running?
I updated my nvidia drivers to the latest 2313, and only had
problems (screen corruption, lockups, etc) on a system that
had been running stable for a long time now. i went back to
the previous version, and it is 100% again. I also had problems with my
old savage and sertain drivers.
Then, nearly a year back, I had the same type of problems
(lockups), but this was due to bad ram, and a kernel/reiserfs
and hardware compat problem.
Greetings,
--
Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-13 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 17:11 [gentoo-dev] System hangup w/ X taking 100% cpu Dan Armak
2001-12-13 17:38 ` Nathaniel Grady
2001-12-13 18:27 ` djamil
2001-12-13 18:19 ` Dan Armak
2001-12-13 17:29 ` djamil essaissi
2001-12-13 18:35 ` Dan Armak
2001-12-13 18:42 ` Dan Armak
2001-12-13 19:38 ` Martin Schlemmer [this message]
2001-12-13 19:50 ` Dan Armak
2001-12-13 20:43 ` Dan Armak
2001-12-15 14:40 ` m3thos
2001-12-15 17:15 ` Dan Armak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1008272303.3441.16.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox