linux-kernel - Re: Current git: no keyboard when booting in verbose mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090923164426.GB13435@core.coreip.homeip.net>
Date:	Wed, 23 Sep 2009 09:44:27 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Marc Dionne <marc.c.dionne@...il.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	linux-input@...r.kernel.org
Subject: Re: Current git: no keyboard when booting in verbose mode

On Wed, Sep 23, 2009 at 08:16:02AM -0400, Marc Dionne wrote:
> On Wed, Sep 23, 2009 at 5:09 AM, Jiri Kosina <jkosina@...e.cz> wrote:
> >
> > [ adding some CCs ]
> >
> > On Tue, 22 Sep 2009, Marc Dionne wrote:
> >
> >> I'm having issues with the current kernel in git, and wondering if this
> >> will ring a bell for anyone. The main symptom is that on most boots the
> >> keyboard is not detected - the system gets to the console login prompt
> >> but input is not recognized.  Sometimes (rarely) the keyboard will be ok
> >> at the console, but the keyboard and mouse are non functional once in X.
> >
> > Are both keyboard and mouse in question PS/2?
> 
> No - keyboard is PS/2 but the mouse is USB.
> 
> >> - On a failed boot with no keyboard, this line is missing from dmesg:
> >>     AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
> >
> > Could you please provide output from kernel booted with 'i8042.debug' from
> > the failing case?
> 
> Attached are the dmesg output for a successful boot (with "quiet") and
> a failed one.  I see that the i8042.debug output is quite different
> for the 2 cases.
> 

Hmm, nothing obvious jumps at me... Just keyboard not responding at all
in the bad case. Any chance of bisecting? Maybe check before first input
merge and after?

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/