From: Keith Owens <kaos@sgi.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: KDB blindly reads keyboard port
Date: Fri, 10 Nov 2006 06:15:57 +0000 [thread overview]
Message-ID: <16089.1163139357@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 09 Nov 2006 21:28:03 PDT." <20061110042803.GU16952@parisc-linux.org>
In-Reply-To: <200609261354.30722.bjorn.helgaas@hp.com>
Matthew Wilcox (on Thu, 9 Nov 2006 21:28:03 -0700) wrote:
>On Fri, Nov 10, 2006 at 03:23:20PM +1100, Keith Owens wrote:
>> Bjron, could you try kdb-v4.4-2.6.19-rc5-{common,ia64}-2 on your
>> problem system? I changed kdb so it only uses the keyboard if at least
>> one console matches the pattern /^tty[0-9]*$/. IOW, if the user
>> specifies an i8042 style console on the command line (or uses the
>> default with CONFIG_VT=y) then kdb will attempt to use that keyboard.
>> Otherwise kdb ignores a VT style console, even when the kernel is
>> compiled with CONFIG_VT=y.
>
>If I'm using an HP Integrity system with a USB keyboard, won't I still
>have a console that matches ^tty[0-9]*$ ?
Good point. How about the console list must include /^tty[0-9]*$/
_and_ there must be an interrupt registered with a name of "i8042"
before KDB will attempt to access i8042 ports?
WARNING: multiple messages have this Message-ID (diff)
From: Keith Owens <kaos@sgi.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: KDB blindly reads keyboard port
Date: Fri, 10 Nov 2006 17:15:57 +1100 [thread overview]
Message-ID: <16089.1163139357@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 09 Nov 2006 21:28:03 PDT." <20061110042803.GU16952@parisc-linux.org>
Matthew Wilcox (on Thu, 9 Nov 2006 21:28:03 -0700) wrote:
>On Fri, Nov 10, 2006 at 03:23:20PM +1100, Keith Owens wrote:
>> Bjron, could you try kdb-v4.4-2.6.19-rc5-{common,ia64}-2 on your
>> problem system? I changed kdb so it only uses the keyboard if at least
>> one console matches the pattern /^tty[0-9]*$/. IOW, if the user
>> specifies an i8042 style console on the command line (or uses the
>> default with CONFIG_VT=y) then kdb will attempt to use that keyboard.
>> Otherwise kdb ignores a VT style console, even when the kernel is
>> compiled with CONFIG_VT=y.
>
>If I'm using an HP Integrity system with a USB keyboard, won't I still
>have a console that matches ^tty[0-9]*$ ?
Good point. How about the console list must include /^tty[0-9]*$/
_and_ there must be an interrupt registered with a name of "i8042"
before KDB will attempt to access i8042 ports?
next prev parent reply other threads:[~2006-11-10 6:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 19:54 KDB blindly reads keyboard port Bjorn Helgaas
2006-09-26 19:54 ` Bjorn Helgaas
2006-09-27 2:45 ` Keith Owens
2006-09-27 2:45 ` Keith Owens
2006-09-27 11:57 ` Matthew Wilcox
2006-09-27 11:57 ` Matthew Wilcox
2006-09-27 22:11 ` Bjorn Helgaas
2006-09-27 22:11 ` Bjorn Helgaas
2006-09-29 2:18 ` Keith Owens
2006-09-29 2:18 ` Keith Owens
2006-09-29 16:57 ` Bjorn Helgaas
2006-09-29 16:57 ` Bjorn Helgaas
2006-09-29 18:01 ` Luck, Tony
2006-09-29 18:01 ` Luck, Tony
2006-09-29 18:58 ` Bjorn Helgaas
2006-09-29 18:58 ` Bjorn Helgaas
2006-11-10 4:23 ` Keith Owens
2006-11-10 4:23 ` Keith Owens
2006-11-10 4:28 ` Matthew Wilcox
2006-11-10 4:28 ` Matthew Wilcox
2006-11-10 6:15 ` Keith Owens [this message]
2006-11-10 6:15 ` Keith Owens
2006-11-16 4:02 ` Keith Owens
2006-11-16 4:02 ` Keith Owens
2006-11-16 16:28 ` Bjorn Helgaas
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=16089.1163139357@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 \
--cc=matthew@wil.cx \
/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.