Date: Wed, 22 Dec 2021 15:12:11 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 260393] Page Fault tcp_output/tcp_input Message-ID: <bug-260393-7501-9gl5zA1Lde@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260393-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-260393-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=3D260393 --- Comment #52 from Hans Petter Selasky <hselasky@FreeBSD.org> --- Hi, There appears to be multiple dumps with different issues! Decoding the thread name from the last printout you provided: td_name =3D {0x69, 0x66, 0x5f, 0x69, 0x6f, 0x5f, 0x74, 0x71, 0x67, 0x5f, 0x 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}; td_name =3D "if_io_tqg_1" And according to the panic backtrace: current process =3D 0 (if_io_tqg_1) So this is a different core-dump, probably different issue. Can you repeat in the GDB printouts from the thread with sbdrop() in the backtrace (if_io_tqg_1): I need to see: print /x *tp print /x *tp->t_inpcb Just try searching all frames for these variables. --HPS --=20 You are receiving this mail because: 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-260393-7501-9gl5zA1Lde>