exception with iwm (intel 8260) under CURRENT
howdy - just updated my current workstation yesterday and while the wireless interface is working i noticed several of these exceptions while the device was being brought up: bus_dma_tag_create with the following non-sleepable locks held: exclusive sleep mutex iwm0 (network driver) r = 0 (0xfe00a5b6c010) locked @ /usr/home/pete/git/freebsd/sys/dev/iwm/if_iwm.c:2889 stack backtrace: #0 0x80bd16a3 at witness_debugger+0x73 #1 0x80bd2a81 at witness_warn+0x461 #2 0x8119d32e at bus_dma_tag_create+0x7e #3 0x83151fd4 at iwm_dma_contig_alloc+0x64 #4 0x83155823 at iwm_save_fw_paging+0x113 #5 0x8314f267 at iwm_mvm_load_ucode_wait_alive+0x1247 #6 0x83150f8a at iwm_init_hw+0x9a #7 0x8315144f at iwm_init+0x2f #8 0x8314de66 at iwm_parent+0x46 #9 0x80bc44ac at taskqueue_run_locked+0x14c #10 0x80bc5278 at taskqueue_thread_loop+0x88 #11 0x80b2b174 at fork_exit+0x84 #12 0x8100bede at fork_trampoline+0xe here's the output of the device from pciconf: iwm0@pci0:1:0:0: class=0x028000 card=0x00108086 chip=0x24f38086 rev=0x3a hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 8260' class = network not sure if this is a known issue or not. if its new i can file a PR, let me know. cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Panic On Restarting netif
On 05/24/2017 01:58, Andriy Gapon wrote: On 23/05/2017 20:45, Pete Wright wrote: On 05/23/2017 10:42, Andriy Gapon wrote: On 23/05/2017 20:28, Pete Wright wrote: MCA: Bank 6, Status 0xfe801136 MCA: Global Cap 0x0c08, Status 0x0005 MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. The CPU might have started dying. I hope that's not the case, this is a new Kabylake system :( The hope could be that this was a one-time glitch (proverbial cosmic ray). Machine Check Architecture is designed to report hardware problems. cheers - thanks for pointing that logline out btw! i was so focused on the following lines i missed the MCA lines. d'oh! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Panic On Restarting netif
On 05/23/2017 10:42, Andriy Gapon wrote: On 23/05/2017 20:28, Pete Wright wrote: MCA: Bank 6, Status 0xfe801136 MCA: Global Cap 0x0c08, Status 0x0005 MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. The CPU might have started dying. I hope that's not the case, this is a new Kabylake system :( Time to run extended BIOS diagnostics over lunch. cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Panic On Restarting netif
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 0xfe801136
MCA: Global Cap 0x0c08, Status 0x0005
MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2
MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error
MCA: Address 0xaa00
MCA: Misc 0x30e286
vt_kms_postswitch() at vt_kms_postswitch+0x52/frame 0xfe034114cfb0
vt_window_switch() at vt_window_switch+0xdb/frame 0xfe034114cff0
vtterm_cngrab() at vtterm_cngrab+0x20/frame 0xfe034114d010
cngrab() at cngrab+0x42/frame 0xfe034114d030
vpanic() at vpanic+0x10a/frame 0xfe034114d0b0
panic() at panic+0x43/frame 0xfe034114d110
mca_intr() at mca_intr+0xab/frame 0xfe034114d130
trap() at trap+0xc0/frame 0xfe034114d2f0
calltrap() at calltrap+0x8/frame 0xfe034114d2f0
--- trap 0x1c, rip = 0x80394b74, rsp = 0xfe034114d3c8, rbp =
0xfe034114d420 ---
rijndaelEncrypt() at rijndaelEncrypt+0x2a4/frame 0xfe034114d420
ccmp_decap() at ccmp_decap+0x480/frame 0xfe034114d540
The wireless network I was joining has the following wpa_supplicant config:
network={
ssid=""
#+ 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
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: iwm Intel 3165
On 03/29/2017 22:59, Adrian Chadd wrote: hi! Just don't load it in /boot/loader.conf . That's still buggy. thanks - loading it via rc.conf did the trick! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
iwm Intel 3165
Hi there, I have a new laptop with the following Intel wireless chipset that seems to be having problems getting enabled: iwm0@pci0:1:0:0:class=0x028000 card=0x44108086 chip=0x31658086 rev=0x79 hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 3165' class = network I have the following configured in my loader.conf: if_iwm_load="YES" iwm3160fw_load="YES" iwm7260fw_load="YES" iwm7265fw_load="YES" iwm8000Cfw_load="YES" I have seen the following error on both the latest 12-CURRENT snapshot as well as the drm-next branch that work is being done on to support newer Intel graphics and can reproduce on both code bases. Here is what I'm seeing in the dmesg buffer: iwm0: <Intel(R) Dual Band Wireless AC 3165> mem 0xd100-0xd1001fff at device 0.0 on pci1 iwm7265Dfw: root not mounted yet, no way to load image iwm0: could not read firmware iwm7265Dfw (error 0) iwm0: dumping device error log iwm0: Invalid error log pointer 0x iwm0: driver status: iwm0: tx ring 0: qid=0 cur=0 queued=0 iwm0: tx ring 1: qid=1 cur=0 queued=0 iwm0: tx ring 2: qid=2 cur=0 queued=0 iwm0: tx ring 3: qid=3 cur=0 queued=0 uhub0: iwm0: tx ring 4: qid=4 cur=0 queued=0 iwm0: tx ring 5: qid=5 cur=0 queued=0 iwm0: tx ring 6: qid=6 cur=0 queued=0 iwm0: tx ring 7: qid=7 cur=0 queued=0 iwm0: tx ring 8: qid=8 cur=0 queued=0 iwm0: tx ring 9: qid=9 cur=0 queued=0 iwm0: tx ring 10: qid=10 cur=0 queued=0 iwm0: tx ring 11: qid=11 cur=0 queued=0 iwm0: tx ring 12: qid=12 cur=0 queued=0 iwm0: tx ring 13: qid=13 cur=0 queued=0 iwm0: tx ring 14: qid=14 cur=0 queued=0 iwm0: tx ring 15: qid=15 cur=0 queued=0 iwm0: tx ring 16: qid=16 cur=0 queued=0 iwm0: tx ring 17: qid=17 cur=0 queued=0 iwm0: tx ring 18: qid=18 cur=0 queued=0 iwm0: tx ring 19: qid=19 cur=0 queued=0 iwm0: tx ring 20: qid=20 cur=0 queued=0 iwm0: tx ring 21: qid=21 cur=0 queued=0 iwm0: tx ring 22: qid=22 cur=0 queued=0 iwm0: tx ring 23: qid=23 cur=0 queued=0 iwm0: tx ring 24: qid=24 cur=0 queued=0 iwm0: tx ring 25: qid=25 cur=0 queued=0 iwm0: tx ring 26: qid=26 cur=0 queued=0 iwm0: tx ring 27: qid=27 cur=0 queued=0 iwm0: tx ring 28: qid=28 cur=0 queued=0 iwm0: tx ring 29: qid=29 cur=0 queued=0 iwm0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 iwm0: rx ring: cur=0 iwm0: 802.11 state -1 iwm_intr: null vap iwm0: Failed to start INIT ucode: 35 When i try to configure the device the netif rc script errors out stating the device doesn't exist. Let me know if any additional debugging info would be helpful, and if this is a real issue I am def willing to help test patches etc. Cheers! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
