[Bug 259218] Fatal trap 12: page fault while in kernel mode

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 20 Oct 2021 00:15:33 UTC

--- Comment #11 from Dennis Clarke <dclarke@blastwave.org> ---
Well, the most recent comment and data that I provided was from a
panic on the same new kernel that I built in the last 48 hours. 

esther# uname -apKU
FreeBSD esther 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n250102-d95c0a12a2d:
Mon Oct 18 05:58:15 GMT 2021    
root@esther:/usr/obj/usr/src/i386.i386/sys/GENERIC  i386 i386 1400038 1400038

Why did I bother to build a new kernel?

Because there was no way to follow your instructions when there is no
such thing as "kernel.full" previously. Also no way to fetch it and then
use gdb.  Why?  There was no way to install gdb.  The whole system was
so unstable that it did a panic in the middle of "pkg install gdb" and
that mess landed me in a situation where the pkg sqlite database held a
pid lock record on the process when the panic happened.

It has been a ton of fun just getting to this point.

This is what I saw on the console when the panic happened in the middle
of trying to do "pkg install gdb" : 

Last login: Mon Oct 18 01:58:17 on ttyu0
Oct 18 18:37:35 esther login[753]: ROOT LOGIN (root) ON ttyu0
FreeBSD 14.0-CURRENT (GENERIC) #0 main-n250102-d95c0a12a2d: Mon Oct 18 05:58:15
GMT 2021

Welcome to FreeBSD!

Release Notes, Errata: https://www.FreeBSD.org/releases/
Security Advisories:   https://www.FreeBSD.org/security/
FreeBSD Handbook:      https://www.FreeBSD.org/handbook/
FreeBSD FAQ:           https://www.FreeBSD.org/faq/
Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/
FreeBSD Forums:        https://forums.FreeBSD.org/

Documents installed with the system are in the /usr/local/share/doc/freebsd/
directory, or can be installed later with:  pkg install en-freebsd-doc
For other languages, replace "en" with a language code like de or fr.

Show the version of FreeBSD installed:  freebsd-version ; uname -a
Please include that output and any error messages when posting questions.
Introduction to manual pages:  man man
FreeBSD directory layout:      man hier

To change this login announcement, see motd(5).
You have new mail.
esther# ls -lap /var/crash
total 109816
drwxr-x---   2 root  wheel        512 Oct 18 18:24 ./
drwxr-xr-x  24 root  wheel        512 Oct 18 18:23 ../
-rw-r--r--   1 root  wheel          2 Oct 18 18:24 bounds
-rw-r--r--   1 root  wheel         84 Oct 18 18:24 core.txt.0
-rw-------   1 root  wheel        516 Oct 18 18:24 info.0
lrwxr-xr-x   1 root  wheel          6 Oct 18 18:24 info.last -> info.0
-rw-r--r--   1 root  wheel          5 Oct  7 21:44 minfree
-rw-------   1 root  wheel  121741312 Oct 18 18:24 vmcore.0
lrwxr-xr-x   1 root  wheel          8 Oct 18 18:24 vmcore.last -> vmcore.0
esther# cat /var/crash/core.txt.0 
Unable to find a kernel debugger.
Please install the devel/gdb port or gdb package.
esther# pkg update --force
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%    6 MiB   3.2MB/s    00:02    
Processing entries: 100%
FreeBSD repository update completed. 30438 packages processed.
All repositories are up to date.
esther# date -u 
Mon Oct 18 18:41:42 UTC 2021
esther# pkg audit
0 problem(s) in 0 installed package(s) found.
esther# pkg install gdb
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        boost-libs: 1.72.0_5
        gdb: 11.1
        libiconv: 1.16
        source-highlight: 3.1.9_1

Number of packages to be installed: 4

The process will require 218 MiB more space.

Proceed with this action? [y/N]: y
[1/4] Installing boost-libs-1.72.0_5...
[1/4] Extracting boost-libs-1.72.0_5:  98%panic: vm_fault_lookup: fault on
nofault entry, addr: 0xd2d8000
cpuid = 0
time = 1634582864
KDB: stack backtrace:
db_trace_self_wrapper(0,10283000,10283002,d2d7a48,202,...) at
db_trace_self_wrapper+0x28/frame 0xd2d79bc
vpanic(151e45c,d2d79f8,d2d79f8,d2d7ab0,12de9b2,...) at vpanic+0x124/frame
panic(151e45c,150024a,d2d8000,d2d8000,0,...) at panic+0x14/frame 0xd2d79ec
vm_fault(1e4f5ec,d2d8000,2,0,0) at vm_fault+0x1862/frame 0xd2d7ab0
vm_fault_trap(1e4f5ec,d2d8000,2,0,0,0) at vm_fault_trap+0x52/frame 0xd2d7ad8
trap_pfault(d2d8000,0,0) at trap_pfault+0x16a/frame 0xd2d7b24
trap(d2d7bf8,8,28,28,d2d8000,...) at trap+0x2d2/frame 0xd2d7bec
calltrap() at 0xffc0319f/frame 0xd2d7bec
--- trap 0xc, eip = 0x1404240, esp = 0xd2d7c38, ebp = 0xd2d7c60 ---
random_nehemiah_read(b2d5278a,f90b3d82,3e782ecf,9908ee70,a799ef37,...) at
random_nehemiah_read+0x60/frame 0xd2d7c60

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0xb2b9d8d1
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0x1409ea0
stack pointer           = 0x28:0xd2d784c
frame pointer           = 0x28:0xd2d7894
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 0
current process         = 5 (rand_harvestq)
trap number             = 12
panic: page fault
cpuid = 0
time = 1634582864
KDB: stack backtrace:
db_trace_self_wrapper(d2d780c,10283000,d2d780c,c,0,...) at
db_trace_self_wrapper+0x28/frame 0xd2d769c
vpanic(1479c1e,d2d76d8,d2d76d8,d2d7700,142f277,...) at vpanic+0x124/frame
panic(1479c1e,150c09f,0,fffff,d2df69b,...) at panic+0x14/frame 0xd2d76cc
trap_fatal(d2d0000,7f,1,8,1511eb4,...) at trap_fatal+0x347/frame 0xd2d7700
trap_pfault(b2b9d8d1,0,0) at trap_pfault+0x6f/frame 0xd2d7734
trap(d2d780c,8,28,28,d2d7984,...) at trap+0x2d2/frame 0xd2d7800
calltrap() at 0xffc0319f/frame 0xd2d7800
--- trap 0xc, eip = 0x1409ea0, esp = 0xd2d784c, ebp = 0xd2d7894 ---


I will attach the remainder of the 4000+ lines in a txt file.

You are receiving this mail because:
You are the assignee for the bug.