Date: Wed, 05 Nov 2003 02:50:16 +0100 From: Eirik Oeverby <ltning@anduin.net> To: Alex Wilkinson <alex.wilkinson@dsto.defence.gov.au> Cc: Morten Johansen <mail@morten-johansen.net> Subject: Re: Was: More ULE bugs fixed. Is: Mouse problem? Message-ID: <3FA85758.5030107@anduin.net> In-Reply-To: <20031105013742.GL90988@squirm.dsto.defence.gov.au> References: <3FA82486.7000200@morten-johansen.net> <3FA835C8.6010304@anduin.net> <20031105013742.GL90988@squirm.dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FA85758.5030107>