Date: Mon, 8 Jul 2019 15:24:05 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Firefox dumps core on rpi3 at r349806 Message-ID: <20190708222405.GA53084@www.zefox.net>
next in thread | raw e-mail | index | archive | help
Firefox has started causing a panic on a Pi3b+ running r349806. The
problem appeared about a week ago and has persisted since. The controlling
terminal reports:
bob@www:~ % firefox
console.error: "Could not write session state file " (new Error("_initWorker called too early! Please read the session file from disk first.", "resource:///modules/sessionstore/SessionFile.jsm", 334)) "_initWorker/<@resource:///modules/sessionstore/SessionFile.jsm:334:15\n_initWorker@resource:///modules/sessionstore/SessionFile.jsm:327:12\n_postToWorker@resource:///modules/sessionstore/SessionFile.jsm:351:11\nwrite@resource:///modules/sessionstore/SessionFile.jsm:390:19\nwrite@resource:///modules/sessionstore/SessionFile.jsm:63:12\n_writeState@resource:///modules/sessionstore/SessionSaver.jsm:356:12\n_saveState@resource:///modules/sessionstore/SessionSaver.jsm:294:12\n_saveStateAsync@resource:///modules/sessionstore/SessionSaver.jsm:340:5\nsaveStateAsyncWhenIdle@resource:///modules/sessionstore/SessionSaver.jsm:191:9\n"
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
On the serial console one sees:
login: panic: Invalid l3 page (16000002c80074b != 16000002c8007cb)
cpuid = 3
time = 1562624166
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
pc = 0xffff00000070a038 lr = 0xffff000000102640
sp = 0xffff0000516eb250 fp = 0xffff0000516eb460
db_trace_self_wrapper() at vpanic+0x18c
pc = 0xffff000000102640 lr = 0xffff0000003f8aa0
sp = 0xffff0000516eb470 fp = 0xffff0000516eb520
vpanic() at panic+0x44
pc = 0xffff0000003f8aa0 lr = 0xffff0000003f8850
sp = 0xffff0000516eb530 fp = 0xffff0000516eb5b0
panic() at pmap_demote_l2_locked+0xb48
pc = 0xffff0000003f8850 lr = 0xffff00000071c808
sp = 0xffff0000516eb5c0 fp = 0xffff0000516eb660
pmap_demote_l2_locked() at pmap_ts_referenced+0x300
pc = 0xffff00000071c808 lr = 0xffff0000007226b8
sp = 0xffff0000516eb670 fp = 0xffff0000516eb6f0
pmap_ts_referenced() at vm_pageout_worker+0xed4
pc = 0xffff0000007226b8 lr = 0xffff0000006cb8b4
sp = 0xffff0000516eb700 fp = 0xffff0000516ebae0
vm_pageout_worker() at vm_pageout+0x15c
pc = 0xffff0000006cb8b4 lr = 0xffff0000006ca99c
sp = 0xffff0000516ebaf0 fp = 0xffff0000516ebb50
vm_pageout() at fork_exit+0x7c
pc = 0xffff0000006ca99c lr = 0xffff0000003b9694
sp = 0xffff0000516ebb60 fp = 0xffff0000516ebb90
fork_exit() at fork_trampoline+0x10
pc = 0xffff0000003b9694 lr = 0xffff000000725b2c
sp = 0xffff0000516ebba0 fp = 0x0000000000000000
KDB: enter: panic
[ thread pid 21 tid 100066 ]
Stopped at 0
db>
Thanks for reading, any suggestions appreciated!
bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190708222405.GA53084>