[Bug 233193] Reproducible vm panic with AMD Ryzen 3 2200G

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Nov 13 09:22:33 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233193

            Bug ID: 233193
           Summary: Reproducible vm panic with AMD Ryzen 3 2200G
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: johalun0 at gmail.com
 Attachment #199200 text/plain
         mime type:

Created attachment 199200
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199200&action=edit
dmesg

My setup that I've had a few months have been very unstable (Ubuntu, Windows
and FreeBSD) from start. After I've managed to run Windows update without
crashes, Windows 10 is now stable on this machine.

I've found a way to reproduce the panics with stress from sysutils/stress

# stress --vm 1

will cause panic reboot or lockup. 

All software is up to date and cpu microcode updates enabled.
I have checked for BIOS updates regularly since purchase but nothing so far. 
Ubuntu memtest passes without problems.

Hardware:
ASRock A320M-HDV
QUMOX 4GB DDR4 2133 2133MHz PC4-17000 PC-17000 (288 PIN) DIMM MEMORY 4GB
AMD YD2200C5FBBOX Ryzen 3 2200G CPU with Wraith Stealth Cooler and RX Vega
Graphics

dmesg output attached.

Backtraces from a few panics:

BT 1:
-----
Unread portion of the kernel message buffer:
panic: page 0xfffff800b636d630 has object
cpuid = 1
time = 1542033179
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe002a97f620
vpanic() at vpanic+0x1a3/frame 0xfffffe002a97f680
panic() at panic+0x43/frame 0xfffffe002a97f6e0
vm_page_alloc_check() at vm_page_alloc_check+0x81/frame 0xfffffe002a97f6f0
vm_page_alloc_domain_after() at vm_page_alloc_domain_after+0x295/frame
0xfffffe002a97f770
vm_page_alloc() at vm_page_alloc+0x74/frame 0xfffffe002a97f7d0
vm_fault_hold() at vm_fault_hold+0x12c2/frame 0xfffffe002a97f910
vm_fault() at vm_fault+0x60/frame 0xfffffe002a97f950
trap_pfault() at trap_pfault+0x188/frame 0xfffffe002a97f9a0
trap() at trap+0x45a/frame 0xfffffe002a97fab0
calltrap() at calltrap+0x8/frame 0xfffffe002a97fab0
--- trap 0xc, rip = 0x204860, rsp = 0x7fffffffda00, rbp = 0x7fffffffda90 ---


BT 2:
-----
Unread portion of the kernel message buffer:
Kernel page fault with the following non-sleepable locks held:
shared rw vm object (vm object) r = 0 (0xfffff80012e17900) locked @
/usr/src/sys/vm/vm_fault.c:628
stack backtrace:
#0 0xffffffff8072e5a3 at witness_debugger+0x73
#1 0xffffffff8072f4ef at witness_warn+0x43f
#2 0xffffffff80a50dc3 at trap_pfault+0x53
#3 0xffffffff80a503fa at trap+0x2ba
#4 0xffffffff80a2ab75 at calltrap+0x8
#5 0xffffffff809f6081 at vm_fault_hold+0xd01
#6 0xffffffff809f5330 at vm_fault+0x60
#7 0xffffffff80a50ef8 at trap_pfault+0x188
#8 0xffffffff80a5059a at trap+0x45a
#9 0xffffffff80a2ab75 at calltrap+0x8


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x2c0a
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80a19bfc
stack pointer           = 0x0:0xfffffe002a8e97d0
frame pointer           = 0x0:0xfffffe002a8e97d0
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         = 762 (vmstat)
trap number             = 12
panic: page fault
cpuid = 2
time = 1542033089
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe002a8e9490
vpanic() at vpanic+0x1a3/frame 0xfffffe002a8e94f0
panic() at panic+0x43/frame 0xfffffe002a8e9550
trap_fatal() at trap_fatal+0x35f/frame 0xfffffe002a8e95a0
trap_pfault() at trap_pfault+0x62/frame 0xfffffe002a8e95f0
trap() at trap+0x2ba/frame 0xfffffe002a8e9700
calltrap() at calltrap+0x8/frame 0xfffffe002a8e9700
--- trap 0xc, rip = 0xffffffff80a19bfc, rsp = 0xfffffe002a8e97d0, rbp =
0xfffffe002a8e97d0 ---
vm_radix_lookup() at vm_radix_lookup+0x2c/frame 0xfffffe002a8e97d0
vm_fault_hold() at vm_fault_hold+0xd01/frame 0xfffffe002a8e9910
vm_fault() at vm_fault+0x60/frame 0xfffffe002a8e9950
trap_pfault() at trap_pfault+0x188/frame 0xfffffe002a8e99a0
trap() at trap+0x45a/frame 0xfffffe002a8e9ab0
calltrap() at calltrap+0x8/frame 0xfffffe002a8e9ab0
--- trap 0xc, rip = 0x80026d7a0, rsp = 0x7fffffffd1b0, rbp = 0x7fffffffd1b0 ---


BT 3:
-----
Unread portion of the kernel message buffer:
panic: page 0xfffff800b5528f20 is allocated and unlocked
cpuid = 3
time = 1542033030
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe002a8855f0
vpanic() at vpanic+0x1a3/frame 0xfffffe002a885650
panic() at panic+0x43/frame 0xfffffe002a8856b0
vm_page_dequeue() at vm_page_dequeue+0x24e/frame 0xfffffe002a8856f0
vm_page_alloc_domain_after() at vm_page_alloc_domain_after+0x28d/frame
0xfffffe002a885770
vm_page_alloc() at vm_page_alloc+0x74/frame 0xfffffe002a8857d0
vm_fault_hold() at vm_fault_hold+0x12c2/frame 0xfffffe002a885910
vm_fault() at vm_fault+0x60/frame 0xfffffe002a885950
trap_pfault() at trap_pfault+0x188/frame 0xfffffe002a8859a0
trap() at trap+0x45a/frame 0xfffffe002a885ab0
calltrap() at calltrap+0x8/frame 0xfffffe002a885ab0
--- trap 0xc, rip = 0x204860, rsp = 0x7fffffffda00, rbp = 0x7fffffffda90 ---

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list