From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263990AbTG2DPV (ORCPT ); Mon, 28 Jul 2003 23:15:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270373AbTG2DPV (ORCPT ); Mon, 28 Jul 2003 23:15:21 -0400 Received: from fw.osdl.org ([65.172.181.6]:47499 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263990AbTG2DPP (ORCPT ); Mon, 28 Jul 2003 23:15:15 -0400 Date: Mon, 28 Jul 2003 20:14:59 -0700 From: Andrew Morton To: Albert Cahalan Cc: zwane@arm.linux.org.uk, albert@users.sourceforge.net, linux-yoann@ifrance.com, linux-kernel@vger.kernel.org, akpm@digeo.com, vortex@scyld.com, jgarzik@pobox.com Subject: Re: another must-fix: major PS/2 mouse problem Message-Id: <20030728201459.78c8c7c6.akpm@osdl.org> In-Reply-To: <1059447325.3862.86.camel@cube> References: <1054431962.22103.744.camel@cube> <3EDCF47A.1060605@ifrance.com> <1054681254.22103.3750.camel@cube> <3EDD8850.9060808@ifrance.com> <1058921044.943.12.camel@cube> <20030724103047.31e91a96.akpm@osdl.org> <1059097601.1220.75.camel@cube> <20030725201914.644b020c.akpm@osdl.org> <1059447325.3862.86.camel@cube> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Albert Cahalan wrote: > > OK, I did this. Now, in microseconds, I get: > > ------------------------ > IRQ use min max > --- -------- --- ------- > 0 timer 40 103968 > 1 i8042 14 1138 (was 389773) > 2 cascade - - > 3 - - - > 4 serial 29 56 > 5 uhci-hcd - - > 6 - 690 690 > 7 - 40 40 > 8 - - - > 9 - - - > 10 - - - > 11 eth0 73 31332 (was 1535331) > 12 i8042 18 215 (was 102895) > 13 - - - > 14 ide0 7 43846 > 15 ide1 7 12 > ------------------------ > > boomerang_interrupt itself takes 4 to 59 microseconds. So this looks OK, yes? (Is that instrumentation patch productisable? Looks handly, albeit a subset of microstate accounting) > Then I switched to 2.6.0-test2. Testing more, I get the > problem with or without SMP and with or without > preemption. Here's a chunk of my log file: > > Loosing too many ticks! > TSC cannot be used as a timesource. (Are you running with SpeedStep?) > Falling back to a sane timesource. > psmouse.c: Lost synchronization, throwing 3 bytes away. > psmouse.c: Lost synchronization, throwing 1 bytes away. > > Arrrrgh! The TSC is my only good time source! Arrrgh! More PS/2 problems! I think the lost synchronisation is the problem, would you agree? The person who fixes this gets a Nobel prize. > Remember that this is a pretty normal system. I have > a Red Hat 8 install w/ required upgrades, ext3, IDE, > a 1-GHz Pentium III, a boring VIA chipset, etc. > > To reproduce, I do some PS/2 mouse movement while > doing one of: > > a. Lots of concurrent write() and sync() activity to ext3. > b. Lots of NFSv3 traffic. ie: lots of interrupt traffic causes the PS2 driver to go whacky?