From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Keith Owens <kaos@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: KDB blindly reads keyboard port
Date: Tue, 26 Sep 2006 19:54:30 +0000 [thread overview]
Message-ID: <200609261354.30722.bjorn.helgaas@hp.com> (raw)
get_kbd_char() in arch/ia64/kdb/kdba_io.c does "inb(KBD_STATUS_REG)".
But we don't know whether there's even an i8042 keyboard controller
present. On HP ia64 boxes, there is no i8042, and trying to read
from it can cause an MCA.
This depends on the specific platform and how it is configured. I
observed this MCA while booting the SLES10 install kernel on an
HP rx7620 in "default" acpiconfig mode. The supported acpiconfig
mode on this box is "single-pci-domain", which also puts some
legacy ports into "soft-fail" mode, where the read will just return
0xff instead of causing an MCA. But I think it's wrong to blindly
poke around in I/O port space.
i8042_pnp_init() uses PNPACPI to figure out whether the i8042
device is present. That's probably too heavy-weight for what
you want to do in KDB, though.
Bjorn
next reply other threads:[~2006-09-26 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 19:54 Bjorn Helgaas [this message]
2006-09-27 2:45 ` KDB blindly reads keyboard port Keith Owens
2006-09-27 11:57 ` Matthew Wilcox
2006-09-27 22:11 ` Bjorn Helgaas
2006-09-29 2:18 ` Keith Owens
2006-09-29 16:57 ` Bjorn Helgaas
2006-09-29 18:01 ` Luck, Tony
2006-09-29 18:58 ` Bjorn Helgaas
2006-11-10 4:23 ` Keith Owens
2006-11-10 4:28 ` Matthew Wilcox
2006-11-10 6:15 ` Keith Owens
2006-11-16 4:02 ` Keith Owens
2006-11-16 16:28 ` Bjorn Helgaas
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=200609261354.30722.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=kaos@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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