Date: Wed, 9 Oct 2019 05:04:51 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694 Message-ID: <20191009120451.GK1263@albert.catwhisker.org> In-Reply-To: <20191008121519.GS1263@albert.catwhisker.org> References: <20191008121519.GS1263@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--aRgyPjBQ+CXa49SM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 08, 2019 at 05:15:19AM -0700, David Wolfskill wrote: > This was on my laptop (build machine, which was updated in parallel, > but uses a different NIC, had no issues) after a src update from > r353176 to r353298; laptop's NIC is wlan(4) (which is iwn(4), in > this case). After restoring the /boot/*.old set, I was able to reboot & update from r353298 to r353336. The subsequent reboot seemed OK ... until the keyboard & mouse were enabled (under X11; I use xdm on the laptop). Then I got a slightly different panic: panic: Assertion in_epoch(net_epoch_preempt) failed at /usr/src/sys/net/if.= c:356 Backtrace: panic: Assertion in_epoch(net_epoch_preempt) failed at /usr/src/sys/net/if.= c:356 cpuid =3D 0 time =3D 1570621553 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff8049ebab =3D db_trace_self_wrapper+0x2= b/frame 0xfffffe1072956580 vpanic() at 0xffffffff80b978fd =3D vpanic+0x19d/frame 0xfffffe10729565d0 panic() at 0xffffffff80b97693 =3D panic+0x43/frame 0xfffffe1072956630 if_ref() at 0xffffffff80ca1b10 =3D if_ref/frame 0xfffffe1072956650 sysctl_ifdata() at 0xffffffff80cb247d =3D sysctl_ifdata+0x4d/frame 0xfffffe= 1072956760 sysctl_root_handler_locked() at 0xffffffff80ba714b =3D sysctl_root_handler_= locked+0x7b/frame 0xfffffe10729567a0 sysctl_root() at 0xffffffff80ba64dc =3D sysctl_root+0x20c/frame 0xfffffe107= 2956820 userland_sysctl() at 0xffffffff80ba6bab =3D userland_sysctl+0x17b/frame 0xf= ffffe10729568d0 sys___sysctl() at 0xffffffff80ba69ef =3D sys___sysctl+0x5f/frame 0xfffffe10= 72956980 amd64_syscall() at 0xffffffff810480f4 =3D amd64_syscall+0x2d4/frame 0xfffff= e1072956ab0 fast_syscall_common() at 0xffffffff8101eaa0 =3D fast_syscall_common+0x101/f= rame 0xfffffe1072956ab0 --- syscall (202, FreeBSD ELF64, sys___sysctl), rip =3D 0x8014d4d2a, rsp = =3D 0x7fffffffeaa8, rbp =3D 0x7fffffffeae0 --- KDB: enter: panic > The ddb "dump" command recorded a dump, which I managed to capture; the > information may be found at > http://www.catwhisker.org/~david/FreeBSD/head/r353298/ This one is at http://www.catwhisker.org/~david/FreeBSD/head/r353336 As before, the (headless) build machine had no issues that I could see. Peace, david --=20 David H. Wolfskill david@catwhisker.org I am amazed that anyone would condone what Trunp has publicly admitted he d= id. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --aRgyPjBQ+CXa49SM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl2dzOJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 Pcl+HAgAlmgXxUZvCIGmds0/Y2A04UUnfMgvPmDUlYAlpkH424FPTgfL6pVHwVoc PEGgTrxSe5/MqD6RoljFRzNpzoX5n2p6PcBL25Fhcq3ozPiJd3/yLjiC0bfeQSco RWetTCVFuqyUOAmNImXfDZv1EvwXRfrcjlIm7hq1irLvYxNgPyb9c8dNIHjUcHCt IPSSYZUc13oFuAtqiZuHZ7krdO8zVKqkQzOuTItjwpOnN+zp0zz25qZyFtqDW9R8 beIASqG+1MwP9ox2GdprLsSgmZ3rK/VFnoNHwCC4DejBPwaybFWY15rMU68+LvXl I15PTdKH+AT0zo0oB+Z/A0TFKwtosQ== =vvf1 -----END PGP SIGNATURE----- --aRgyPjBQ+CXa49SM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191009120451.GK1263>