From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: kernel lockup
Date: Wed, 16 May 2001 03:00:13 -0800 [thread overview]
Message-ID: <20010516030013.N14546@plato.local.lan> (raw)
In-Reply-To: <20010516092154.16870@mailhost.mipsys.com>; from benh@kernel.crashing.org on Wed, May 16, 2001 at 11:21:54AM +0200
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
On Wed, May 16, 2001 at 11:21:54AM +0200, Benjamin Herrenschmidt wrote:
>
> >bigfoot:~# kbdrate -h
> >kbdrate: invalid option -- h
thats interesting, kbdrate -h gives a usage message for me.. like it
should.
> >Machine check in kernel mode.
> >Caused by (from SRR1=c9030): Unknown values in msr
> >
> > What do I do to debug this?
> >
> > The machine is totally locked, not even the SysRQ combination does
> >anything. (control+command+power still resets though, since it is handled
> >in hardware on oldworlds.)
>
> Well, I guess that kbdrate is yet another dumb x86'ism that will
> directly tap the hardware of a PC's keyboard controller...
according to the man page it trys to be portable:
[...]
All this is very architecture dependent. Nowadays kbdrate
first tries the KDKBDREP and KIOCSRATE ioctls. (The for-
mer usually works on an m68k machine, the latter for
SPARC.) When these ioctls fail an ioport interface as on
i386 is assumed.
FILES
/etc/rc.local
/dev/port
Linux 1.1.19 22 June 1994 2
that fallback is probably the bugger though.
> Well, I may be wrong, but machine check usually means that you are
> trying to access non-existing hardware.
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2001-05-16 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 4:03 kernel lockup Peter Cordes
2001-05-16 9:21 ` Benjamin Herrenschmidt
2001-05-16 11:00 ` Ethan Benson [this message]
2001-05-16 15:28 ` Peter Cordes
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=20010516030013.N14546@plato.local.lan \
--to=erbenson@alaska.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.