Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Feb 2011 23:19:25 GMT
From:      "gb.freebsd@gmail.com" <gb.freebsd@gmail.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   amd64/154629: Fatal trap 9: general protection fault while in kernel mode
Message-ID:  <201102092319.p19NJPwj075515@red.freebsd.org>
Resent-Message-ID: <201102092320.p19NKBN9070403@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         154629
>Category:       amd64
>Synopsis:       Fatal trap 9: general protection fault while in kernel mode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 09 23:20:11 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     gb.freebsd@gmail.com
>Release:        8.2-RC2
>Organization:
>Environment:
FreeBSD gateway 8.2-RC2 FreeBSD 8.2-RC2 #0: Wed Jan 12 17:02:35 UTC 2011     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Receiving the following crash:

Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0xffffffff80649f27
stack pointer           = 0x28:0xffffff808a3f69d0
frame pointer           = 0x28:0xffffff808a3f6a00
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 21 (syncer)
trap number             = 9
panic: general protection fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff805f556e at kdb_backtrace+0x5e
#1 0xffffffff805c3467 at panic+0x187
#2 0xffffffff808acd30 at trap_fatal+0x290
#3 0xffffffff808ad319 at trap+0x109
#4 0xffffffff808956e4 at calltrap+0x8
#5 0xffffffff806547bc at vfs_msync+0x13c
#6 0xffffffff80654a6a at sync_fsync+0x15a
#7 0xffffffff80652c1e at sync_vnode+0x15e
#8 0xffffffff80652f11 at sched_sync+0x1d1
#9 0xffffffff80599c58 at fork_exit+0x118

Have executed MemTest86+ for five complete cycles w/o error.
No known filesystem issues when issues started
Boot drive used to be part of a software based array (note "ar0: FAILURE - RAID0 array broken" messages) 
System had similar panics running 8.2-RC2/i386 and 8.1/i386.
Using default GENERIC kernel binary included with installation ISO
Recompiling GENERIC or building custom kernel does not fix issue

Hardware:
EVGA 113-M2-E113 (nForce 730a based)
AMD Athlon 64 X2 3800+
G.Skill 1GB DDR2-800 SDRAM DIMM (x2; 2GB total)
Intel Pro/100 PCI Ethernet (i82559 based)
Generic PCI-to-Cardbus Adapter (RF5C475 based)
Belkin Wireless A+G PC-Card Ethernet (Atheros 5212 based)
Seagate ST310014A 10GB PATA HDD (boot, ufs2)
Samsung HD204UI 2TB SATA HDD (ufs2+journal)

Crash report:
http://rapidshare.com/files/447090555/bugreport.tgz

Crash report contents:
/var/crash/core.txt.0
/var/crash/info.0
/var/crash/vmcore.0
dmesg > dmesg_verbose.txt (rebooted with verbose logging)
pciconf -l > pciconf_verbose.txt
>How-To-Repeat:
System panics randomly with time between panics ranging from a few hours to a few days.
>Fix:
None

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102092319.p19NJPwj075515>