HEADS UP [Re: Insta-panic with recent -current on Ultra10]

Scott Long scottl at samsco.org
Wed Aug 18 10:22:32 PDT 2004


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


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
>>I've seen exactly this panic from a kernel dated 15th. Just another
> Ok, I can reproduce this on a kernel from today:
> acd0: CDRW <CRD-8322B/1.06> 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.

More information about the freebsd-sparc64 mailing list