Date: Wed, 13 Sep 2017 19:08:26 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: Sean Bruno <sbruno@freebsd.org>, freebsd-current@freebsd.org, dhw@freebsd.org Subject: Re: Panic: @r323525: iflib Message-ID: <a268f351-cec4-ca98-28a2-d35561463f8f@FreeBSD.org> In-Reply-To: <dd34f001-cafb-6fc0-e21d-9fc100661358@freebsd.org> References: <20170913131042.GZ1351@albert.catwhisker.org> <dd34f001-cafb-6fc0-e21d-9fc100661358@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --J1hOlhspkf7O88ngKucbkkSsw97He1tcL Content-Type: multipart/mixed; boundary="2Vi9i3vMVV19iXHJ1g67uHmRrots2Ihbf"; protected-headers="v1" From: Jung-uk Kim <jkim@FreeBSD.org> To: Sean Bruno <sbruno@freebsd.org>, freebsd-current@freebsd.org, dhw@freebsd.org Message-ID: <a268f351-cec4-ca98-28a2-d35561463f8f@FreeBSD.org> Subject: Re: Panic: @r323525: iflib References: <20170913131042.GZ1351@albert.catwhisker.org> <dd34f001-cafb-6fc0-e21d-9fc100661358@freebsd.org> In-Reply-To: <dd34f001-cafb-6fc0-e21d-9fc100661358@freebsd.org> --2Vi9i3vMVV19iXHJ1g67uHmRrots2Ihbf Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 09/13/2017 11:21, Sean Bruno wrote: >> Previous successful build was: >> FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #398 = r323483M/323489:1200044: Tue Sep 12 04:31:08 PDT 2017 root@g1-252.cat= whisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >> >> The usual historical information, including a verbose-boot dmesg.boot >> from the above-cited build, may be found at >> <http://www.catwhisker.org/~david/FreeBSD/history/>. >> >> I will try hand-transcribing some of the lock & backtrace info: >> >> ... >> em0: allocated for 1 rx_queues >> Kernel page fault with the following non-sleepable locks held: >> exclusive sleep mutex taskqgroup (taskqgroup) r =3D 0 (0xfffffe07be2e4= 800) locked @ /usr/src/sys/kern/subr_gtaskqueue.c:803 >> stack backtrace: [which I am abbreviating at this point -- dhw] >> #0 ... at witness_debugger+0x73 >> #1 ... at witness_warn+0x43f >> #2 ... at trap_pfault+0x53 >> #3 ... at trap+0x2c5 >> #4 ... at calltrap+0x8 >> #5 ... at iflib_device_register+0x2a61 >> #6 ... at iflib_device_attach+0xb7 >> #7 ... at device_attach+0x3ee >> #8 ... at bus_generic_attach+0x5a >> #9 ... at pci_attach+0xd5 >> #10 ... at device_attach+0x3ee >> #11 ... at bus_generic_attach+0x5a >> #12 ... at acpi_pcib_acpi_attach+0x3bc >> #13 ... at device_attach+0x3ee >> #14 ... at bus_generic_attach+0x5a >> #15 ... at acpi_attach+0xe85 >> #16 ... at device_attach+0x3ee >> #17 ... at bus_generic_attach+0x5a >> >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 2; apic id =3D 02 >> fault virtual address =3D 0xffffffff8b530c20 >> fault code =3D supervisor write data, page not present >> ... >> [ thread pid 0 tid 100000 ] >> Stopped at 0xffffffff80a743b0 =3D taskqgroup_attach+0x230: orq= %rax,-0x 58(%rbp,%xrx,8) >> >> I can provide more specific excerpts, but I need to focus on some >> other activities for a while. >> >> Peace, >> david >> >=20 >=20 > When you get a chance, let me know what em(4) device is in your machine= > (pciconf -lvbc). I'll see if I have one around here to test. FYI, I have very similar panics after the commit. Reverting the commit from today's head, i.e., r323566 - (r323516 & r323517), fixed the problem for me. em0@pci0:7:0:0: class=3D0x020000 card=3D0x115e8086 chip=3D0x105e8086 rev=3D= 0x06 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82571EB Gigabit Ethernet Controller' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 32, base 0xd0ca0000, size 131072, enabled bar [14] =3D type Memory, range 32, base 0xd0c80000, size 131072, enabled bar [18] =3D type I/O Port, range 32, base 0x2020, size 32, enabled= cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 cap 05[d0] =3D MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] =3D PCI-Express 1 endpoint max data 256(256) NS link x4(x4) speed 2.5(2.5) ASPM disabled(L0s) ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected ecap 0003[140] =3D Serial 1 001517ffff51bcba em1@pci0:7:0:1: class=3D0x020000 card=3D0x115e8086 chip=3D0x105e8086 rev=3D= 0x06 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82571EB Gigabit Ethernet Controller' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 32, base 0xd0c40000, size 131072, enabled bar [14] =3D type Memory, range 32, base 0xd0c20000, size 131072, enabled bar [18] =3D type I/O Port, range 32, base 0x2000, size 32, enabled= cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 cap 05[d0] =3D MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] =3D PCI-Express 1 endpoint max data 256(256) NS link x4(x4) speed 2.5(2.5) ASPM disabled(L0s) ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected ecap 0003[140] =3D Serial 1 001517ffff51bcba > I'm assuming you do *not* have any iflib or em(4) tuning options set ei= ther. Nope. Jung-uk Kim --2Vi9i3vMVV19iXHJ1g67uHmRrots2Ihbf-- --J1hOlhspkf7O88ngKucbkkSsw97He1tcL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlm5um8ACgkQfJ+WJvzb 8Ua+gQf/VQwJJBLjSua22uIEtmJvtyAEVyMSBxIjtEe/gfC3RxeqcaEgVWSYiZ5b 1E/Jf9BnK1YfVLS0bIfdI1gfCkaiWvLVlSQMETcupr17gOHMgzLNNbRqqXT6/DUv yN/QOtfNoUideReBCwU6lE+glFmuasI1EKVgEWsO8ICaW0dqAzIr7lMSZYeLqVMs oo95cwxD4dRNj6Ddy/DVk11sO+iqBZsx1h+lBUijiEd1/GYInpy0K6o5hjT2riW1 Guq385L1WR50jLRMkcGtlSVOCm9HIMoJlNdEiK6rCOK/EAV0Meep0o+Pp5b0UbMm UGO0EObH9zVVs4Ix6gqMSE1TIfaYwQ== =rq+H -----END PGP SIGNATURE----- --J1hOlhspkf7O88ngKucbkkSsw97He1tcL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a268f351-cec4-ca98-28a2-d35561463f8f>