[Bug 292469] panic: page fault in m_copydata() via TCP stack (bge) on 14.3-RELEASE

[email protected]
Newsgroups gmane.os.freebsd.devel.net
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292469

--- Comment #4 from Mual <[email protected]> ---
I don’t have a core file to share. 

Today I had a similar panic on another server with the same software
configuration:

rdi: 0000000000000000  rsi: 0000000000000000  rdx: fffffe01e4bded28
rcx: 0000000000000000   r8: 0000000000000000   r9: 0000000000000000
rax: 0000000000000000  rbx: 0000000000000000  rbp: fffffe01e4bdebc0
r10: 000000000000005a r11: 0000000000004029 r12: fffffe819872a3d60
r13: 0000000000000034 r14: ffff82b76747000 r15: 000000000000005a
trap number             = 12
panic: page fault
cpuid = 14
time = 1768766834
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe01e4bde890
vpanic() at vpanic+0x161/frame 0xfffffe01e4bde9c0
panic() at panic+0x43/frame 0xfffffe01e4bdea20
trap_pfault() at trap_pfault+0x3da/frame 0xfffffe01e4bdea70
calltrap() at calltrap+0x8/frame 0xfffffe01e4bdea70
--- trap 0xc, rip = 0xffffffff80869f02, rsp = 0xfffffe01e4bdeb40, rbp =
0xfffffe01e4bdebc0
tcp_m_copy() at tcp_m_copy+0x62/frame 0xfffffe01e4bdebc0
tcp_default_output() at tcp_default_output+0x121e/frame 0xfffffe01e4bded90
tcp_timer_delack() at tcp_timer_delack+0x6d/frame 0xfffffe01e4bdede0
tcp_timer_enter() at tcp_timer_enter+0x104/frame 0xfffffe01e4bdee10
softclock_call_cc() at softclock_call_cc+0x129/frame 0xfffffe01e4bdeec0
softclock_thread() at softclock_thread+0xe5/frame 0xfffffe01e4bdef00
fork_exit() at fork_exit+0x81/frame 0xfffffe01e4bdef30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01e4bdef30
--- trap 0, rip = 0, rsp = 0, rbp = 0
KDB: enter: panic
[ thread pid 2 tid 100086 ]
Stopped at  kdb_enter+0x33: movq  $0,0xc0ef02(%rip)
db>

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.