Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752349AbZGaPRC (ORCPT ); Fri, 31 Jul 2009 11:17:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751838AbZGaPRA (ORCPT ); Fri, 31 Jul 2009 11:17:00 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:57543 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751621AbZGaPQ7 (ORCPT ); Fri, 31 Jul 2009 11:16:59 -0400 Date: Fri, 31 Jul 2009 16:17:35 +0100 From: Alan Cox To: Ozan =?UTF-8?B?w4dhxJ9sYXlhbg==?= Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , ACPI Devel Maling List Subject: Re: [Bug #13471] Loading parport_pc kills the keyboard if ACPI is enabled Message-ID: <20090731161735.6a94ad9c@lxorguk.ukuu.org.uk> In-Reply-To: <4A7308E8.1000200@pardus.org.tr> References: <20090731151417.568094e5@lxorguk.ukuu.org.uk> <4A7308E8.1000200@pardus.org.tr> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1255 Lines: 30 O> Finally, it seems that the problem is available with 2.6.28, so the starting > point is still fuzzy to me. I remember that the keyboard was working OK with > 2.6.29_rc7 but now it's not. > > Maybe we should drop this report from the regression list." > > > Monday I'll have access to the computer. I'll build and try to find the last working version. > Meanwhile, I'd like to hear about your possible finding. 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 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. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/