Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: amd64 kernel crash



--- Paul Goyette <paul%whooppee.com@localhost> wrote:

> Got the following crash on a recent (current as of
> 2008-09-20 21:18:14) 
> 4.99.72 kernel.  Nothing special was happening at
> the time, just a 
> normal 'build.sh -j 8 release'.  Kernel config and
> dmesg are attached.
> 
> This is similar to the "random" crashes that I've
> previously attributed 
> to having "too much memory" (8GB total), but the
> kernel is built with
> 
>       options PHYSMEM_MAX_ADDR=4096
> 
> so that shouldn't be an issue.
> 
> (gdb) bt
> #0  0xffffffff8032ef3a in cpu_reboot (howto=260,
> bootstr=<value 
> optimized out>)
>      at
> /build/src/sys/arch/amd64/amd64/machdep.c:654
> #1  0xffffffff8029999b in panic
> (fmt=0xffffffff804614a0 "trap")
>      at /build/src/sys/kern/subr_prf.c:258
> #2  0xffffffff80330794 in trap
> (frame=0xffff80004d5f9370)
>      at /build/src/sys/arch/amd64/amd64/trap.c:254
> #3  0xffffffff80101002 in calltrap ()
> #4  0xffffffff8029886b in kprintf (fmt0=0x0,
> oflags=Cannot access memory 
> at address 0xffffffffffffff7c)
>      at /build/src/sys/kern/subr_prf.c:1463
> Previous frame inner to this frame (corrupt stack?)
> (gdb)
> 
> Any clues on how to dig deeper into this would be
> appreciated.  I've got 
> the whole 3.2GB dump file...
> 
> 

Why we have a lot of problems with NetBSD/amd64 ?
 

NetBSD is Very JIHBED, JIHEBD it is word arabic == TOP AND POWER INTELLIGENT

http://jihbedunix.blogspot.com


      



Home | Main Index | Thread Index | Old Index