From: Martin Costabel <costabel@univ-rennes1.fr>
To: Gwyn Judd <b.judd@xtra.co.nz>
Cc: Dan Foster <dsf@gblx.net>,
LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: X still locks up
Date: Fri, 07 Jul 2000 11:47:14 +0100 [thread overview]
Message-ID: <3965B532.F00E82B6@univ-rennes1.fr> (raw)
In-Reply-To: 20000707153525.A1445@thislove.dyndns.org
Gwyn Judd wrote:
[]
> Okay so you get it on x86 2.2.16 and XFree 4.01
> I get it on powerpc kernel >= 2.2.15 and XFree3.3.6
> Any other takers?
I don't know if all this is really the same thing, but I have been
getting sudden X freezes randomly with all 2.2.x kernels when using
Xpmac. For me this was the main reason to switch to XFree68_FBDev where
I *never* got these with 2.2.x kernels. Now I am getting these freezes
also with XFree68_FBDev (some 3.3.6 version) when using 2.3.x or 2.4.0
kernels. I very rarely use xmms (but always netscape), and I get these
freezes sometimes when the machine is completely idle. Sometimes this
happens after a couple of minutes, sometimes after 3 days.
The symptoms are: Mouse frozen, no keyboard input possible, no
MagicSysRq, no X shutdown with ctl-cmd-del, no console switching, the
only key combination working is the ctl-cmd-power hard reboot. On the
other hand, the kernel and even X seem to continue to live at least for
a while. I can see messages continue to scroll down and hear downloads
or compilations making their disk noise. The one time I tried to ping
from the outside, I was not successful, but then it sometimes takes 2
minutes of pinging to wake the machine up and get a response even when
it is not frozen.
>From my observations, I concluded that this must be a problem with the
keyboard and/or mouse drivers in X. But since this part of the kernel
and X ( I never understood why XFree has to have their own drivers for
everything that is already in the kernel) is worst black magic, rapidly
changing in incompatible ways, and since my machine (6400, ADB keyboard
and mouse, valkyrie video) belongs to an endangered species anyway, I
did not really try to understand what happens.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-07 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 2:26 X still locks up Gwyn Judd
2000-07-07 3:22 ` Dan Foster
2000-07-07 3:35 ` Gwyn Judd
2000-07-07 10:47 ` Martin Costabel [this message]
2000-07-07 16:39 ` Gregorio Gervasio Jr.
2000-07-07 6:07 ` Michel Lanners
2000-07-07 9:09 ` Michel Dänzer
[not found] ` <20000707105332.11070@mailhost.mipsys.com>
2000-07-08 19:15 ` Gwyn Judd
-- strict thread matches above, loose matches on Subject: below --
2000-07-08 22:06 Iain Sandoe
[not found] <200007090058.BAA22277@hyperion.valhalla.net>
2000-07-09 10:29 ` Gwyn Judd
2000-07-09 19:24 ` Michel Dänzer
2000-07-09 12:25 Iain Sandoe
2000-07-09 20:56 Iain Sandoe
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=3965B532.F00E82B6@univ-rennes1.fr \
--to=costabel@univ-rennes1.fr \
--cc=b.judd@xtra.co.nz \
--cc=costabel@wanadoo.fr \
--cc=dsf@gblx.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).