From owner-freebsd-current Mon May 22 9:52: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C55E337B69D for ; Mon, 22 May 2000 09:52:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA60866; Mon, 22 May 2000 09:51:50 -0700 (PDT) (envelope-from dillon) Date: Mon, 22 May 2000 09:51:50 -0700 (PDT) From: Matthew Dillon Message-Id: <200005221651.JAA60866@apollo.backplane.com> To: Garrett Wollman Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, Boris Popov Subject: Re: Anyone else seeing jumpy mice? References: <3970.958963729@localhost> <200005221518.LAA43664@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> No, I don't mean rodents who've nibbled on chocolate-covered expresso :> beans, I mean PS/2 mice which fall victim to this new problem: : :> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != 0000). : :I saw this happen once, during a period heavy disk and serial :activity. : :-GAWollman I got an email from Boris Popov in regards to getting more silo overflows after the SMP cleanup patch then before. One thing the patch removed was the hack that allowed certain interrupts (tty interrupts) to run in parallel with the supervisor. Now, I must say, that there is no way we are going to add that hack back in ... it was a real mess and is simply not worth it, and when we move to the interrupt threading model we can truely make the serial interrupt SMP-safe and do away with the issue once and for all. I don't know if the mouse problems are related or not, did anyone have jumpy-mouse problems before the SMP cleanup was committed? (i.e. in kernels then two weeks old for 4.0, and four weeks old for 5.0). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message