From: Nathaniel Grady <nate@nutopia.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] System hangup w/ X taking 100% cpu
Date: Thu, 13 Dec 2001 12:38:31 -0500 [thread overview]
Message-ID: <20011213123831.B16820@nutopia.org> (raw)
In-Reply-To: <0GOA00914L3IVX@mxout2.netvision.net.il>; from danarmak@gentoo.org on Thu, Dec 13, 2001 at 07:11:23PM +0200
To add to this my really old -rc6 system I believe has similar problems - konqueror locks fairly frequently when dragging and dropping (when using as a file manager) - I never ssh'd in to check top because i don't like having any open ports on my laptop. If i ever get my brand-new gentoo install to work with PCMCIA correctly i'll report on that. I do not have this issue with Nautulus or GMC (however i do have a problem that sometmes i get stuck with the "drag and drop" mouse pointer and have to switch to another console to kill -9 gmc or nautulus - i assume that is a backbox or xmms issue). I use default optimization flags for PII in make.conf.
For anyone who is curious this is a Thinkpad 600e / 128mb ram / 366mhz PII / NeoMAGIC video / ambicom ethernet / CS4232 audio w/ oss drivers. W2K did really odd things to the IRQ/DMA assignments but i reflashed the bios and used mkfs to fix that problem :)
--Nate Grady
PS: I'm saying this in hopes that it will help diagnose the problem - I don't really expect to be able to look at much for the next week as it's finals time :( Over xmass break i do plant to get this darn thing workin right :)
On Thu, Dec 13, 2001 at 07:11:23PM +0200, 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?
>
> --
>
> Dan Armak
> Gentoo Linux Developer, Desktop Team
> Matan, Israel
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-12-13 17:38 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 [this message]
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
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=20011213123831.B16820@nutopia.org \
--to=nate@nutopia.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