From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 10:19:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1D7C16A4CF for ; Wed, 5 Nov 2003 10:19:25 -0800 (PST) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4BD9243FF3 for ; Wed, 5 Nov 2003 10:19:22 -0800 (PST) (envelope-from ltning@anduin.net) Received: (qmail 35523 invoked by uid 85); 5 Nov 2003 18:19:21 -0000 Received: from ltning@anduin.net by anduin.net by uid 82 with qmail-scanner-1.20rc1 (clamscan: 0.60. Clear:RC:1:. Processed in 0.769903 secs); 05 Nov 2003 18:19:21 -0000 X-Qmail-Scanner-Mail-From: ltning@anduin.net via anduin.net X-Qmail-Scanner: 1.20rc1 (Clear:RC:1:. Processed in 0.769903 secs) Received: from anduin.net (ltning@212.12.46.226) by anduin.net with SMTP; 5 Nov 2003 18:19:20 -0000 Message-ID: <3FA93F20.6040602@anduin.net> Date: Wed, 05 Nov 2003 19:19:12 +0100 From: Eirik Oeverby User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031017 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Matthew D. Fuller" References: <20031104153820.GB73736@starjuice.net> <20031104154618.E10222-100000@mail.chesapeake.net> <20031105091007.GJ73736@starjuice.net> <3FA8D0E2.5060507@anduin.net> <20031105175253.GJ12248@over-yonder.net> In-Reply-To: <20031105175253.GJ12248@over-yonder.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Jeff Roberson cc: current@freebsd.org Subject: Re: More ULE bugs fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 18:19:26 -0000 Matthew D. Fuller wrote: > On Wed, Nov 05, 2003 at 11:28:50AM +0100 I heard the voice of > Eirik Oeverby, and lo! it spake thus: > >>The second is that mouse messages are actually *lost*, or bogus ones are >>being generated. I guess it's the first, making moused or X misinterpret >>the messages it gets. Where along the chain it fails I obviously have no >>clue. The consequence of this is that when the mouse stops (like in #1) >>but then resumes from an entirely different point - be it 10 pixels away >>or at the other end of the screen - possibly even generating a button >>push (but not necessarily the corresponding button release) message. > > > Note that I've had this to a greater or lesser extent for as long as I > can remember (certainly back to 3.0-CURRENT). It corresponds with > syslog'd messages on my xconsole along the lines of: > > Nov 3 12:46:13 mortis kernel: psmintr: out of sync (00c0 != 0000). > Nov 3 12:46:13 mortis kernel: psmintr: discard a byte (12). > > It's certainly a lot more common (by orders of magnitude) on 5.x in the > past... oh, I dunno, year-ish, than it was previously. I lose mouse > function for maybe a second, then it squirms itself off somewhere on the > screen and sends some button press events. > > I'm currently running 5.1-R, the traditional scheduler, a PS/2 mouse with > no moused. And since I got them (much more rarely) with earlier > 5-CURRENT's, and with 4-CURRENT's, etc, I can't see how it's scheduler > related. > No idea, but I never got messages like the ones you mention, and it has absolutely never happened on 4.x or with SCHED_4BSD. Weirdness. :) /Eirik > > >>When you say you get the bogus mouse events (which I believe you are >>saying atleast ;) only during load, I'm immediately thinking that yes, >>that might make sense. > > > I don't get it only under load; sometimes from flat idle. However, it's > usually when I first move the mouse, after it sitting still for a while > (where 'while' can vary from a few seconds to a few days, of course); it > hardly ever happens in mid-move. > > >