Panic : bad pte

David Demelier demelier.david at
Tue Mar 19 17:34:25 UTC 2013


There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can
just say there is a problem in the 9.1-RELEASE because I had no panic
before. What afraid me is that my production server also panic'ed a
few days ago, fortunately it does not appears so often.

This is a panic that happened on my desktop computer, with a graphic
card. The crash usually appears when X starts.

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
panic: bad pte
cpuid = 3
KDB: stack backtrace:
Uptime: 2m31s
Dumping 183 out of 1950 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..96%

Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
#0  doadump (textdump=Variable "textdump" is not available.
) at pcpu.h:224
224     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) bt
#0  doadump (textdump=Variable "textdump" is not available.
) at pcpu.h:224
#1  0x0000000000000004 in ?? ()
#2  0xffffffff8048c156 in kern_reboot (howto=260) at
#3  0xffffffff8048c619 in panic (fmt=0x1 <Address 0x1 out of bounds>)
at /usr/src/sys/kern/kern_shutdown.c:636
#4  0xffffffff8065f88a in pmap_remove_pages (pmap=0xfffffe0005a2fa60)
at /usr/src/sys/amd64/amd64/pmap.c:4156
#5  0xffffffff8063d26b in vmspace_exit (td=0xfffffe0005a05470) at
#6  0xffffffff8045d725 in exit1 (td=0xfffffe0005a05470, rv=Variable
"rv" is not available.
) at /usr/src/sys/kern/kern_exit.c:315
#7  0xffffffff8045e5ce in sys_sys_exit (td=Variable "td" is not available.
) at /usr/src/sys/kern/kern_exit.c:122
#8  0xffffffff8066737f in amd64_syscall (td=0xfffffe0005a05470,
traced=0) at subr_syscall.c:135
#9  0xffffffff80652d97 in Xfast_syscall () at
#10 0x0000000800d51c1c in ?? ()
Previous frame inner to this frame (corrupt stack?)

Of course I may do something wrong, and I hope so but unfortunately I
can't find any solution. May the nvidia driver be the problem?

Kind regards

Demelier David

More information about the freebsd-stable mailing list