From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 04:18:03 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 6A9D416A420; Sun, 20 Nov 2005 04:18:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E888C43D45; Sun, 20 Nov 2005 04:18:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAK4I19M010936; Sat, 19 Nov 2005 21:18:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <437FF8F9.8000207@samsco.org> Date: Sat, 19 Nov 2005 21:18:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> In-Reply-To: <200511182206.49195.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org, freebsd-current@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: Sun, 20 Nov 2005 04:18:03 -0000 John Baldwin wrote: > 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 > home tonight. Peter has a hack in amd64 that if you don't include 'device > atpic' in your kernel config (not in GENERIC amd64 by default in HEAD) he > just masks the PICs. However, he doesn't setup handlers for the spurious > interrupts that can still occur (since they are unmaskable). Couple that > with the fact that HEAD (until a few hours ago) didn't print the trap message > for a T_RESERVED trap, and you'll see that your panic on amd64 was caused by > a spurious ICU interrupt. I have part of peter's hack expanded to do a full > reset of the ICUs, and I'll update it for Monday to adjust the base interrupt > such that the spurious ICU vectors get sent to the APIC spurious interrupt > vector. That should fix your issue as well as the same issue reported by > someone else on the amd64@ list recently. > Does this imply that the 'correct' fix involves catching the stray ICU interrupt via a trap handler? How often do these interrupts happen, and therefore what is the performance consequence to having to handle them? Scott