Date: Wed, 5 Nov 2003 10:48:19 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: current@freebsd.org Subject: Re: More ULE bugs fixed. Message-ID: <Pine.NEB.3.96L.1031105104658.76974D-100000@fledge.watson.org> In-Reply-To: <20031105091007.GJ73736@starjuice.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Nov 2003, Sheldon Hearn wrote: > On (2003/11/04 15:46), Jeff Roberson wrote: > > > > The thing is, I'm using 4BSD, not ULE, so I wouldn't trouble Jeff to > > > look for a cause for that specific problem in ULE. > > > > How long have you been seeing this? Are you using a usb mouse? Can you > > try with PS/2 if you are? > > Since my last update, Fri Oct 24 17:47:22. > > I am using a USB mouse, but don't have a PS/2 one. I'm also using > moused, and my WM is sawfish. > > The problem with all these reports is that they're scattered. It's hard > to pin down exactly what the common elements are. Indeed, we may be > looking at combinations of elements. > > I don't have time to be more helpful, which is why I hadn't complained. > I just wanted to include the datapoint that over-active mouse behaviour > under load exists under SCHED_4BSD as well. > > Incidentally, this is under ATA disk load. I don't really push my CPU. There's been some speculation that the PS/2 mouse problem could be due to high interrupt latency for non-fast interrupt handlers (especially ones not MPSAFE) in 5.x. I think it would make a lot of sense for us to push Giant off both the PS/2 mouse and syscons interrupt handlers in the near future. For syscons, this would also improve the reliability of dropping into the debugger from a non-serial console. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1031105104658.76974D-100000>