From owner-freebsd-current@FreeBSD.ORG Sat Nov 19 03:07:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F5EB16A41F; Sat, 19 Nov 2005 03:07:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6196D43D46; Sat, 19 Nov 2005 03:07:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2258813 for multiple; Fri, 18 Nov 2005 22:07:00 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAJ36oKN042486; Fri, 18 Nov 2005 22:06:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 18 Nov 2005 22:06:47 -0500 User-Agent: KMail/1.8.3 References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> In-Reply-To: <200511190018.jAJ0ItTe013855@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511182206.49195.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: amd64@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 03:07:09 -0000 On Friday 18 November 2005 07:18 pm, Matthew Dillon wrote: > :So the amd64 snapshot didn't boot but the i386 one did? Interesting. > :Thanks a lot for investigating this. > : > :Scott > > Yup. My guess is that the 64-bit boot issue that early in the boot > sequence is something stupid simple. It looks it from the consistency > of the crash. Actually, your comments about the stray ICU interrupts led me to it on the = way=20 home tonight. Peter has a hack in amd64 that if you don't include 'device= =20 atpic' in your kernel config (not in GENERIC amd64 by default in HEAD) he=20 just masks the PICs. However, he doesn't setup handlers for the spurious=20 interrupts that can still occur (since they are unmaskable). Couple that=20 with the fact that HEAD (until a few hours ago) didn't print the trap messa= ge=20 for a T_RESERVED trap, and you'll see that your panic on amd64 was caused b= y=20 a spurious ICU interrupt. I have part of peter's hack expanded to do a ful= l=20 reset of the ICUs, and I'll update it for Monday to adjust the base interru= pt=20 such that the spurious ICU vectors get sent to the APIC spurious interrupt= =20 vector. That should fix your issue as well as the same issue reported by=20 someone else on the amd64@ list recently. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org