linux-kernel - Re: Lenovo 3000 N100 i8042 problems

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Sep 2008 18:03:59 -0400 (EDT)
From:	Daniel Barkalow <barkalow@...ervon.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	Christopher Desjardins <cddesjardins@...il.com>
Subject: Re: Lenovo 3000 N100 i8042 problems

On Wed, 3 Sep 2008, Henrique de Moraes Holschuh wrote:

> On Wed, 03 Sep 2008, Dmitry Torokhov wrote:
> > On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > > > I guess we could use System's product name to differentiate between 
> > > > Cristopher's and Daniel's boards. Although I must admit it is the very 
> > > > first time when I see a box that behaves better with active mux. DOes 
> > > > Vista use active mux nowadays? Because if it is not then I bet there is 
> > > > (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.
> > > 
> > > I guess so, yes.
> > > 
> > > On the other hand, this might also be viewed as regression (we made 
> > > Daniel's hardware behave worse with recent kernel than it did before), so 
> > > I think we still would like to have this fixed. What about the patch 
> > > below, adding the match on System's product name, as you suggested? 
> > > Thanks.
> > > 
> > 
> > I agree. Daniel, could you please try the patch to make sure it
> > restores the previous behavior for you and I will push it through.
> 
> I fell I need to warn you guys that you are likely breaking machines that
> match that DMI info but have a newer BIOS, unless they use different BIOSes
> (not enough data without a full dmidecode output from the other machine).

The patch under consideration is to restore pre-2.6.25 behavior (i.e., 
active mux) for machines other than the one in a particular bug report, 
while 2.6.25 broke my machine. So this will probably rebreak machines that 
were broken until 2.6.25 (and can't break anything else). I think it would 
actually be better if we could apply the quirk to all models of 3000 N100 
except for mine (but I don't think quirk-matching supports that); my 
model is the only one we know of which came with a BIOS that has issues 
with legacy mode. I still think it's weird that Lenovo managed to break 
active mux when they'd had it working before, but who knows what's going 
on in their firmware development process.

In any case, I suspect that the legacy behavior on my machine is strange 
but manageable (given that Windows doesn't seem to have had problems using 
legacy mode even on my hardware, so far as I can tell), and we should be 
able to cope with it in general.

	-Daniel
*This .sig left intentionally blank*
--
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/