Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: M2 assertion with today's current
On Wed, Jan 30, 2008 at 08:18:52PM +0100, Matthias Drochner wrote:
> tnn%NetBSD.org@localhost said:
> > My quad xeon box hits this assertion when booting today's current
>
> My core2duo doesn't even get that far:
>
> panic: kmem_poison_check: 0xcb81fc90: 0x00 != 0x48
>
> during autoconf. Still have to find out what that means.
Can you try booting with DEBUG, and see if this catches anything?
boot -d
w debug_freecheck 1
c
I don't know if that check still works but it did about 8 months ago.
Andrew
Home |
Main Index |
Thread Index |
Old Index