https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285275
--- Comment #1 from Graham Perrin <grahamper...@gmail.com> ---
Two sets of notes from yesterday morning:
----
root@mowa219-gjp4-zbook-freebsd:/var/crash # rm kgdb151.core
root@mowa219-gjp4-zbook-freebsd:/var/crash # date ; uptime
Sat Mar 8 03:17:30 GMT 2025
3:17AM up 42 mins, 5 users, load averages: 0.75, 1.36, 1.10
root@mowa219-gjp4-zbook-freebsd:/var/crash # crashinfo vmcore.13
Writing crash summary to ./core.txt.13.
You have new mail.
root@mowa219-gjp4-zbook-freebsd:/var/crash # ls -hlnrt | grep 8\ 03
-rw------- 1 0 0 2.8G Mar 8 03:17 kgdb151.core
-rw-r--r-- 1 0 0 8.0K Mar 8 03:25 core.txt.13
root@mowa219-gjp4-zbook-freebsd:/var/crash # /usr/bin/time -h crashinfo
vmcore.13
Writing crash summary to ./core.txt.13.
4m24.03s real 17.25s user 39.65s sys
root@mowa219-gjp4-zbook-freebsd:/var/crash # ls -hlnrt | grep 8\ 03
-rw------- 1 0 0 2.8G Mar 8 03:29 kgdb151.core
-rw-r--r-- 1 0 0 8.3K Mar 8 03:33 core.txt.13
root@mowa219-gjp4-zbook-freebsd:/var/crash # cat info.13
Dump header from device: /dev/ada1p2
Architecture: amd64
Architecture Version: 2
Dump Length: 2706395136
Blocksize: 512
Compression: none
Dumptime: 2025-03-08 02:18:33 +0000
Hostname: mowa219-gjp4-zbook-freebsd
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 15.0-CURRENT main-n275833-136c5e17b61a
GENERIC-NODEBUG
Panic String: page fault
Dump Parity: 3349005578
Bounds: 13
Dump Status: good
root@mowa219-gjp4-zbook-freebsd:/var/crash # ls -hln vmcore.13
-rw------- 1 0 0 82M Mar 8 02:27 vmcore.13
root@mowa219-gjp4-zbook-freebsd:/var/crash # du -hs vmcore.13
23M vmcore.13
root@mowa219-gjp4-zbook-freebsd:/var/crash #
----
root@mowa219-gjp4-zbook-freebsd:/var/crash # crashinfo vmcore.13
Writing crash summary to ./core.txt.13.
root@mowa219-gjp4-zbook-freebsd:/var/crash # ls -hlnrt | grep 8\ 04
-rw------- 1 0 0 2.8G Mar 8 04:03 kgdb151.core
-rw-r--r-- 1 0 0 8.6K Mar 8 04:03 core.txt.13
root@mowa219-gjp4-zbook-freebsd:/var/crash #
----
In the first set, it's noticeable that a run of crashinfo sometimes takes much
longer than usual. In these cases, there is unexpectedly high use of memory; I
should treat this as a separate issue.
--
You are receiving this mail because:
You are the assignee for the bug.
