linux-kernel - Re: [Bug #13471] Loading parport_pc kills the keyboard if ACPI is enabled

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: <4A781C6E.7040900@pardus.org.tr>
Date:	Tue, 04 Aug 2009 14:33:02 +0300
From:	Ozan Çağlayan <ozan@...dus.org.tr>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [Bug #13471] Loading parport_pc kills the keyboard if ACPI is
 enabled

Alan Cox wrote On 31-07-2009 18:17:
> There have been few changes to parport_pc but one thing recent changed
> the probe for SuperIO chips via low addresses and that could be
> interfering.
>
> commit e2434dc1c19412639dd047a4d4eff8ed0e5d0d50
> Author: Jens Rottmann <JRottmann@...PERTEmbedded.de>
> Date:   Mon Jun 22 16:51:49 2009 +0100
>
> changed the behaviour slightly (hence asking about which release if it
> was a recent breakage). Its also a code area with very few changes so if
> you can find which one worked last, you should be able to transplant that
> parport_pc into 2.6.current and see if its parport or acpi triggered
> breakage.
>   

I've tested on 2.6.30.4 which has apparently this commit, no changes.

I've booted into Ubuntu 8.10 which has 2.6.28. The keyboard was working
correctly eventhough parport_pc was loaded. I removed and re-probed and
the keyboard is gone.

I've set BIOS settings to default, nope.

I'll try bisecting when I find the last-good/first-bad kernel version.
--
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/