From owner-freebsd-sparc64@FreeBSD.ORG Wed Aug 18 17:22:32 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92A8E16A4CE for ; Wed, 18 Aug 2004 17:22:32 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A53D43D1F for ; Wed, 18 Aug 2004 17:22:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.2.73] (cpe.125.wat.v126.packetworks.net [64.235.97.125] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i7IHMmV3064950; Wed, 18 Aug 2004 11:22:48 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <41238FB0.9000909@samsco.org> Date: Wed, 18 Aug 2004 11:19:44 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Smith References: <200408170909.i7H99taL082002@postoffice.e-easy.com.au> <20040817115518.W68839@ury.york.ac.uk> <20040818010554.GB5194@electra.cse.Buffalo.EDU> In-Reply-To: <20040818010554.GB5194@electra.cse.Buffalo.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Chris Knight cc: sparc64@freebsd.org Subject: HEADS UP [Re: Insta-panic with recent -current on Ultra10] X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 17:22:32 -0000 All, This is likely my fault, not Soeren's. I'm going to try to fix it the right way before BETA1 rather than ask Soeren to re-add the ugly fix-up code. Scott Ken Smith wrote: > On Tue, Aug 17, 2004 at 11:56:11AM +0100, Gavin Atkinson wrote: > >>On Tue, 17 Aug 2004, Chris Knight wrote: >> >>>I'm getting the following panic on a kernel built from CURRENT >>>as of 17/08/2004 0100 AEST (+10). >>>A kernel from the 13/08/2004 0100 AEST (+10) works fine. >>>In the process of rebuilding the kernel so I can get some more >>>details... >> >>I've seen exactly this panic from a kernel dated 15th. Just another >>datapoint. > > > Ok, I can reproduce this on a kernel from today: > > acd0: CDRW at ata3-master PIO4 > Mounting root from ufs:/dev/ad0a > IOMMU fault virtual address 0xc0620000 > panic: pcib: uncorrectable DMA error AFAR 0x3f867880 AFSR 0x270000ff00000000 > cpuid = 0; > KDB: enter: panic > [thread 100042] > Stopped at kdb_enter+0x38: ta %xcc, 1 > db> tr > panic() at panic+0x1a8 > psycho_ue() at psycho_ue+0x60 > intr_fast() at intr_fast+0x88 > -- interrupt level=0xd pil=0 %o7=0xc02b474c -- > spitfire_block_zero() at spitfire_block_zero+0x74 > vm_pagezero() at vm_pagezero+0x1b8 > fork_exit() at fork_exit+0x9c > fork_trampoline() at fork_trampoline+0x8 > db> > > And a kernel from the 10th does not appear to have the problem. I'll > do a little playing with CVS to see if I can locate exactly what commit > does it. >