kern/119332: reboots suddenly irregularly.

Kris Kennaway kris at FreeBSD.org
Fri Jan 4 11:50:03 PST 2008


The following reply was made to PR kern/119332; it has been noted by GNATS.

From: Kris Kennaway <kris at FreeBSD.org>
To: nrgmilk <nrgmilk at gmail.com>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: kern/119332: reboots suddenly irregularly.
Date: Fri, 04 Jan 2008 20:49:49 +0100

 nrgmilk wrote:
 >> Number:         119332
 >> Category:       kern
 >> Synopsis:       reboots suddenly irregularly.
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       medium
 >> Responsible:    freebsd-bugs
 >> State:          open
 >> Quarter:        
 >> Keywords:       
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Fri Jan 04 13:10:01 UTC 2008
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     nrgmilk
 >> Release:        FreeBSD 7.0-PRERELEASE
 >> Organization:
 > null
 >> Environment:
 > FreeBSD www.vixi.us 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Mon Dec 24 04:10:38 JST 2007     root at www.vixi.us:/usr/obj/usr/src/sys/ULE  amd64
 >> Description:
 > It came to reboot around in the change of CPU from Athlon64 3700 + to Opteron185 suddenly. About four months ago.
 > 
 > It publishes together because the dump was output this time though neither the log nor the dump were usually output. 
 > 
 > This phenomenon has happened since 6.2. 
 > 
 > ###############################################################################
 > #kgdb /usr/obj/usr/src/sys/ULE/kernel.debug vmcore.1
 > ###############################################################################
 > [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 "amd64-marcel-freebsd".
 > 
 > Unread portion of the kernel message buffer:
 > 
 > 
 > Fatal trap 10: trace trap while in kernel mode
 > cpuid = 0; apic id = 00
 > instruction pointer     = 0x8:0xffffffff8073b01b
 > stack pointer           = 0x10:0xffffffffac257bd0
 > frame pointer           = 0x10:0xffffff00010e8000
 > code segment            = base 0x0, limit 0xfffff, type 0x1b
 >                         = DPL 0, pres 1, long 1, def32 0, gran 1
 > processor eflags        = trace trap, interrupt enabled, IOPL = 2
 > current process         = 12 (idle: cpu0)
 > trap number             = 10
 > panic: trace trap
 > cpuid = 0
 > Uptime: 1d17h23m3s
 > Physical memory: 3443 MB
 > Dumping 452 MB: 437 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 133 117 101 85 69 53 37 21 5
 > 
 > #0  doadump () at pcpu.h:194
 > 194     pcpu.h: No such file or directory.
 >         in pcpu.h
 
 Looks like you forgot to do the most important command when submitting a 
 panic (obtaining a backtrace with 'bt' :-), but the fact that it is the 
 idle process that is panicking, together with your observation that it 
 started immediately after changing the hardware, suggests that it is 
 almost certainly a hardware problem and not a FreeBSD problem.
 
 Kris


More information about the freebsd-bugs mailing list