Date: Thu, 18 Oct 2018 05:59:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 222314] ifconfig epair create panics the kernel (arm64) Message-ID: <bug-222314-7501-NNMQyTSd0o@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222314-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-222314-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=3D222314 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- A powerpc64 head -r339076 based context running # kyua test -k /usr/tests/Kyuafile reliably crashes (so far) during kyua displaying: sys/netinet/reuseport_lb:basic_ipv4 -> failed: /usr/src/tests/sys/netinet/reuseport_lb.c:165: bind() failed: Address alrea= dy in use [0.013s] sys/netinet/reuseport_lb:basic_ipv6 -> failed: /usr/src/tests/sys/netinet/reuseport_lb.c:221: bind() failed: Address alrea= dy in use [0.013s] sys/netipsec/tunnel/aes_cbc_128_hmac_sha1:v4 ->=20=20 Example details based on a debug kernel (invariants, witness, and diagnostics) . . . Note the LOR backtrace and the crash backtrace are the same for the call chain that calls vnet_sysinit. . . . epair3a: Ethernet address: 02:60:27:70:4b:0a epair3b: Ethernet address: 02:60:27:70:4b:0b epair3a: link state changed to UP epair3b: link state changed to UP lock order reversal: 1st 0x13be260 allprison (allprison) @ /usr/src/sys/kern/kern_jail.c:960 2nd 0x15964a0 vnet_sysinit_sxlock (vnet_sysinit_sxlock) @ /usr/src/sys/net/vnet.c:575 stack backtrace: #0 0x6f6520 at witness_debugger+0xf4 #1 0x6f8440 at witness_checkorder+0xa1c #2 0x675690 at _sx_slock_int+0x70 #3 0x675810 at _sx_slock+0x1c #4 0x7f4338 at vnet_sysinit+0x38 #5 0x7f44dc at vnet_alloc+0x118 #6 0x62ab84 at kern_jail_set+0x3274 #7 0x62b62c at sys_jail_set+0x8c #8 0xa8a798 at trap+0x9a0 #9 0xa7e660 at powerpc_interrupt+0x140 fatal kernel trap: exception =3D 0x300 (data storage interrupt) virtual address =3D 0xc00000008df1df30 dsisr =3D 0x42000000 srr0 =3D 0xe000000047854e98 (0xe000000047854e98) srr1 =3D 0x9000000000009032 current msr =3D 0x9000000000009032 lr =3D 0xe000000047854e90 (0xe000000047854e90) curthread =3D 0xc0000000206b6000 pid =3D 9464, comm =3D jail (Hand transcribed from here on:) [ thread pid 9464 tid 100296 ] Stopped at vnet_epair_init+0x78: stdx r3,r29,r30 db:0:kdb.enter.default> bt Tracing pid 9464 tid 100296 td 0xc0000000206b6000 0xe000000047274240: at vnet_sysinit+0x70 0xe000000047274270: at vnet_alloc+0x118 0xe000000047274300: at kern_jail_set+0x3274 0xe000000047274610: at sys_jail_set+0x8c 0xe000000047274660: at trap+0x9a0 0xe000000047274790: at powerpc_interrupt+0x140 0xe000000047274820: user sc trap by 0x81016a888 srr1 =3D 0x900000000000f032 r1 =3D 0x3fffffffffffd080 cr =3D 0x28002482 xer =3D 0x20000000 ctr =3D 0x81016a880 r2 =3D 0x810322300 There are past reports of the lock order reversal, such as: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210907 but this did not report any crash. Notes: The powerpc64 -r339076 based system was built via devel/powerpc-xtoolchain-gcc and created system-cc-is-clang and is using base/binutils as well. kyua is as of ports -r480180 and system-clang built it (and other things). I experiment with what the issues are with using fairly modern compiler toolchains for powerpc64 instead of gcc 4.2.1 . At this point I do not see this as likely to be responsible for the above crash. --=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-222314-7501-NNMQyTSd0o>