Date: Mon, 11 Jul 2022 08:51:09 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264257] [tcp] Panic: Fatal trap 12: page fault while in kernel mode (if_io_tqg_4) - m_copydata ... at /usr/src/sys/kern/uipc_mbuf.c:659 Message-ID: <bug-264257-7501-S6npz9ZsW6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264257-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264257-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264257 --- Comment #78 from Michael Tuexen <tuexen@freebsd.org> --- >From the pcap information we were able to reconstruct the packet sequence, = but not the exact timing. Unfortunately, we were not able to reproduce the issu= e. However, it seems hard, to extend the pcap logging. So I suggest to use the BlackBox Logging instead. Could you: * Add options TCP_BLACKBOX to you kernel configuration file and recompile the kernel. You can remove the TCPPCAP option, if you want. * Add net.inet.tcp.bb.log_auto_all=3D1 net.inet.tcp.bb.log_auto_ratio=3D1 net.inet.tcp.bb.log_auto_mode=3D1 net.inet.tcp.bb.log_session_limit=3D200 This should enable BlackBox Logging on all TCP connections and it will the = last 200 events per TCP connection stored in the end point. Once the system has cras= hed, please provide a core. This time we should not only get the packet being sent/received, but also internal TCP state variables and information about the retransmission timer. If this information is not enough, we can adhoc extend the TCP Black Box Logging. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264257-7501-S6npz9ZsW6>