Re: dmesg -a shows "Failed to fully fault in a core file segment at VA" examples, anything to worry about?
On 30/11/2017 23:04, Mark Millard wrote: > The messages seem to be considered non-fatal at the system > level, although the processes are getting signal 11. It is > not clear to me if the signal 11's are consequences, causes, > or just happen to be associated. The messages are produced if there is a problem while writing a core file. So, they can appear only if (after) a process crashed. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
dmesg -a shows "Failed to fully fault in a core file segment at VA" examples, anything to worry about?
Basic context: # uname -apKU FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r326192M amd64 amd64 1200054 1200054 During an experiment with a "poudriere bulk -a" I've noticed the following 2 message sequences: > Failed to fully fault in a core file segment at VA 0x80064b000 with size > 0x1000 to be written at offset 0x2e000 for process conftest > pid 26417 (conftest), uid 0: exited on signal 11 (core dumped) > Nov 30 03:37:25 FBSDHUGE kernel: Failed to fully fault in a core file segment > at VA 0x80064b000 with size 0x1000 to be written at offset 0x2e000 for > process conftest and: > Failed to fully fault in a core file segment at VA 0x80064c000 with size > 0x1000 to be written at offset 0x2d000 for process a.out > pid 65189 (a.out), uid 0: exited on signal 11 (core dumped) > Nov 30 04:58:23 FBSDHUGE kernel: Failed to fully fault in a core file segment > at VA 0x80064c000 with size 0x1000 to be written at offset 0x2d000 for > process a.out (The console only shows the two non-timestampted "Failed to . . ." messages.) I note that VA+offset == 0x800679000 in both cases. This suggests a common cause associated with that spot in some way. The messages seem to be considered non-fatal at the system level, although the processes are getting signal 11. It is not clear to me if the signal 11's are consequences, causes, or just happen to be associated. So far I've only had the 2 examples as of: # poudriere status SET PORTS JAIL BUILDSTATUS QUEUE BUILT FAIL SKIP IGNORE REMAIN TIME LOGS - default FBSDFSSDjail 2017-11-29_03h45m33s parallel_build 2 14609 156 2015136 10861 33:09:51 /usr/local/poudriere/data/logs/bulk/FBSDFSSDjail-default/2017-11-29_03h45m33s More context: FreeBSD is running under a Windows 10 Pro Hyper-V virtual machine. === Mark Millard markmi at dsl-only.net ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
