Re: Panic on 6.1-RELEASE-p3

2006-12-06 Thread Anthony Chavez
Anthony Chavez [EMAIL PROTECTED] writes:

 John Baldwin [EMAIL PROTECTED] writes:

 On Thursday 02 November 2006 15:19, Anthony Chavez wrote:
 freebsd-hackers:
 
 I have attached the backtraces of 17 core dumps from one of my
 machines.  I have several deployments of this same FreeBSD version in
 the wild, and this is the only machine exhibiting this behavior.
 
 Initially, the cause of these panics seemed to be related to some
 component in the FreeBSD toolchain, as they would occur when
 attempting to install a port.  net/samba3 was the one we'd usually
 test with, but the system would panic with most other larger packages
 as well.
 
 However, the system is panicking at irrgeular intervals, ranging
 between 1-3 weeks apart.  This is mostly happening in the off-hours
 when no human users are actively using the machine, but there have
 been 1 or 2 incidences where the machine has panicked during prime
 time.

 Have you ran a memory checker or other diags to check for failing hardware?

 I ran sysutils/memtest twice.  Both times, it failed to panic the
 system.  I have yet to bring the system down and boot into a real
 memory/hardware checker, however.  I usually just go with
 ultimatebootcd.com when testing, but if you have other suggestions for
 tools, I'd welcome your input before we schedule to do the testing.

Rather than pay us to debug the problem, our client opted to simply
replace the memory, and it only took them 17 more panics to move on
it until it started becoming a daily issue.

What follows is yet another backtrace from a panic that occurred after
about 20.5 hours of uptime.

I would appreciate any further assistance in addressing this problem.

-- 
Anthony Chavez http://anthonychavez.org/
mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]

mybox% kgdb /usr/obj/usr/src/sys/WITFW/kernel.debug vmcore.37
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: 
Undefined symbol ps_pglobal_lookup]
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:
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc06809c4
stack pointer   = 0x28:0xe9606bb4
frame pointer   = 0x28:0xe9606bbc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 42888 (nagios)
trap number = 12
panic: page fault
Uptime: 20h27m59s
Dumping 1023 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 1023MB (261808 pages) 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:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) backtrace
#0  doadump () at pcpu.h:165
#1  0xc065ff79 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:402
#2  0xc0660240 in panic (fmt=0xc08b378a %s)
at /usr/src/sys/kern/kern_shutdown.c:558
#3  0xc087a09e in trap_fatal (frame=0xe9606b74, eva=0)
at /usr/src/sys/i386/i386/trap.c:836
#4  0xc087979a in trap (frame=
  {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -987783168, tf_esi = 0, 
tf_ebp = -379556932, tf_isp = -379556960, tf_ebx = -985433088, tf_edx = 
-985433088, tf_ecx = -985433088, tf_eax = 4, tf_trapno = 12, tf_err = 0, tf_eip 
= -1066923580, tf_cs = 32, tf_eflags = 65539, tf_esp = 0, tf_ss = -987818712})
at /usr/src/sys/i386/i386/trap.c:269
#5  0xc08689aa in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6  0xc06809c4 in turnstile_broadcast (ts=0x0)
at /usr/src/sys/kern/subr_turnstile.c:717
#7  0xc0657587 in _mtx_unlock_sleep (m=0xc51f1528, opts=0, file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:676
#8  0xc07fef0c in vnode_pager_lock (first_object=0xc5dcfa50)
at /usr/src/sys/vm/vnode_pager.c:1198
#9  0xc07eb572 in vm_fault (map=0xc591da8c, vaddr=134918144, 
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:299
#10 0xc0879cff in trap_pfault (frame=0xe9606d38, usermode=1, eva=134921272)
at /usr/src/sys/i386/i386/trap.c:721
#11 0xc087988f in trap (frame=
  {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134921272, tf_esi = 
672508804, tf_ebp = -1077961820, tf_isp = -379556508, tf_ebx = 671912920, 
tf_edx = 0, tf_ecx = 134534302, tf_eax = 671941632

Re: Panic on 6.1-RELEASE-p3

2006-11-03 Thread Anthony Chavez
John Baldwin [EMAIL PROTECTED] writes:

 On Thursday 02 November 2006 15:19, Anthony Chavez wrote:
 freebsd-hackers:
 
 I have attached the backtraces of 17 core dumps from one of my
 machines.  I have several deployments of this same FreeBSD version in
 the wild, and this is the only machine exhibiting this behavior.
 
 Initially, the cause of these panics seemed to be related to some
 component in the FreeBSD toolchain, as they would occur when
 attempting to install a port.  net/samba3 was the one we'd usually
 test with, but the system would panic with most other larger packages
 as well.
 
 However, the system is panicking at irrgeular intervals, ranging
 between 1-3 weeks apart.  This is mostly happening in the off-hours
 when no human users are actively using the machine, but there have
 been 1 or 2 incidences where the machine has panicked during prime
 time.

 Have you ran a memory checker or other diags to check for failing hardware?

I ran sysutils/memtest twice.  Both times, it failed to panic the
system.  I have yet to bring the system down and boot into a real
memory/hardware checker, however.  I usually just go with
ultimatebootcd.com when testing, but if you have other suggestions for
tools, I'd welcome your input before we schedule to do the testing.

Thanks!

-- 
Anthony Chavez http://anthonychavez.org/
mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]


pgpUk85xiUWr2.pgp
Description: PGP signature


Panic on 6.1-RELEASE-p3

2006-11-02 Thread Anthony Chavez
freebsd-hackers:

I have attached the backtraces of 17 core dumps from one of my
machines.  I have several deployments of this same FreeBSD version in
the wild, and this is the only machine exhibiting this behavior.

Initially, the cause of these panics seemed to be related to some
component in the FreeBSD toolchain, as they would occur when
attempting to install a port.  net/samba3 was the one we'd usually
test with, but the system would panic with most other larger packages
as well.

However, the system is panicking at irrgeular intervals, ranging
between 1-3 weeks apart.  This is mostly happening in the off-hours
when no human users are actively using the machine, but there have
been 1 or 2 incidences where the machine has panicked during prime
time.

I would greatly appreciate any assistance that I can get with this.

-- 
Anthony Chavez http://anthonychavez.org/
mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]



backtraces.txt.gz
Description: Binary data


pgpWZ6iIX1Ns5.pgp
Description: PGP signature