From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 19:09:04 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 E785F16A4CE for ; Tue, 4 Nov 2003 19:09:04 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D05D343FEC for ; Tue, 4 Nov 2003 19:09:03 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id hA538s772390; Tue, 4 Nov 2003 22:08:54 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Tue, 4 Nov 2003 22:08:54 -0500 (EST) From: Jeff Roberson To: Eirik Oeverby In-Reply-To: <3FA85758.5030107@anduin.net> Message-ID: <20031104220836.A10222-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Morten Johansen cc: Alex Wilkinson 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 03:09:05 -0000 On Wed, 5 Nov 2003, Eirik Oeverby wrote: > 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 Ident also works on source files. Cheers, Jeff > > /Eirik > > > > > - aW > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >