Date: Mon, 20 Nov 2023 17:48:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275169] Panic: rw_rlock: wlock already held for tcpinp @ /usr/src/sys/netinet/in_pcb.c:2529 Message-ID: <bug-275169-227-VtFo2goKZj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275169-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275169-227@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=3D275169 --- Comment #10 from Dani I. <i.dani@outlook.com> --- Created attachment 246450 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D246450&action= =3Dedit Panic caused by sysctl net.link.ether.ipfw=3D1 A small update: 1: We're also able to trigger a panic when setting the following sysctl: # sysctl net.link.ether.ipfw=3D1 After setting the sysctl the system crashes after a few seconds. The panic seems to be the same but the locks shown in the dump seem to be different. 2: This isn't specific to http-traffic, more to tcp-traffic in general - we= can also reproduce this with ssh for example. 3: While debugging and trying out, we tried setting "hw.ix.enable_rss" to 0= in loader.conf (default=3D1), which didn't have any impact (panic still occurs= ). --=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-275169-227-VtFo2goKZj>