Sun, Mar 18, 2001 at 16:41:03, des (Dag-Erling Smorgrav) wrote about "Interesting
backtrace...":
> I finally caught a backtrace from one of those recurring stack smash
> panics. I've been getting a few of these every day for a couple of
> weeks now but never caught a dump; I caught this one by typing 'panic'
> immediately instead of trying to get a trace at the ddb prompt first.
[...]
> #11 0xffff037f in ?? ()
> #12 0xc023c8bb in vm_fault (map=0xd0768a00, vaddr=138502144,
> fault_type=2 '\002', fault_flags=8) at ../../vm/vm_page.h:493
I seen a bunch of identical panics on my home system (5.0-current
of ~2001.02.27.22.10.00 UTC).
I did not reported them yet because of lack of understanding
what's happen because pmap_zero_page() call is occured in vm_fault()
without this call in source code ;|
> Looks to me like there was a page fault, and the stack got corrupted
> while handling that fault (possibly somewhere in pmap_zero_page(),
> called from vm_page_zero_fill() which is inlined in vm_fault()).
> (BTW, this is a K6-2, which as far as I can tell is a 586-class CPU)
The same, K6-2:
CPU: AMD-K6(tm) 3D processor (298.96-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x58c Stepping = 12
Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>
AMD Features=0x80000800<SYSCALL,3DNow!>
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
