From: Peter Cordes <peter@llama.nslug.ns.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: kernel lockup
Date: Wed, 16 May 2001 01:03:28 -0300 [thread overview]
Message-ID: <20010516010328.D19015@llama.nslug.ns.ca> (raw)
I'm running 2.4.4, rsynced from the benh tree. I wanted to adjust my
keyboard key repeat stuff, so I ran (on the console)
bigfoot:~# kbdrate -h
kbdrate: invalid option -- h
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.)
More details: I'm running a quad PPC604 Mac clone from Daystar (the Genesis
MP). The top line in /usr/src/linux-2.4-benh/ChangeSet is:
cort@ftsoj.fsmlabs.com|drivers/sound/dmasound/Config.in|20010106072831|13776|67da7753905f489
benh@zion.wanadoo.fr|drivers/sound/dmasound/Config.in|20010512181358|01477,
in case that helps :)
I wasn't running X at the time of the crash. I was using a framebuffer
console (ATI mach64 driver).
This crash is repeatable. I just did it again (after going to single user
mode and remounting my drives read-only :). However, this time it prints an
infinity of newlines after the crash message.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@llama.nslug. , ns.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BCE
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-16 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 4:03 Peter Cordes [this message]
2001-05-16 9:21 ` kernel lockup Benjamin Herrenschmidt
2001-05-16 11:00 ` Ethan Benson
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=20010516010328.D19015@llama.nslug.ns.ca \
--to=peter@llama.nslug.ns.ca \
--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).