On Tue, Dec 22, 2020 at 09:05:01AM -0500, mike tancsa wrote:
> Hmmm, another one. Not sure if this is hardware as it seems different ?
>
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 11; apic id = 0b
> fault virtual address = 0x0
> fault code = supervisor write data, page not present
> instruction pointer = 0x20:0xffffffff80ca0826
> stack pointer = 0x28:0xfffffe00bc0f8540
> frame pointer = 0x28:0xfffffe00bc0f8590
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 33 (dom0)
> trap number = 12
> panic: page fault
> cpuid = 11
> time = 1608641071
> KDB: stack backtrace:
> #0 0xffffffff80a3fe85 at kdb_backtrace+0x65
> #1 0xffffffff809f406b at vpanic+0x17b
> #2 0xffffffff809f3ee3 at panic+0x43
> #3 0xffffffff80e3fe71 at trap_fatal+0x391
> #4 0xffffffff80e3fecf at trap_pfault+0x4f
> #5 0xffffffff80e3f516 at trap+0x286
> #6 0xffffffff80e19318 at calltrap+0x8
> #7 0xffffffff80ca47d4 at bucket_cache_drain+0x134
> #8 0xffffffff80c9e302 at zone_drain_wait+0xa2
> #9 0xffffffff80ca2bbd at uma_reclaim_locked+0x6d
> #10 0xffffffff80ca2af4 at uma_reclaim+0x34
> #11 0xffffffff80cc5321 at vm_pageout_worker+0x421
> #12 0xffffffff80cc4ee3 at vm_pageout+0x193
> #13 0xffffffff809b55be at fork_exit+0x7e
> #14 0xffffffff80e1a34e at fork_trampoline+0xe
> Uptime: 5d20h37m16s
> Dumping 16057 out of 65398
> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
>
> __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
> 55 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n"
> (offsetof(struct pcpu,
> (kgdb) bt
Could you go to frame 11 and print zone->uz_name and
bucket->ub_bucket[18]? I'm wondering if the item pointer was mangled
somehow.
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
