> I have seen the following stack trace at at least a couple of these
> panics. As far as I can tell they might be hardware related or they
> may be related to the68040 pmap interface. Any good ideas are welcome.
> 
> I have "a feeling" that this problem is new since a few weeks, but as
> I have only had the machine for a couple of months, and I have been
> reconfiguring it a couple of times (disk+ram), I have really never
> had it running for extended periods of time -- so my "feeling" is
> not necessarily correct.
> 
> _panic("Bus error trap")
> _trap
> _addrerr(?)
> _pmap_testbit(16d0000,10,83fefc,bc10c,16d0000) + e8
> _pmap_is_modified(16d0000) + c
> _vm_object_page_clean(6c63f00,0,0,0,0) +d4
> _vnode_pager_sync(6bb2000, f1, 6bfe500,0,83ffa81) + 96
> _sys_sync(6bfc500,83ff88,83ff80)+4a
> _syscall(24)+10c
> _trap0()+e

If I'm reading this dump right, we're performing a syscall 0x24
when this problem happens. That's 2x16+4=36 decimal, which is
SYS_sync. So there's a problem when the sync daemon runs.

I can't help much from there.

Take care,

Bill