https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
--- Comment #91 from Mark Millard <mar...@dsl-only.net> --- My first ever compelted attempt at anything like: pousriere bulk -w -a finished. (It started from a prior interrupted attempt from a prior boot so some things had already built and the prior failures were retried.) It reported "62 FAIL" overall, most for source code rejections based on a preliminary look. Few Signals. But when I went to look at dmesg -a there were lots of Signals there: FBSDx6411SL# dmesg -a | grep "^pid" | cut -d " " -f 3-100 | sort | uniq -c | less 1 (a.out), uid 0: exited on signal 11 (core dumped) 1 (bash), uid 0: exited on signal 11 (core dumped) 3 (cc), uid 0: exited on signal 11 (core dumped) 1 (clang), uid 0: exited on signal 11 (core dumped) 1 (cm3), uid 0: exited on signal 6 (core dumped) 1 (conftest) is attempting to use unsafe AIO requests - not logging anymore 1 (conftest), uid 0: exited on signal 10 (core dumped) 4 (conftest), uid 0: exited on signal 11 (core dumped) 4 (conftest), uid 0: exited on signal 6 (core dumped) 76 (fc-cache), uid 0: exited on signal 11 (core dumped) 4 (gcc), uid 0: exited on signal 11 (core dumped) 17 (gdk-pixbuf-query-lo), uid 0: exited on signal 11 (core dumped) 121 (gio-querymodules-64), uid 0: exited on signal 11 (core dumped) 1 (go), uid 0: exited on signal 5 (core dumped) 16 (gtk-query-immodules), uid 0: exited on signal 11 (core dumped) 1 (nm), uid 0: exited on signal 6 (core dumped) 17 (pango-querymodules-), uid 0: exited on signal 11 (core dumped) 24 (pctest), uid 0: exited on signal 11 (core dumped) 24 (pdtest), uid 0: exited on signal 11 (core dumped) 24 (pstest), uid 0: exited on signal 11 (core dumped) 24 (pztest), uid 0: exited on signal 11 (core dumped) 2 (readonly.exe), uid 0: exited on signal 11 1 (scm), uid 0: exited on signal 11 (core dumped) 1 (test_26349), uid 0: exited on signal 4 (core dumped) 15 (try), uid 0: exited on signal 11 How much of the Signal activity is abnormal I do not know. These are all from the kern.sched.steal_idle=0 type of test context. Some other odd items in FreeBSD's demsg -a output were: interrupt storm detected on "irq19:"; throttling interrupt source Failed to fully fault in a core file segment at VA 0x800641000 with size 0x1000 to be written at offset 0x25000 for process conftest Failed to fully fault in a core file segment at VA 0x800643000 with size 0x1000 to be written at offset 0x25000 for process a.out FYI: systat -vmstat indicates "le0" for irq19. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"