I would run a few cycles of memtest86+ and see how that looks..
--
Sent from a phone, apologies for poor formatting.
On 9 January 2022 16:13:00 jason houx <[email protected]> wrote:
I have two new Intel(R) Celeron(R) CPU J3160 systems I picked up over the
holidays to put into a carp/pfsync setup. I finished rebuild to -stable on
Jan 1
From device not failing boot (sister system):
kern.version=OpenBSD 7.0-stable (GENERIC.MP) #0: Sat Jan 1 17:28:07 EST 2022
# what changed?
* installed vim from the package manger on both systems
* setup pfsync on a dedicated interface.
* reboot of both systems to test some netstart scripts One system rebooted
fine the other system rebooted with this error message on console:
```
+3367944+352288+0+1171456 [1070557+128+1166808+878269]=0x15cdef8
entry point at 0xffffffff81001000.
[ using 3116792 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org
kernel: privileged instruction fault trap, code=0
Stopped at uvm_init+0x7: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
>> OpenBSD/amd64 BOOT 3.53
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
Stopped at db_read_bytes: kernel: page fault trap, code=0
--db_more--
```
I can hit enter and it will eventually just reboot - it won't accept any
other commands( break from console, ctrl-alt-escape). I don't believe vim
or pfsync could have impacted uvm and assume I am likely dealing with a
hardware issue.
I realize this is not providing much information I looked at:
* https://www.openbsd.org/ddb.html
* https://www.openbsd.org/report.html
I can't get to dbb (console break or ctrl-alt-escape).
One item that I did different during rebuild on these two sister system is
the one working I did make *without* -j, on this system I did a make -j3.
I have rebooted several times since rebuild so I highly doubt this is the
cause - I assume I am dealing with hardware but wanted to report this in
case it was helpful. I will be re-installing the system *without* -j.
If this happens again - any recommendations?
Thanks,
-jh
