This is caused by https://svnweb.freebsd.org/changeset/base/339634.
--- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert <cy.schub...@cschubert.com> or <c...@freebsd.org> The need of the many outweighs the greed of the few. --- -----Original Message----- From: David Wolfskill Sent: 23/10/2018 04:39 To: curr...@freebsd.org Subject: Panic during network initialization after r339583 -> r339639 Gory details in <http://www.catwhisker.org/~david/FreeBSD/head/r339639/>. I snapped some screenshots, but can't associate using laptop's iwn(4) (in stable/11, stable/12, or head/13) at the place I'm currently staying. (I may be able to at least get the screenshots uploaded to the Web server later on today.) But since I was able to get a dump, they are probably not very interesting. It looks (to my semi-trained eye) as if iflib is implicated -- partly because the backtrace mentions it (ref. frame #14 from the backtrace in core.txt.8), and partly because I only saw the panic on my laptop, the wired NIC for which is em(4), while my build machine (which uses rl(4)) had no issues. I'm happy to poke and/or test, but will need some direction to do so. Peace, david -- David H. Wolfskill da...@catwhisker.org Women (and decent men): vote against supporters of Trump's misogyny! See http://www.catwhisker.org/~david/publickey.gpg for my public key. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
