From owner-freebsd-arm@FreeBSD.ORG Mon Oct 22 01:40:16 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00A5BFEF for ; Mon, 22 Oct 2012 01:40:15 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id A30028FC08 for ; Mon, 22 Oct 2012 01:40:15 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q9M1e9mh012114 for arm@freebsd.org; Mon, 22 Oct 2012 01:40:09 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 9tysexkyvb3ra2fpuq9m7ja892; for arm@freebsd.org; Mon, 22 Oct 2012 01:40:08 +0000 (UTC) (envelope-from kientzle@freebsd.org) From: Tim Kientzle Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Trashed registers returning from kernel? Date: Sun, 21 Oct 2012 18:40:08 -0700 Message-Id: <2B1CF099-50F0-46BE-8B02-61309DF93D5F@freebsd.org> To: arm@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 01:40:16 -0000 On the BeagleBone, I'm seeing a similar crash in several different user = land programs. I suspect it's a kernel bug. Symptom: program is killed with SIGSEGV. Most of the registers contain = values above 0xc0000000 (pointing into kernel space). Theory: * Registers are not always getting correctly restored on a kernel->user = transition. * SEGV is a consequence. I can reproduce it semi-consistently by running "emacs existing-file" = just after a reboot. (But I'm pretty sure this is the same symptoms = I've seen with several other programs, so I don't think it's a bug in = emacs.) Has anyone else seen this on an armv6 system? Does anyone have suggestions for how to go about debugging this? Suggestions appreciated. Cheers, Tim