From owner-freebsd-current Thu Nov 29 18:41:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 33D6C37B417 for ; Thu, 29 Nov 2001 18:41:11 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id NAA18089 for ; Fri, 30 Nov 2001 13:41:08 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01KBBF9EE7C04M2KPP@cim.alcatel.com.au> for freebsd-current@freebsd.org; Fri, 30 Nov 2001 13:41:02 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id fAU2f4x42635 for freebsd-current@freebsd.org; Fri, 30 Nov 2001 13:41:04 +1100 Content-return: prohibited Date: Fri, 30 Nov 2001 13:41:04 +1100 From: Peter Jeremy Subject: XFree86 3.3.6 dying To: freebsd-current@freebsd.org Mail-Followup-To: freebsd-current@freebsd.org Message-id: <20011130134104.A42555@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG With a recently re-built XFree86, running on -current from last Sunday, whenever I hit one of the keypad keys, the X server crashes. This is somewhat disconcerting... The kernel prints "sigreturn: eflags = 0x13282, was 0x256" (the old eflags value an addition I made to that printf whilst tracking down another problem). These values are consistent. The X server reports that it received SIGBUS and will core dump, but instead goes into a tight loop and needs kill -ABRT or kill -9 to recover. This happens whether or not I'm logged in, after I use xmodmap to unmap the relevant keycodes and when the screen is locked. ktrace on the Xserver shows the server reading a keycode from the keyboard, checking the mouse and getting EWOULDBLOCK then receiving a SIGBUS. Has anyone else seen anything like this? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message