[Bug 240213] Firefox compilation fails due to node.js crashing (SIGBUS) due to a HMI event
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Aug 30 16:47:25 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240213
Bug ID: 240213
Summary: Firefox compilation fails due to node.js crashing
(SIGBUS) due to a HMI event
Product: Base System
Version: CURRENT
Hardware: powerpc
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: gustavo.romero at protonmail.com
Currently Firefox compilation inside poudriere is falling (please see full log
attached firefox-68.0.2_1,1.log) due to a SIGBUS caught on node.js executable
'node'.
ports head used is:
[root at p9 //usr/obj/tree2]# git log --oneline -1
f47d97e0e832 (HEAD -> master, origin/master, origin/HEAD) Get rid of the
deprecated @exec and @unexec
dmesg shows something like:
Hypervisor Maintenance Event received(Severity 0, type 1, HMER:
2040000000000000).
pid 2551 (node), jid 479, uid 65534: exited on signal 10 (core dumped)
'node' itself looks to crash at different instructions, mostly load/store ones
but in one case a trivial compare instruction, which does not access any
position in the storage, was also found, as I believe, to generated the HMI
event:
(gdb) x/i $pc
=> 0x109d9258
<._ZN2v88internal9Scavenger14ScavengeObjectINS0_18FullHeapObjectSlotEEENS0_18SlotCallbackResultET_NS0_10HeapObjectE+1048>:
std r29,0(r9)
(gdb) x/i $pc
=> 0x109d8e68
<._ZN2v88internal9Scavenger14ScavengeObjectINS0_18FullHeapObjectSlotEEENS0_18SlotCallbackResultET_NS0_10HeapObjectE+40>:
ld r9,0(r26)
(gdb) x/pi $pc
=> 0x812d646c8: cmpdi r3,0
(gdb) x/i $pc
=> 0x109debcc <._ZN2v88internal9Scavenger7ProcessEPNS0_14OneshotBarrierE+5228>:
ld r9,8(r9)
On inspecting the OPAL ring buffer the following can be found:
[213443.350925782,7] HMI: Received HMI interrupt: HMER = 0x2040000000000000
[213443.350954904,7] HMI: Core WOF = 0x0000000020000000 recovered error:
[213443.350956412,7] HMI: LSU - SLB multi hit
(please see attached logs for all details, including how to grab the log using
'pdbg')
Although the HMI severity is 0 (see above) meaning it can safely be ignored as
a CPU event critical event, one of the causes for a "HMI: LSU - SLB multi hit"
are duplicated entries in SLB which are hit once a EA (Effective Address) is
looked up in to the SLB, so it apparently points to some MM issue on FreeBSD
kernel.
I'll proceed to create (hopefully) a test case to hit the issue outside the
node.js.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list