From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PNP PS/2 probing racy?
Date: Thu, 28 Jan 2010 22:24:05 -0800 [thread overview]
Message-ID: <20100129062405.GA4177@core.coreip.homeip.net> (raw)
In-Reply-To: <20100128162248.GF14636@basil.fritz.box>
On Thu, Jan 28, 2010 at 05:22:48PM +0100, Andi Kleen wrote:
> On Thu, Jan 28, 2010 at 07:57:47AM -0800, Dmitry Torokhov wrote:
> >> Hi,
> >>
> >> I noticed that on one test system of machine when booting the same
> >> kernel I get:
> >>
> >> PNP: No PS/2 controller found. Probing ports directly.
> >> serio: i8042 KBD port at 0x60,0x64 irq 1
> >> serio: i8042 AUX port at 0x60,0x64 irq 12
> >>
> >> and sometimes on another boot
> >>
> >> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
> >>
> >> Since I presume the BIOS does not change, is it possible the Linux
> >> procedure for this PNP probe is racy? I haven't checked the code so far.
> >>
> >
> > Are you using KVM with that box by any chance?
>
> Yes, it uses a KVM, but the console was always on it.
>
That is wierd... Was it on the whole time (including the time when BIOS
was doing the initialization)? Anyway i8042 expects to find all PNP
devices already enumerated by the time its initialization runs. When
you see that message about PS2 controller not found do you see PNP0303
and PNP0f03 if you do:
for i in /sys/devices/pnp0/00*; do echo -n "$i: "; cat $i/id; done
?
--
Dmitry
next prev parent reply other threads:[~2010-01-29 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 13:54 PNP PS/2 probing racy? Andi Kleen
2010-01-28 15:57 ` Dmitry Torokhov
2010-01-28 16:22 ` Andi Kleen
2010-01-29 6:24 ` Dmitry Torokhov [this message]
2010-01-29 12:24 ` Andi Kleen
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=20100129062405.GA4177@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=andi@firstfloor.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