On Tue, Mar 19, 2013 at 06:34:24PM +0100, David Demelier
wrote:> Hello,
>
> 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
> /usr/src/sys/kern/kern_shutdown.c:448
> #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
> /usr/src/sys/vm/vm_map.c:422
> #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
> /usr/src/sys/amd64/amd64/exception.S:387
> #10 0x0000000800d51c1c in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> (kgdb)
>
> 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?
Interesting timing. Semi-recently (February) src/sys/amd64/amd64/pmap.c
in 9.1-STABLE (not -RELEASE) was modified to increase the information
shown for this specific type of panic. See revision 247079:
http://svnweb.freebsd.org/base/stable/9/sys/amd64/amd64/pmap.c?view=log
I've CC'd Konstantin Belousov (kib@), who should be able to help step
you through getting information out of the crash dump, to help track
down the root cause.
--
| Jeremy Chadwick jdc at koitsu.org |
| UNIX Systems Administrator http://jdc.koitsu.org/ |
| Mountain View, CA, US |
| Making life hard for others since 1977. PGP 4BD6C0CB |