From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 17:50:26 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 431A716A4CF for ; Tue, 4 Nov 2003 17:50:26 -0800 (PST) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C57D643F85 for ; Tue, 4 Nov 2003 17:50:24 -0800 (PST) (envelope-from ltning@anduin.net) Received: (qmail 93018 invoked by uid 85); 5 Nov 2003 01:50:23 -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.50574 secs); 05 Nov 2003 01:50:23 -0000 X-Qmail-Scanner-Mail-From: ltning@anduin.net via anduin.net X-Qmail-Scanner: 1.20rc1 (Clear:RC:1:. Processed in 0.50574 secs) Received: from anduin.net (ltning@212.12.46.226) by anduin.net with SMTP; 5 Nov 2003 01:50:23 -0000 Message-ID: <3FA85758.5030107@anduin.net> Date: Wed, 05 Nov 2003 02:50:16 +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: Alex Wilkinson References: <3FA82486.7000200@morten-johansen.net> <3FA835C8.6010304@anduin.net> <20031105013742.GL90988@squirm.dsto.defence.gov.au> In-Reply-To: <20031105013742.GL90988@squirm.dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Morten Johansen Subject: Re: Was: More ULE bugs fixed. Is: Mouse problem? 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 01:50:26 -0000 Alex Wilkinson wrote: > On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote: > > Just for those interested: > I do *not* get any messages at all from the kernel (or elsewhere) when > my mouse goes haywire. And it's an absolute truth (just tested back and > forth 8 times) that it *only* happens with SCHED_ULE and *only* with old > versions (~1.50) and the very latest ones (1.75 as I'm currently > running). 1.69 for instance did *not* show any such problems. > > I will, however, update my kernel again now, to get the latest > sched_ule.c (if any changes have been made since 1.75) and to test with > the new interrupt handler. I have a suspicion it might be a combination > of SCHED_ULE and some signal/message/interrupt handling causing messages > to get lost along the way. Because that's exactly how it feels... > > Question: How can I find out what verion of SCHED_ULE I am running ? I asked the same recently, and here's what I know: - check /usr/src/sys/kern/sched_ule.c - a page or so down there's a line with the revision - ident /boot/kernel/kernel | grep sched_ule /Eirik > > - aW