4.8-STABLE kernel crash
Allan Marshall
allan at skene.net
Fri Oct 29 19:06:05 PDT 2004
Ive been through the tuning man pages a few times, everything seems to be ok
However i could be missing something
Im am not tracking the 4.8-STABLE, this is just from some point
here is the full backtrace, any more help is greatly appreciated
bt full
(kgdb) bt full
#0 dumpsys () at ../../kern/kern_shutdown.c:487
error = 0
#1 0xc017c3af in boot (howto=256) at ../../kern/kern_shutdown.c:316
howto = 256
#2 0xc017c7d4 in poweroff_wait (junk=0xc02b182c, howto=-1070918865)
at ../../kern/kern_shutdown.c:595
fmt = 0xc02b182c "%s"
bootopt = 256
buf = "page fault", '\000' <repeats 245 times>
#3 0xc0261e1a in trap_fatal (frame=0xf79ace3c, eva=983060)
at ../../i386/i386/trap.c:974
frame = (struct trapframe *) 0x100
code = -1070917588
type = 12
ss = -1070917588
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27,
ssd_dpl = 0, ssd_p = 1, ssd_xx = 10, ssd_xx1 = 1, ssd_def32 = 1,
ssd_gran = 1}
#4 0xc0261aed in trap_pfault (frame=0xf79ace3c, usermode=0, eva=983060)
at ../../i386/i386/trap.c:867
va = 983040
vm = (struct vmspace *) 0x0
---Type <return> to continue, or q <return> to quit---
map = 0xf79bc640
rv = 0
ftype = 1 '\001'
p = (struct proc *) 0xf7a96780
#5 0xc02616d7 in trap (frame={tf_fs = -1070923760, tf_es = -147914736,
tf_ds = 16973840, tf_edi = 672440320, tf_esi = 227, tf_ebp
= -140849532,
tf_isp = -140849560, tf_ebx = -148367476, tf_edx = 983040,
tf_ecx = 250428367, tf_eax = 524281, tf_trapno = 12, tf_err = 0,
tf_eip = -1071494896, tf_cs = 8, tf_eflags = 66054, tf_esp = 0,
tf_ss = -140786112}) at ../../i386/i386/trap.c:466
p = (struct proc *) 0xf7a96780
sticks = 17841799634098427673
i = 0
ucode = 0
type = 12
code = 0
eva = 983060
#6 0xc0224910 in vm_page_lookup (object=0xf728178c, pindex=227)
at ../../vm/vm_page.c:515
object = 0x0
pindex = 227
m = 0x0
generation = 0
---Type <return> to continue, or q <return> to quit---
#7 0xc021cc70 in vm_fault (map=0xf79bc640, vaddr=672440320,
fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:292
fault_type = 1 '\001'
prot = 5 '\005'
result = 0
wired = 0
map_generation = 89
next_object = 0x0
marray = {0x0, 0xf7a96780, 0xf7a96780, 0xf79bc640, 0x2814a000, 0x0,
0x7, 0x1, 0x0, 0x0, 0x1, 0xf79bc640, 0xf79bc640, 0xf7c28c60, 0xf79acf3c,
0xc0266426}
hardfault = 0
faultcount = 0
fs = {m = 0x1000000, object = 0xf728178c, pindex = 227, first_m =
0x0,
first_object = 0xf728178c, first_pindex = 227, map = 0xf79bc640,
entry = 0xf7c28c60, lookup_still_valid = 1, vp = 0xf72ff800}
#8 0xc0261a82 in trap_pfault (frame=0xf79acfa8, usermode=1, eva=672441792)
at ../../i386/i386/trap.c:847
va = 672440320
vm = (struct vmspace *) 0x0
map = 0xf79bc640
rv = 0
ftype = 1 '\001'
---Type <return> to continue, or q <return> to quit---
p = (struct proc *) 0xf7a96780
#9 0xc02615ab in trap (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 672514096, tf_esi = 0, tf_ebp = -1077937344,
tf_isp = -140849196, tf_ebx = 672505356, tf_edx = 0, tf_ecx =
134533128,
tf_eax = 1008, tf_trapno = 12, tf_err = 4, tf_eip = 672010244,
tf_cs = 31, tf_eflags = 66054, tf_esp = -1077937368, tf_ss = 47})
at ../../i386/i386/trap.c:377
p = (struct proc *) 0xf7a96780
sticks = 1
i = 0
ucode = 0
type = 12
code = 0
eva = 672441792
#10 0x280e1004 in ?? ()
No symbol table info available.
#11 0x280e10bd in ?? ()
No symbol table info available.
#12 0x280e70e5 in ?? ()
No symbol table info available.
#13 0x28085174 in ?? ()
No symbol table info available.
#14 0x8048f66 in ?? ()
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#15 0x8048e4a in ?? ()
No symbol table info available.
----- Original Message -----
From: "Joseph Koshy" <joseph.koshy at gmail.com>
To: "Allan Marshall" <allan at skene.net>
Sent: Friday, October 29, 2004 10:47 PM
Subject: Re: 4.8-STABLE kernel crash
>> The instablity has been for a few months, but prior to that, the box was
>> up
>> over 140 days without a single problem, no hardware changes
>> since. I think i recompiled allowing ipfw after that, but nothing else
>> major.
>
> In the absence of a full backtrace here are some guesses at possible
> problems:
>
> 1) You seem to have 1G of RAM. Please check that you've set the memory
> related loader tunables accordingly. You may want to set the value
> of the kern.maxusers sysctl to below 256. See man tuning(7).
>
> 2) Are you tracking the 4.8 RELEASE branch, or is this kernel from
> some point on 4-STABLE?
>
> Notes: If you are using loadable kernel modules, please ensure
> that the kernel and modules are compiled from the same source
> revisions.
>
> It may be helpful to get a full kernel backtrace from a dump. The
> steps to do obtain this is present in the Handbook.
>
>> dmesg
>> Copyright (c) 1992-2003 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 4.8-STABLE #1: Sun Sep 19 21:04:55 GMT 2004
>> ***********************************
>> Timecounter "i8254" frequency 1193182 Hz
>> CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.61-MHz 686-class CPU)
>> Origin = "GenuineIntel" Id = 0xf27 Stepping = 7
>>
>> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>> real memory = 1072627712 (1047488K bytes)
>> avail memory = 1040183296 (1015804K bytes)
>> Preloaded elf kernel "kernel" at 0xc0362000.
>> Pentium Pro MTRR support enabled
>> md0: Malloc disk
>> Using $PIR table, 7 entries at 0xc00fc8f0
>> npx0: <math processor> on motherboard
>> npx0: INT 16 interface
>> pcib0: <Host to PCI bridge> on motherboard
>> pci0: <PCI bus> on pcib0
>> agp0: <Intel 82845G (845G GMCH) SVGA controller> mem
>> 0xe8100000-0xe817ffff,0xe0000000-0xe7ffffff irq 10 at device 2.0 on pci0
>> agp0: detected 892k stolen memory
>> agp0: aperture size is 128M
>> pcib1: <Intel 82801BA/BAM (ICH2) Hub to PCI bridge> at device 30.0 on
>> pci0
>> pci1: <PCI bus> on pcib1
>> rl0: <RealTek 8139 10/100BaseTX> port 0xc000-0xc0ff mem
>> 0xe8000000-0xe80000ff irq 11 at device 5.0 on pci1
>> rl0: Ethernet address: 00:20:ed:7e:8d:58
>> miibus0: <MII bus> on rl0
>> rlphy0: <RealTek internal media interface> on miibus0
>> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> isab0: <PCI to ISA bridge (vendor=8086 device=24c0)> at device 31.0 on
>> pci0
>> isa0: <ISA bus> on isab0
>> atapci0: <Intel ICH4 ATA100 controller> port
>> 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0
>> ata0: at 0x1f0 irq 14 on atapci0
>> ata1: at 0x170 irq 15 on atapci0
>> pci0: <unknown card> (vendor=0x8086, dev=0x24c3) at 31.3 irq 3
>> fdc0: ready for input in output
>> fdc0: cmd 3 failed at out byte 1 of 3
>> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
>> sc0: <System console> at flags 0x100 on isa0
>> sc0: VGA <16 virtual consoles, flags=0x300>
>> sio0: configured irq 4 not in bitmap of probed irqs 0
>> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
>> sio0: type 8250
>> sio1: configured irq 3 not in bitmap of probed irqs 0
>> DUMMYNET initialized (011031)
>> IP packet filtering initialized, divert disabled, rule-based forwarding
>> enabled, default to accept, logging limited to 10 packets/entry by
>> default
>> ad0: 76319MB <WDC WD800JB-00ETA0> [155061/16/63] at ata0-master UDMA100
>> Mounting root from ufs:/dev/ad0s1a
>> WARNING: / was not properly dismounted
>>
>>
>>
>> ----- Original Message -----
>> From: "Joseph Koshy" <joseph.koshy at gmail.com>
>> To: "Allan Marshall" <allan at skene.net>
>> Cc: <hackers at freebsd.org>
>> Sent: Friday, October 29, 2004 11:14 AM
>> Subject: Re: 4.8-STABLE kernel crash
>>
>> > On Thu, 28 Oct 2004 21:30:45 -0300, Allan Marshall <allan at skene.net>
>> > wrote:
>> >> The box has been quite unstable, with restarts every few days
>> >> this is the first dump ive got with DDB
>> >> I realize this likely isnt enough information, but if you could point
>> >> me
>> >> in the right direction
>> >> I can provide anymore information required.
>> >
>> > 1) dmesg output please
>> > 2) Is this a new problem? Did the box run FreeBSD stably earlier?
>>
>>
More information about the freebsd-hackers
mailing list