public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: KDB blindly reads keyboard port
Date: Fri, 29 Sep 2006 12:18:04 +1000	[thread overview]
Message-ID: <14425.1159496284@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 27 Sep 2006 16:11:00 CST." <200609271611.00701.bjorn.helgaas@hp.com>

Bjorn Helgaas (on Wed, 27 Sep 2006 16:11:00 -0600) wrote:
>On Tuesday 26 September 2006 20:45, Keith Owens wrote:
>> No support for legacy I/O ports could be a bigger problem than just
>> KDB.
>
>On Itanium (and I suppose on x86), ACPI theoretically tells us enough
>that we don't need to assume any legacy resources.  Of course, Linux
>doesn't listen to everything ACPI is trying to tell it.  But that's
>a Linux deficiency we should remedy.
>
>> To fix just KDB, apply this patch over kdb-v4.4-2.6.18-common-1 and
>> add 'kdb_skip_keyboard' to the boot command line on the offending
>> hardware. 
>
>This doesn't feel like the right solution.  Since firmware tells us
>whether the device is present, I think we should rely on that.  If
>you want to use the device before ACPI is initialized, *then* you
>should pass a "kdb_use_keyboard" sort of flag.

I have never been a big fan of ACPI, having seen too many broken ACPI
tables.  But if that is what you want ...

Bjorn, could you apply my previous patch anyway, boot your problem
system with kdb_skip_keyboard, drop into KDB and
'md4c1 acpi_kbd_controller_present'.  That will quickly confirm if acpi
is detecting the absence of the keyboard on your system.


  reply	other threads:[~2006-09-29  2:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 19:54 KDB blindly reads keyboard port Bjorn Helgaas
2006-09-27  2:45 ` Keith Owens
2006-09-27 11:57   ` Matthew Wilcox
2006-09-27 22:11   ` Bjorn Helgaas
2006-09-29  2:18     ` Keith Owens [this message]
2006-09-29 16:57       ` Bjorn Helgaas
2006-09-29 18:01         ` Luck, Tony
2006-09-29 18:58           ` Bjorn Helgaas
2006-11-16  4:02     ` Keith Owens
2006-11-16 16:28       ` Bjorn Helgaas
2006-11-10  4:23 ` Keith Owens
2006-11-10  4:28   ` Matthew Wilcox
2006-11-10  6:15     ` Keith Owens

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=14425.1159496284@kao2.melbourne.sgi.com \
    --to=kaos@sgi.com \
    --cc=bjorn.helgaas@hp.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