From owner-freebsd-current Wed Nov 11 23:06:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05401 for freebsd-current-outgoing; Wed, 11 Nov 1998 23:06:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05396 for ; Wed, 11 Nov 1998 23:06:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA08543; Wed, 11 Nov 1998 23:04:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811120704.XAA08543@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Peter Johnson , current@FreeBSD.ORG Subject: Re: XFree86 nonstandard server / ELF compat problem In-reply-to: Your message of "Wed, 11 Nov 1998 22:54:58 PST." <622.910853698@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 23:04:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is most likely a bug in the server. > > Are you sure he wasn't using the same server before without problems > before the upgrade? That's the way I read it, anyway. No, I'm not. But the symptoms are indeed indicative of an interrupt storm, or something else that's seriously screwing up interrupt delivery, and the finger is pointed fairly squarely at the X server. Peter, are you using an ELF kernel? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message