r348750 amd64 panic: bad pte va 8002de000 pte 8002de000

2019-06-25 Thread Andriy Gapon
One of remote systems got this panic. Unfortunately, all I have is this bit of its console log. No crash dump (not even a text dump). It's curious that va == pte. panic: bad pte va 8002de000 pte 8002de000^M cpuid = 0^M time = 1561459522^M KDB: stack backtrace:^M db_trace_self_wrapper

trying /sbin/init = panic: bad pte

2010-09-04 Thread David O'Brien
to mount root from ufs:/dev/ad8s1a ct_to_ts([2010-09-03 23:27:18]) = 1283556438.0 start_init: trying /sbin/init panic: bad pte cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at 0x802050aa = db_trace_self_wrapper+0x2a panic() at 0x805da702 = panic+0x182 pmap_remove_pages

Re: trying /sbin/init = panic: bad pte

2010-09-04 Thread David O'Brien
On Fri, Sep 03, 2010 at 11:34:10PM -0700, David O'Brien (@FreeBSD) wrote: This happens on AMD64 for me, r212166 (2010-09-02 15:37:13 -0700) kernel sources. Sorry for the false alarm - this was a local environment problem. -- David ___

panic: bad pte

2003-11-11 Thread Igor Sysoev
I have core dump caused by panic: bad pte on FreeBSD 5.1-CURRENT SMP cvsuped on date=2003.11.04.02.02.00. System runs make -j 64 buildworld in a cycle and sometimes paniced with message bad pte. - Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address

panic: bad pte

2003-06-10 Thread Fred Souza
Hello, I experienced this panic few hours ago, but couldn't debug it back then (the kernel that crashed has no debugging stuff). So here's the only info I could read from the screen when the box hardlocked: TPTE at 0xbfefeffc IS ZERO @ VA bfbff000 panic: bad pte syncing

panic: bad pte

2002-09-11 Thread Martin Blapp
) frame 11 #11 0xc02fe2a5 in pmap_remove_pages (pmap=0xc1f97e04, sva=0, eva=3217031168) at /usr/src/sys/i386/i386/pmap.c:2946 2946panic(bad pte); (kgdb) list 2941tpte = *pte; 2942 2943if (tpte == 0) { 2944

Re: panic: bad pte

2002-09-11 Thread Wesley Morgan
=3217031168) at /usr/src/sys/i386/i386/pmap.c:2946 2946panic(bad pte); (kgdb) list 2941tpte = *pte; 2942 2943if (tpte == 0) { 2944printf(TPTE at %p IS ZERO @ VA %08x\n, 2945

Re: panic: bad pte

2002-09-11 Thread Martin Blapp
Hi, A method to crash current is the following: cd /usr/ports/editors/openoffice make extract# does use about 500M diskspace rm -rfd work# removes everything make# create it again I had more panics

panic: bad pte

2002-02-26 Thread jgranden
I got the following panic while building X with today's current: TPTE at 0xbfc201a0 IS ZERO @ VA 08068000 panic: bad pte db trace Debugger(x029a31b) at Debugger+0x40 panic(c02b617f,c02b6160,bfc201a0,8068000,d909fa00) at panic+0x70 pmap_remove_pages(d909fa6c,0,bfc0,d8e3bd20,d8d81e00

Re: panic: bad pte

2002-02-26 Thread Peter Wemm
[EMAIL PROTECTED] wrote: I got the following panic while building X with today's current: TPTE at 0xbfc201a0 IS ZERO @ VA 08068000 panic: bad pte I've had this about an hour ago too. I'm looking at it right now.. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL