linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gwyn Judd <b.judd@xtra.co.nz>
To: DeRobertis <derobert@erols.com>
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Fixing dead Xservcfers (was Re: seemingly random lock-up with kernel 2.2.17p7)
Date: Fri, 7 Jul 2000 10:17:25 +1200	[thread overview]
Message-ID: <20000707101725.A2168@thislove.dyndns.org> (raw)
In-Reply-To: <l03130300b58a3be9712a@[209.122.247.91]>; from derobert@erols.com on Thu, Jul 06, 2000 at 09:41:36AM -0400


On Thu, Jul 06, 2000 at 09:41:36AM -0400, DeRobertis wrote:
> At 2:03 AM +1200 on 7/6/00, Gwyn Judd wrote:
>
> >This all sounds quite familiar. The lockups have happened with both xmms
> >and mpg123. I have no idea if it is a full system lock or just X since I
> >have no remote machine to ping it with, all I am able to do is force
> >reboot.
>
> All you need to do is have your scripts which start as reset the keyboard
> mode to XLATE after the server terminates. A few lines of C code will do
> this; I think there is even a binary to do it, too.
>
> No idea why Linuxppc does not put this in the X start script.

This is not the only problem that can occur. I installed the Xpmac
server the other day and the most annoying thing it did was if it
couldn't start up correctly for some reason (one of them was that I
didn't have the 100dpi fonts installed) then it would immediately quit.
This would cue init (or gdm I'm not sure which) to try to start it
again. and again. This happened about 3 times a second rendering the
system completely unusable. I was not able to change VC's or anything
like that. Fortunately using someone else's suggestion I was able to use
the "Magic Sysrq" key combo to at least reboot the system safely.

--
Gwyn Judd (b.judd@xtra.co.nz)
A sine curve goes off to infinity, or at least to the end of the blackboard.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-07-06 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 13:36 seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 13:45 ` Michel Dänzer
2000-07-05 13:57   ` Gwyn Judd
2000-07-05 20:13     ` Magic SysRq key [was Re: seemingly random lock-up with kernel 2.2.17p7] phandel
     [not found] ` <Pine.SGI.4.21.0007050845550.10655-100000@rainbow.uchicago.edu>
2000-07-05 14:03   ` seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 14:10     ` Michel Dänzer
2000-07-05 14:17       ` Gwyn Judd
2000-07-05 14:47         ` me
2000-07-05 15:00           ` Michel Dänzer
2000-07-05 15:27           ` Mario Scarpa
2000-07-05 15:43             ` Benjamin Herrenschmidt
     [not found]     ` <l03130300b58a3be9712a@[209.122.247.91]>
2000-07-06 22:17       ` Gwyn Judd [this message]
2000-07-05 14:26 ` Benjamin Herrenschmidt
2000-07-05 14:36   ` Michel Dänzer

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=20000707101725.A2168@thislove.dyndns.org \
    --to=b.judd@xtra.co.nz \
    --cc=derobert@erols.com \
    --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).