Bug 154629 - [panic] Fatal trap 9: general protection fault while in kernel mode
Summary: [panic] Fatal trap 9: general protection fault while in kernel mode
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: amd64 (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mark Linimon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-09 23:20 UTC by Some User
Modified: 2018-05-31 15:50 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Some User 2011-02-09 23:20:11 UTC 
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 rx0, 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

Fix: 

None
How-To-Repeat: System panics randomly with time between panics ranging from a few hours to a few days.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:48 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2018-05-31 15:50:25 UTC 
Unfortunately this PR was never addressed before these versions of FreeBSD went out of support.  Sorry.

If this is still a problem, please open a new PR.  Thanks.