[Bug 193388] [panic] bad pte

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388

Eitan Adler  changed:

   What|Removed |Added

 Status|In Progress |Open

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193388] [panic] bad pte

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388

Eitan Adler  changed:

   What|Removed |Added

 Resolution|--- |Not Enough Information
 Status|Open|Closed

--- Comment #3 from Eitan Adler  ---
The PTE code has changed drastically since this was reported, and it was likely
a hardware fault in the first place.

Closing unless we get more information.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193388] [panic] bad pte

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388

--- Comment #2 from Eitan Adler  ---
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "b...@freebsd.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Panic : bad pte

[David Demelier]

Le mercredi 20 mars 2013 20:09:42 David Demelier a écrit :
 2013/3/19 Jeremy Chadwick j...@koitsu.org:
  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  0x0004 in ?? ()
  #2  0x8048c156 in kern_reboot (howto=260) at
  /usr/src/sys/kern/kern_shutdown.c:448
  #3  0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds)
  at /usr/src/sys/kern/kern_shutdown.c:636
  #4  0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60)
  at /usr/src/sys/amd64/amd64/pmap.c:4156
  #5  0x8063d26b in vmspace_exit (td=0xfe0005a05470) at
  /usr/src/sys/vm/vm_map.c:422
  #6  0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable
  rv is not available.
  ) at /usr/src/sys/kern/kern_exit.c:315
  #7  0x8045e5ce in sys_sys_exit (td=Variable td is not
  available.
  ) at /usr/src/sys/kern/kern_exit.c:122
  #8  0x8066737f in amd64_syscall (td=0xfe0005a05470,
  traced=0) at subr_syscall.c:135
  #9  0x80652d97 in Xfast_syscall () at
  /usr/src/sys/amd64/amd64/exception.S:387
  #10 0x000800d51c1c 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   j...@koitsu.org |
  | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
  | Mountain View, CA, US|
  | Making life hard for others since 1977. PGP 4BD6C0CB |
 
 You will not believe that, when I leave the desktop. I completely
 detach the AC adaptor (usually at evening). And everyday when I plug
 it and start the machine it panics. But when it reboots and start
 again no panic anymore. I just can't believe it.
 
 The panic is completely different from yesterday's one :
 
 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address   = 0x8010
 fault code  = supervisor read data, page not present
 instruction pointer = 0x20:0x8049db4e
 stack pointer   = 0x28:0xff8000225a90
 frame pointer   = 0x28:0xfe000247c8e0
 code segment= base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags= resume, IOPL = 0
 current process = 10 (idle: cpu0)
 trap number = 12
 panic: page fault
 cpuid = 0
 KDB: stack backtrace:
 Uptime: 1m3s
 Dumping 324 out of 1950 MB:..5%..15%..25%..35%..45%..55%..65%..74%..84%..94%
 
 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  0x0004 in ?? ()
 #2  0x80489506 in kern_reboot (howto=260) at
 /usr/src/sys/kern/kern_shutdown.c:448
 #3  0x804899c9 in panic (fmt=0x1 Address 0x1 out of bounds)
 at /usr/src/sys/kern

Re: Panic : bad pte

[David Demelier]

2013/3/19 Jeremy Chadwick j...@koitsu.org:
 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  0x0004 in ?? ()
 #2  0x8048c156 in kern_reboot (howto=260) at
 /usr/src/sys/kern/kern_shutdown.c:448
 #3  0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds)
 at /usr/src/sys/kern/kern_shutdown.c:636
 #4  0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60)
 at /usr/src/sys/amd64/amd64/pmap.c:4156
 #5  0x8063d26b in vmspace_exit (td=0xfe0005a05470) at
 /usr/src/sys/vm/vm_map.c:422
 #6  0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable
 rv is not available.
 ) at /usr/src/sys/kern/kern_exit.c:315
 #7  0x8045e5ce in sys_sys_exit (td=Variable td is not available.
 ) at /usr/src/sys/kern/kern_exit.c:122
 #8  0x8066737f in amd64_syscall (td=0xfe0005a05470,
 traced=0) at subr_syscall.c:135
 #9  0x80652d97 in Xfast_syscall () at
 /usr/src/sys/amd64/amd64/exception.S:387
 #10 0x000800d51c1c 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   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Mountain View, CA, US|
 | Making life hard for others since 1977. PGP 4BD6C0CB |

You will not believe that, when I leave the desktop. I completely
detach the AC adaptor (usually at evening). And everyday when I plug
it and start the machine it panics. But when it reboots and start
again no panic anymore. I just can't believe it.

The panic is completely different from yesterday's one :

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x8010
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x8049db4e
stack pointer   = 0x28:0xff8000225a90
frame pointer   = 0x28:0xfe000247c8e0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 10 (idle: cpu0)
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
Uptime: 1m3s
Dumping 324 out of 1950 MB:..5%..15%..25%..35%..45%..55%..65%..74%..84%..94%

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  0x0004 in ?? ()
#2  0x80489506 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:448
#3  0x804899c9 in panic (fmt=0x1 Address 0x1 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:636
#4  0x80664e39 in trap_fatal (frame=0xc, eva=Variable eva is
not available.
) at /usr/src/sys/amd64/amd64/trap.c:857
#5  0x806651c4 in trap_pfault (frame

Panic : bad pte

[David Demelier]

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  0x0004 in ?? ()
#2  0x8048c156 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:448
#3  0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:636
#4  0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60)
at /usr/src/sys/amd64/amd64/pmap.c:4156
#5  0x8063d26b in vmspace_exit (td=0xfe0005a05470) at
/usr/src/sys/vm/vm_map.c:422
#6  0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable
rv is not available.
) at /usr/src/sys/kern/kern_exit.c:315
#7  0x8045e5ce in sys_sys_exit (td=Variable td is not available.
) at /usr/src/sys/kern/kern_exit.c:122
#8  0x8066737f in amd64_syscall (td=0xfe0005a05470,
traced=0) at subr_syscall.c:135
#9  0x80652d97 in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:387
#10 0x000800d51c1c 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?

Kind regards

--
Demelier David
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Panic : bad pte

[Jeremy Chadwick]

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  0x0004 in ?? ()
 #2  0x8048c156 in kern_reboot (howto=260) at
 /usr/src/sys/kern/kern_shutdown.c:448
 #3  0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds)
 at /usr/src/sys/kern/kern_shutdown.c:636
 #4  0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60)
 at /usr/src/sys/amd64/amd64/pmap.c:4156
 #5  0x8063d26b in vmspace_exit (td=0xfe0005a05470) at
 /usr/src/sys/vm/vm_map.c:422
 #6  0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable
 rv is not available.
 ) at /usr/src/sys/kern/kern_exit.c:315
 #7  0x8045e5ce in sys_sys_exit (td=Variable td is not available.
 ) at /usr/src/sys/kern/kern_exit.c:122
 #8  0x8066737f in amd64_syscall (td=0xfe0005a05470,
 traced=0) at subr_syscall.c:135
 #9  0x80652d97 in Xfast_syscall () at
 /usr/src/sys/amd64/amd64/exception.S:387
 #10 0x000800d51c1c 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   j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

today's 8.1/i386: panic: bad pte

[Mikhail T.]

Some part of KDE4's kdm crashed at start-up and seems to have taken the 
entire machine with it:


   kgdb /boot/kernel/kernel /var/crash/vmcore.22
   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 i386-marcel-freebsd...

   Unread portion of the kernel message buffer:
   6pid 18398 (drkonqi), uid 0: exited on signal 11 (core dumped)
   TPTE at 0xbfca9488  IS ZERO @ VA 2a522000
   panic: bad pte
   Uptime: 2h28m24s
   Physical memory: 1263 MB
   Dumping 195 MB: 180 164 148 132 116 100 84 68 52 36 20 4

   Reading symbols from /boot/kernel/splash_pcx.ko...Reading symbols
   from /boot/kernel/splash_pcx.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/splash_pcx.ko
   Reading symbols from /boot/kernel/vesa.ko...Reading symbols from
   /boot/kernel/vesa.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/vesa.ko
   Reading symbols from /boot/modules/nvidia.ko...done.
   Loaded symbols for /boot/modules/nvidia.ko
   Reading symbols from /boot/kernel/linux.ko...Reading symbols from
   /boot/kernel/linux.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/linux.ko
   Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
   /boot/kernel/acpi.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/acpi.ko
   Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols
   from /boot/kernel/linprocfs.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/linprocfs.ko
   #0  doadump () at pcpu.h:231
   231 __asm __volatile(movl %%fs:0,%0 : =r (td));
   (kgdb) bt full
   #0  doadump () at pcpu.h:231
   No locals.
   #1  0xc05d10a4 in boot (howto=260) at
   /usr/src/sys/kern/kern_shutdown.c:416
_giantcnt = Variable _giantcnt is not available.
   (kgdb) where
   #0  doadump () at pcpu.h:231
   #1  0xc05d10a4 in boot (howto=260) at
   /usr/src/sys/kern/kern_shutdown.c:416
   #2  0xc05d12b1 in panic (fmt=Variable fmt is not available.
   ) at /usr/src/sys/kern/kern_shutdown.c:590
   #3  0xc07f0406 in pmap_remove_pages (pmap=0xc85bbc78) at
   /usr/src/sys/i386/i386/pmap.c:4198
   #4  0xc079516b in vmspace_exit (td=0xc51f3a00) at
   /usr/src/sys/vm/vm_map.c:409
   #5  0xc05a7253 in exit1 (td=0xc51f3a00, rv=139) at
   /usr/src/sys/kern/kern_exit.c:303
   #6  0xc05d3296 in sigexit (td=0xc51f3a00, sig=139) at
   /usr/src/sys/kern/kern_sig.c:2872
   #7  0xc05d47a8 in postsig (sig=11) at /usr/src/sys/kern/kern_sig.c:2759
   #8  0xc06082f8 in ast (framep=0xe5fafd38) at
   /usr/src/sys/kern/subr_trap.c:234
   #9  0xc07e2c44 in doreti_ast () at
   /usr/src/sys/i386/i386/exception.s:368

Does this look familiar to anyone? Thanks!

   -mi

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: today's 8.1/i386: panic: bad pte

[Alan Cox]

On Mon, Jul 19, 2010 at 11:40 PM, Mikhail T.
mi+t...@aldan.algebra.commi%2bt...@aldan.algebra.com
 wrote:

 Some part of KDE4's kdm crashed at start-up and seems to have taken the
 entire machine with it:

   kgdb /boot/kernel/kernel /var/crash/vmcore.22
   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 i386-marcel-freebsd...

   Unread portion of the kernel message buffer:
   6pid 18398 (drkonqi), uid 0: exited on signal 11 (core dumped)
   TPTE at 0xbfca9488  IS ZERO @ VA 2a522000
   panic: bad pte
   Uptime: 2h28m24s
   Physical memory: 1263 MB
   Dumping 195 MB: 180 164 148 132 116 100 84 68 52 36 20 4

   Reading symbols from /boot/kernel/splash_pcx.ko...Reading symbols
   from /boot/kernel/splash_pcx.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/splash_pcx.ko
   Reading symbols from /boot/kernel/vesa.ko...Reading symbols from
   /boot/kernel/vesa.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/vesa.ko
   Reading symbols from /boot/modules/nvidia.ko...done.
   Loaded symbols for /boot/modules/nvidia.ko
   Reading symbols from /boot/kernel/linux.ko...Reading symbols from
   /boot/kernel/linux.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/linux.ko
   Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
   /boot/kernel/acpi.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/acpi.ko
   Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols
   from /boot/kernel/linprocfs.ko.symbols...done.
   done.
   Loaded symbols for /boot/kernel/linprocfs.ko
   #0  doadump () at pcpu.h:231
   231 __asm __volatile(movl %%fs:0,%0 : =r (td));
   (kgdb) bt full
   #0  doadump () at pcpu.h:231
   No locals.
   #1  0xc05d10a4 in boot (howto=260) at
   /usr/src/sys/kern/kern_shutdown.c:416
_giantcnt = Variable _giantcnt is not available.
   (kgdb) where
   #0  doadump () at pcpu.h:231
   #1  0xc05d10a4 in boot (howto=260) at
   /usr/src/sys/kern/kern_shutdown.c:416
   #2  0xc05d12b1 in panic (fmt=Variable fmt is not available.
   ) at /usr/src/sys/kern/kern_shutdown.c:590
   #3  0xc07f0406 in pmap_remove_pages (pmap=0xc85bbc78) at
   /usr/src/sys/i386/i386/pmap.c:4198
   #4  0xc079516b in vmspace_exit (td=0xc51f3a00) at
   /usr/src/sys/vm/vm_map.c:409
   #5  0xc05a7253 in exit1 (td=0xc51f3a00, rv=139) at
   /usr/src/sys/kern/kern_exit.c:303
   #6  0xc05d3296 in sigexit (td=0xc51f3a00, sig=139) at
   /usr/src/sys/kern/kern_sig.c:2872
   #7  0xc05d47a8 in postsig (sig=11) at /usr/src/sys/kern/kern_sig.c:2759
   #8  0xc06082f8 in ast (framep=0xe5fafd38) at
   /usr/src/sys/kern/subr_trap.c:234
   #9  0xc07e2c44 in doreti_ast () at
   /usr/src/sys/i386/i386/exception.s:368

 Does this look familiar to anyone? Thanks!


Historically, this panic has indicated flakey memory.  This panic occurs
because a memory location within a page table has unexpectedly changed to
zero.

Alan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: today's 8.1/i386: panic: bad pte

[Alan Cox]

Mikhail T. wrote:

20.07.2010 12:47, Alan Cox написав(ла):
Historically, this panic has indicated flakey memory.  This panic 
occurs because a memory location within a page table has unexpectedly 
changed to zero.
Ouch... Thanks for the hint (maybe, the panic should say something 
like that?)


In any case, is there a way to identify the the flakey DIMM? I did run 
memtest on this box and haven't received any errors... Thanks! Yours,


No, not from the panic message.  If a thorough memtest didn't turn up a 
problem, then I would start looking for another cause.


Alan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: today's 8.1/i386: panic: bad pte

[Mikhail T.]

20.07.2010 12:47, Alan Cox написав(ла):
Historically, this panic has indicated flakey memory.  This panic 
occurs because a memory location within a page table has unexpectedly 
changed to zero.
Ouch... Thanks for the hint (maybe, the panic should say something like 
that?)


In any case, is there a way to identify the the flakey DIMM? I did run 
memtest on this box and haven't received any errors... Thanks! Yours,


   -mi

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: panic: bad pte

[John Baldwin]

On Wednesday 23 January 2008 05:17:41 pm Mikhail Teterin wrote:
 середа 23 січень 2008 03:45 по, John Baldwin Ви написали:
   In the controller? It is a newish ahd (although from eBay) -- what could
   be wrong?
 
  RAM.
 
 Ouch... You mean, the main computer RAM or the controller's own memory?
 
 The box itself is from a reputable workstation-maker and is otherwise 
 functioning perfectly. Yet it had two pte-panics within 24-hours from each 
 other (I reported the first one).

system ram.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: bad pte

[Phillip N.]

El jue, 24-01-2008 a las 13:56 -0500, John Baldwin escribió:
 system ram.

I saw similar things on high load on my old NF4-Ultra based motherboard.
Its in the trash now...

:)


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: bad pte

[John Baldwin]

On Sunday 20 January 2008 11:57:29 am Mikhail Teterin wrote:
 Hello!
 
 Is this something, that should be fixed in the 6.3? The kernel is 6.2-STABLE 
 from June (see uptime).
 
 Thanks!

What kind of CPU?  There was a fix for a certain edge condition in 6.x post
6.2, but usually when I see this panic it is due to a hardware failure.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: bad pte

[Mikhail Teterin]

середа 23 січень 2008 09:20 до, John Baldwin Ви написали:
  Is this something, that should be fixed in the 6.3? The kernel is
  6.2-STABLE from June (see uptime).

 What kind of CPU?

Dual Opteron. FreeBSD/amd64.

 There was a fix for a certain edge condition in 6.x post 6.2, but usually
 when I see this panic it is due to a hardware failure.

In the controller? It is a newish ahd (although from eBay) -- what could be 
wrong?

Thanks!

 -mi
##
The information contained in this communication is confidential and
may contain information that is privileged or exempt from disclosure
under applicable law. If you are not a named addressee, please notify
the sender immediately and delete this email from your system.
If you have received this communication, and are not a named
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
##
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: bad pte

[John Baldwin]

On Wednesday 23 January 2008 11:56:02 am Mikhail Teterin wrote:
 середа 23 січень 2008 09:20 до, John Baldwin Ви написали:
   Is this something, that should be fixed in the 6.3? The kernel is
   6.2-STABLE from June (see uptime).
 
  What kind of CPU?
 
 Dual Opteron. FreeBSD/amd64.
 
  There was a fix for a certain edge condition in 6.x post 6.2, but usually
  when I see this panic it is due to a hardware failure.
 
 In the controller? It is a newish ahd (although from eBay) -- what could be 
 wrong?

RAM.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic: bad pte

[Mikhail Teterin]

середа 23 січень 2008 03:45 по, John Baldwin Ви написали:
  In the controller? It is a newish ahd (although from eBay) -- what could
  be wrong?

 RAM.

Ouch... You mean, the main computer RAM or the controller's own memory?

The box itself is from a reputable workstation-maker and is otherwise 
functioning perfectly. Yet it had two pte-panics within 24-hours from each 
other (I reported the first one).

Thanks!

 -mi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

panic: bad pte

[Mikhail Teterin]

Hello!

Is this something, that should be fixed in the 6.3? The kernel is 6.2-STABLE 
from June (see uptime).

Thanks!

-mi

Unread portion of the kernel message buffer:
TPTE at 0x8038  IS ZERO @ VA 7000
panic: bad pte
cpuid = 1
Uptime: 133d0h42m22s
Dumping 3583 MB (2 chunks)
  chunk 0: 1MB (151 pages) ... ok
  chunk 1: 3583MB (917104 pages)panic: ahd_run_qoutfifo recursion
cpuid = 1
 3567 3551 3535 3519 3503 3487 3471 3455 3439 3423 3407 3391 3375 3359 3343 
3327 3311 3295 3279 3263 3247 3231 3215 3199 3183 3167 3151 3135 3119 3103 3087 
3071 3055 3039 3023 3007 2991 2975 2959 2943 2927 2911 2895 2879 2863 2847 2831 
2815 2799 2783 2767 2751 2735 2719 2703 2687 2671 2655 2639 2623 2607 2591 2575 
2559 2543 2527 2511 2495 2479 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 
2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 
2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 
1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 
1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 
1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 
719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 
399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 
79 63 47 31 15

#0  doadump () at pcpu.h:172
172 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) #0  doadump () at pcpu.h:172
#1  0x0004 in ?? ()
#2  0x8028fa27 in boot (howto=260)
at /var/src/sys/kern/kern_shutdown.c:409
#3  0x802900c1 in panic (fmt=0xff00567ba260 )
at /var/src/sys/kern/kern_shutdown.c:565
#4  0x803c03d8 in pmap_remove_pages (pmap=0xff0051ab7c00, sva=0, 
eva=140737488355328) at /var/src/sys/amd64/amd64/pmap.c:2746
#5  0x8026f963 in exec_new_vmspace (imgp=0x0, sv=0x805a99e0)
at vm_map.h:251
#6  0x80257577 in exec_elf64_imgact (imgp=0xb745b9e0)
at /var/src/sys/kern/imgact_elf.c:668
#7  0x802701ec in kern_execve (td=0xff00567ba260, 
args=0xb745bb30, mac_p=0x0) at /var/src/sys/kern/kern_exec.c:426
#8  0x80270d6f in execve (td=0xff00567ba260, uap=0x0)
at /var/src/sys/kern/kern_exec.c:188
#9  0x803c8571 in syscall (frame=
  {tf_rdi = 140737488349781, tf_rsi = 140737488349224, tf_rdx = 
140737488349240, tf_rcx = 0, tf_r8 = 34367075043, tf_r9 = 11, tf_rax = 59, 
tf_rbx = 140737488350300, tf_rbp = 140737488349072, tf_r10 = 31, tf_r11 = 4, 
tf_r12 = 140737488349224, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, 
tf_addr = 34366651872, tf_flags = 0, tf_err = 2, tf_rip = 34366652876, tf_cs = 
43, tf_rflags = 518, tf_rsp = 140737488347816, tf_ss = 35}) at 
/var/src/sys/amd64/amd64/trap.c:803
#10 0x803afed8 in Xfast_syscall ()
at /var/src/sys/amd64/amd64/exception.S:270
#11 0x0008006981cc in ?? ()
(kgdb) 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

panic: bad pte (releng_7)

[Phillip N.]

Dears,

Today i got the following crash. 
Its a GENERIC kernel, but without firewire, and with ULE. the rest is
intact.

Unread portion of the kernel message buffer:
TPTE at 0x84004c40  IS ZERO @ VA 800988000
panic: bad pte
cpuid = 0
Uptime: 2d3h46m1s
Physical memory: 2036 MB
Dumping 279 MB: 264 248 232 216 200 184 168 152 136 120 104 88 72 56 40
24 8

#0  doadump () at pcpu.h:194
194 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) bt
#0  doadump () at pcpu.h:194
#1  0x0004 in ?? ()
#2  0x8045b9f9 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#3  0x8045bdfd in panic (fmt=0x104 Address 0x104 out of
bounds)
at /usr/src/sys/kern/kern_shutdown.c:563
#4  0x806d2f89 in pmap_remove_pages (pmap=0xff0020df1c58)
at /usr/src/sys/amd64/amd64/pmap.c:2948
#5  0x8066bd78 in vmspace_exit (td=0xff004659a9f0)
at /usr/src/sys/vm/vm_map.c:395
#6  0x8043bebc in exit1 (td=0xff004659a9f0, rv=0)
at /usr/src/sys/kern/kern_exit.c:294
#7  0x8043d26e in sys_exit (td=Variable td is not available.
) at /usr/src/sys/kern/kern_exit.c:98
#8  0x806dddb7 in syscall (frame=0xaeceec70)
at /usr/src/sys/amd64/amd64/trap.c:822
#9  0x806c435b in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:272
#10 0x000800933ccc in ?? ()
Previous frame inner to this frame (corrupt stack?)



What could this be?

this is RELENG_7 from Thu Nov  1 18:04:33 CLST 2007

thanks!


-- 
Phillip N. [EMAIL PROTECTED]

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

'panic: bad pte' error on 6.2-RELEASE (amd64)

[Peter Losher]

We recently updated one of our dual Opteron systems (w/ 4GB RAM) from
5.5 to 6.2 (amd64 wipe and reinstalled) and about once a week, it panics
with the below message:

-=-
TPTE at 0x840028a0  IS ZERO @ VA 800514000
panic: bad pte
cpuid = 2
KDB: stack backtrace:
panic() at 0x803fdd03 = panic+0x253
pmap_remove_pages() at 0x806072a3 = pmap_remove_pages+0x283
exec_new_vmspace() at 0x803e18e6 = exec_new_vmspace+0x216
exec_elf64_imgact() at 0x803cbb73 = exec_elf64_imgact+0x273
kern_execve() at 0x803e2107 = kern_execve+0x457
execve() at 0x803e2bed = execve+0x5d
syscall() at 0x8060d141 = syscall+0x4d1
Xfast_syscall() at 0x805f8128 = Xfast_syscall+0xa8
--- syscall (59, FreeBSD ELF64, execve), rip = 0x80069838c, rsp =
0x7fffe7c8, rbp = 0x7fffecd0 ---
Uptime: 4d16h55m46s
-=-

I do have a dump, and can make that available if need be.  Has anyone
encountered this recently and can shed any light on what might be
causing this?

Best Wishes - Peter



signature.asc
Description: OpenPGP digital signature

Re: 'panic: bad pte' error on 6.2-RELEASE (amd64)

[Kostik Belousov]

On Mon, Mar 05, 2007 at 12:05:32AM -0800, Peter Losher wrote:
 We recently updated one of our dual Opteron systems (w/ 4GB RAM) from
 5.5 to 6.2 (amd64 wipe and reinstalled) and about once a week, it panics
 with the below message:
 
 -=-
 TPTE at 0x840028a0  IS ZERO @ VA 800514000
 panic: bad pte
 cpuid = 2
 KDB: stack backtrace:
 panic() at 0x803fdd03 = panic+0x253
 pmap_remove_pages() at 0x806072a3 = pmap_remove_pages+0x283
 exec_new_vmspace() at 0x803e18e6 = exec_new_vmspace+0x216
 exec_elf64_imgact() at 0x803cbb73 = exec_elf64_imgact+0x273
 kern_execve() at 0x803e2107 = kern_execve+0x457
 execve() at 0x803e2bed = execve+0x5d
 syscall() at 0x8060d141 = syscall+0x4d1
 Xfast_syscall() at 0x805f8128 = Xfast_syscall+0xa8
 --- syscall (59, FreeBSD ELF64, execve), rip = 0x80069838c, rsp =
 0x7fffe7c8, rbp = 0x7fffecd0 ---
 Uptime: 4d16h55m46s
 -=-
 
 I do have a dump, and can make that available if need be.  Has anyone
 encountered this recently and can shed any light on what might be
 causing this?

Did rev. 1.516.2.9 of sys/amd64/amd64/pmap.c changed (or even fixed) the
problem ? (This is the same patch I already sent you).


pgplMx9lBVjjg.pgp
Description: PGP signature

Re: 'panic: bad pte' error on 6.2-RELEASE (amd64)

[Gavin Atkinson]

On Mon, 5 Mar 2007, Kostik Belousov wrote:


On Mon, Mar 05, 2007 at 12:05:32AM -0800, Peter Losher wrote:

We recently updated one of our dual Opteron systems (w/ 4GB RAM) from
5.5 to 6.2 (amd64 wipe and reinstalled) and about once a week, it panics
with the below message:

-=-
TPTE at 0x840028a0  IS ZERO @ VA 800514000
panic: bad pte
cpuid = 2
KDB: stack backtrace:
panic() at 0x803fdd03 = panic+0x253
pmap_remove_pages() at 0x806072a3 = pmap_remove_pages+0x283
exec_new_vmspace() at 0x803e18e6 = exec_new_vmspace+0x216
exec_elf64_imgact() at 0x803cbb73 = exec_elf64_imgact+0x273
kern_execve() at 0x803e2107 = kern_execve+0x457
execve() at 0x803e2bed = execve+0x5d
syscall() at 0x8060d141 = syscall+0x4d1
Xfast_syscall() at 0x805f8128 = Xfast_syscall+0xa8
--- syscall (59, FreeBSD ELF64, execve), rip = 0x80069838c, rsp =
0x7fffe7c8, rbp = 0x7fffecd0 ---
Uptime: 4d16h55m46s
-=-

I do have a dump, and can make that available if need be.  Has anyone
encountered this recently and can shed any light on what might be
causing this?


Did rev. 1.516.2.9 of sys/amd64/amd64/pmap.c changed (or even fixed) the
problem ? (This is the same patch I already sent you).


Do you know if this patch is likely to fix the other bad pte panics that 
have been seen (usually during process exit())?  e.g.


http://docs.freebsd.org/cgi/mid.cgi?1148482556.35287.18.camel
http://lists.freebsd.org/pipermail/freebsd-current/2004-August/034909.html

I have a couple of amd64 machines I'm reluctant to make live until this is 
sorted...  I'll cvsup in the next day or two to see, although it wasn't 
consistantly reproduceable.


Thanks,

Gavin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 'panic: bad pte' error on 6.2-RELEASE (amd64)

[Kostik Belousov]

On Mon, Mar 05, 2007 at 06:28:30PM +, Gavin Atkinson wrote:
 On Mon, 5 Mar 2007, Kostik Belousov wrote:
 
 On Mon, Mar 05, 2007 at 12:05:32AM -0800, Peter Losher wrote:
 We recently updated one of our dual Opteron systems (w/ 4GB RAM) from
 5.5 to 6.2 (amd64 wipe and reinstalled) and about once a week, it panics
 with the below message:
 
 -=-
 TPTE at 0x840028a0  IS ZERO @ VA 800514000
 panic: bad pte
 cpuid = 2
 KDB: stack backtrace:
 panic() at 0x803fdd03 = panic+0x253
 pmap_remove_pages() at 0x806072a3 = pmap_remove_pages+0x283
 exec_new_vmspace() at 0x803e18e6 = exec_new_vmspace+0x216
 exec_elf64_imgact() at 0x803cbb73 = exec_elf64_imgact+0x273
 kern_execve() at 0x803e2107 = kern_execve+0x457
 execve() at 0x803e2bed = execve+0x5d
 syscall() at 0x8060d141 = syscall+0x4d1
 Xfast_syscall() at 0x805f8128 = Xfast_syscall+0xa8
 --- syscall (59, FreeBSD ELF64, execve), rip = 0x80069838c, rsp =
 0x7fffe7c8, rbp = 0x7fffecd0 ---
 Uptime: 4d16h55m46s
 -=-
 
 I do have a dump, and can make that available if need be.  Has anyone
 encountered this recently and can shed any light on what might be
 causing this?
 
 Did rev. 1.516.2.9 of sys/amd64/amd64/pmap.c changed (or even fixed) the
 problem ? (This is the same patch I already sent you).
 
 Do you know if this patch is likely to fix the other bad pte panics that 
 have been seen (usually during process exit())?  e.g.
 
 http://docs.freebsd.org/cgi/mid.cgi?1148482556.35287.18.camel
 http://lists.freebsd.org/pipermail/freebsd-current/2004-August/034909.html
Yes, the problem there seems to be fixed by Tor' commit into the i386/pmap.c
at the 2006/02/16. My commit is MFi386 of the fix to the amd64.

 I have a couple of amd64 machines I'm reluctant to make live until this is 
 sorted...  I'll cvsup in the next day or two to see, although it wasn't 
 consistantly reproduceable.
I am interested in testing results.


pgpM4QJ0xYFHJ.pgp
Description: PGP signature

6.1-RELEASE amd64 panic: bad pte

[Gavin Atkinson]

Hi,

I've just seen the following panic on a dual cpu amd64 box:
FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May  7 04:15:57 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP  amd64

Panic happened during cd /usr/port/databases/mysql4-server  make
install - box was otherwise idle.

TPTE at 0x840028c8  IS ZERO @ VA 800519000
panic: bad pte
cpuid = 1
Uptime: 7d0h12m25s
Dumping 2047 MB (2 chunks)
  chunk 0: 1MB (150 pages) ... ok 
  chunk 1: 2047MB (523888 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 
1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 
1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 
1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 
1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 
831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 
511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 
191 175 159 143 127 111 95 79 63 47 31 15 ... ok
Dump complete

As this is a -RELEASE kernel, no kernel.debug exits.  As an aside, what
happened to the idea of generating these and putting them on the CD or
the ftp site?

(kgdb) bt
#0  0x803d204d in doadump ()
#1  0x803d2074 in doadump ()
#2  0x0004 in ?? ()
#3  0x803d2677 in boot ()
#4  0x0019 in ?? ()
#5  0x0fd2cf65 in ?? ()
#6  0xff005d789260 in ?? ()
#7  0x0104 in ?? ()
#8  0x in ?? ()
Previous frame identical to this frame (corrupt stack?)

# this is the TPTE pointer from the panic printf
(kgdb) x/20 0x840028c8
0x840028c8: Cannot access memory at address 0x840028c8

# This address appears in the backtrace
(kgdb) x/40 0xff005d789260
0xff005d789260: 0x5bf62000  0xff00  0x7b9867e0  
0xff00
0xff005d789270: 0x  0x  0x5bf62020  
0xff00
0xff005d789280: 0x  0x  0x7b9867f8  
0xff00
0xff005d789290: 0x  0x  0x62981a80  
0xff00
0xff005d7892a0: 0x  0x  0xb420b890  
0x
0xff005d7892b0: 0x  0x  0x  
0x
0xff005d7892c0: 0x  0x  0x5d7892c0  
0xff00
0xff005d7892d0: 0x62981a80  0xff00  0x628d8500  
0xff00
0xff005d7892e0: 0x60e06b80  0xff00  0x000186f4  
0x05010002
0xff005d7892f0: 0x  0x  0x  
0x

Pointers to this structure are littered throughout the memory following
the stack pointer - it seems to be a thread pointer.  The first value
(0xff005bf62000) appears to be a pointer to struct proc, but I'm not
sure if there's anything useful that can be found from that either.  The
process was grep, pid 84450, p_flags are P_EXEC|P_WEXIT|P_CONTROLT -
so it happened while the process was exiting, which makes sense given
the panic is called from pmap_remove_pages().  I'm happy to do more
digging if there are any lines of investigation anyone can suggest.


Possibly-relevant bits of dmesg:
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
reserved.
FreeBSD 6.1-RELEASE #0: Sun May  7 04:15:57 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
ACPI APIC Table: PTLTD  APIC  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Opteron(tm) Processor 248 (2193.76-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0xf5a  Stepping = 10
Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
  AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow
real memory  = 2146893824 (2047 MB)
avail memory = 2062053376 (1966 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 1.1 irqs 0-23 on motherboard
ioapic1 Version 1.1 irqs 24-27 on motherboard
ioapic2 Version 1.1 irqs 28-31 on motherboard

I have the coredump available for further analysis if anyone wants it,
but without a debug kernel I appreciate it may not be useful.  I'm going
to compile one up, in case it happens again.

Gavin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]