From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working Date: Tue, 18 Mar 2008 11:54:11 -0400 Message-ID: <20080318114711.ZZRA012@mailhub.coreip.homeip.net> References: <1205775229.25146.11.camel@indigo.declera.com> <20080317145429.ZZRA012@mailhub.coreip.homeip.net> <1205780323.25146.13.camel@indigo.declera.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from rn-out-0910.google.com ([64.233.170.190]:32080 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760629AbYCSWa1 (ORCPT ); Wed, 19 Mar 2008 18:30:27 -0400 Received: by rn-out-0910.google.com with SMTP id v46so626657rnb.15 for ; Wed, 19 Mar 2008 15:30:25 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1205780323.25146.13.camel@indigo.declera.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Yanko Kaneti Cc: linux-input@vger.kernel.org On Mon, Mar 17, 2008 at 08:58:43PM +0200, Yanko Kaneti wrote: > > On Mon, 2008-03-17 at 14:55 -0400, Dmitry Torokhov wrote: > > Hi, > > > > On Mon, Mar 17, 2008 at 07:33:49PM +0200, Yanko Kaneti wrote: > > > Hi > > > > > > My PS/2 mouse stops being detected between kernels 2.6.24.3-12.fc8 and > > > 2.6.25-0.121.rc5.git4.fc9 (which I believe do not carry any patches in > > > that area). Its an ASUS P5E-VM DO motherboard , bios revision 0506. The > > > PS/2 keyboard still works. > > > > > > Attached are both dmesg logs with i8042.debug=1, dmidecode, lspci -vvnn > > > Tried i8042.noloop and both the mouse and keyboard stop working. > > > > > > > Could you please send me dmesg from booting with i8042.noloop. I would > > expect this option to help in your case so I am curious what went wrong. > > Attached > Hmm, it looks the kernel does the right thing in case of i8042.noloop, except that it does not work :(. Kernel triest to query the mouse but it does not respond. Can you try taking contents of drivers/input/serio from 2.6.25 and copy it in .24? It will most likely compile... If that works I'm afraid I will ahve to ask you to do git biscect to find the offending commit. -- Dmitry