Date: Tue, 23 May 2017 10:28:02 -0700 From: Pete Wright <pete@nomadlogic.org> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Panic On Restarting netif Message-ID: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org>
next in thread | raw e-mail | index | archive | help
This morning I was restarting netif on my system running the drm-next
branch off of CURRENT and experienced a kernel panic. My system has the
following wireless NIC:
iwm0@pci0:1:0:0: class=0x028000 card=0x44108086 chip=0x31658086
rev=0x79 hdr=0x00
vendor = 'Intel Corporation'
device = 'Wireless 3165'
class = network
Here is what I think is the relevant section from the core.txt file that
was generated:
Unread portion of the kernel message buffer:
MCA: Bank 6, Status 0xfe00000000801136
MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005
MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2
MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error
MCA: Address 0xaa000000
MCA: Misc 0x30e2000086
vt_kms_postswitch() at vt_kms_postswitch+0x52/frame 0xfffffe034114cfb0
vt_window_switch() at vt_window_switch+0xdb/frame 0xfffffe034114cff0
vtterm_cngrab() at vtterm_cngrab+0x20/frame 0xfffffe034114d010
cngrab() at cngrab+0x42/frame 0xfffffe034114d030
vpanic() at vpanic+0x10a/frame 0xfffffe034114d0b0
panic() at panic+0x43/frame 0xfffffe034114d110
mca_intr() at mca_intr+0xab/frame 0xfffffe034114d130
trap() at trap+0xc0/frame 0xfffffe034114d2f0
calltrap() at calltrap+0x8/frame 0xfffffe034114d2f0
--- trap 0x1c, rip = 0xffffffff80394b74, rsp = 0xfffffe034114d3c8, rbp =
0xfffffe034114d420 ---
rijndaelEncrypt() at rijndaelEncrypt+0x2a4/frame 0xfffffe034114d420
ccmp_decap() at ccmp_decap+0x480/frame 0xfffffe034114d540
The wireless network I was joining has the following wpa_supplicant config:
network={
ssid="XXXX"
#+ any_bssid
key_mgmt=WPA-EAP
proto=RSN
eap=PEAP
identity="homer@simpson"
password="doh!"
eap_workaround=1
}
I can post the backtrace or other data if needed. This is the first
time I've seen this error, so I'm not sure I'll be able to easily
reproduce. Also, if this isn't a known issue and is probably related to
wireless I can open a PR.
Cheers!
-pete
--
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98a7a7a7-0227-385f-4cee-87f352490345>