Re: panic

On Sunday, 14 January 2024 at 10:35:24 -0800, Don Dugger wrote:
> I've upgraded two systems from 13.2 to 14-Release p3 and both systems are
> panicking with a "page fault" every few hours.
>
> Any ideas??

In any panic backtrace, you need to look at the  stack fraom beneath
the calltrap or panic frame, in this case

> #6 0xffffffff80d6cb4c at udp6_bind+0x13c

The frames above are show how the system responded to the problem.

This one suggests a network problem, probably IPv6 related.  If your
panics all look like this, please check the bug database
(https://bugs.freebsd.org/bugzilla/) and enter a bug report if there
isn't already one there.

Again, the report for comparison:

> ======================================================================
> Unread portion of the kernel message buffer:
> rax: fffff802e1e53380 rbx: fffff80095562000 rbp: fffffe0122091cf0
> r10: 0000000000000000 r11: fffffe00e3a72c60 r12: fffff802e0d3d460
> r13: 000000000000b7c4 r14: 000000000000b7c4 r15: fffff80095f29600
> trap number             = 12
> panic: page fault
> cpuid = 1
> time = 1705251841
> KDB: stack backtrace:
> #0 0xffffffff80b9009d at kdb_backtrace+0x5d

This is where the backtrace was reported.
> #1 0xffffffff80b431a2 at vpanic+0x132
> #2 0xffffffff80b43063 at panic+0x43

Here the panic frame.  In this case, since it's a trap, it's not the
most important frame.

> #3 0xffffffff8100c85c at trap_fatal+0x40c
> #4 0xffffffff8100c8af at trap_pfault+0x4f
> #5 0xffffffff80fe3a38 at calltrap+0x8
> #6 0xffffffff80d6cb4c at udp6_bind+0x13c

And this is where the trap occurred.

> #7 0xffffffff80be61b2 at sobind+0x32
> #8 0xffffffff80bed645 at kern_bindat+0xc5

bind syscall

> #9 0xffffffff80bed4db at sys_bind+0x9b
> #10 0xffffffff8100d119 at amd64_syscall+0x109
> #11 0xffffffff80fe434b at fast_syscall_common+0xf8

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php