Bug 266277 - iwm(4) firmware assert
Summary: iwm(4) firmware assert
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Bjoern A. Zeeb
URL:
Keywords:
Depends on:
Blocks: 277512
  Show dependency tree / graph
 
Reported: 2022-09-07 17:55 UTC by Bjoern A. Zeeb
Modified: 2024-03-05 21:05 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bjoern A. Zeeb freebsd_committer freebsd_triage 2022-09-07 17:55:22 UTC 
That's what happens if I switch to the old one ... haven't seem one of those on iwm(4) in ages ...  *sigh*  That's an LQ command in RUN state.

iwm0: dumping device error log
iwm0: Start Error Log Dump:
iwm0: Status: 0x3, count: 6
iwm0: 0x0000090A | ADVANCED_SYSASSERT          
iwm0: 000002F0 | trm_hw_status0
iwm0: 00000000 | trm_hw_status1
iwm0: 0000E258 | branchlink2
iwm0: 0002730C | interruptlink1
iwm0: 00000000 | interruptlink2
iwm0: 000000FF | data1
iwm0: 0002F4DC | data2
iwm0: DEADBEEF | data3
iwm0: 3B8009DF | beacon time
iwm0: B116A452 | tsf low
iwm0: 00000021 | tsf hi
iwm0: 00000000 | time gp1
iwm0: 9D16F5AA | time gp2
iwm0: 00000000 | uCode revision type
iwm0: 00000016 | uCode version major
iwm0: 00058404 | uCode version minor
iwm0: 00000230 | hw version
iwm0: 0000FF0F | board version
iwm0: 0013001C | hcmd
iwm0: 00022002 | isr0
iwm0: 00000000 | isr1
iwm0: 08001802 | isr2
iwm0: 0041F8C1 | isr3
iwm0: 00000000 | isr4
iwm0: 00004110 | last cmd Id
iwm0: 00000000 | wait_event
iwm0: 00009DCC | l2p_control
iwm0: 00000020 | l2p_duration
iwm0: 00000000 | l2p_mhvalid
iwm0: 00000090 | l2p_addr_match
iwm0: 0000008F | lmpm_pmg_sel
iwm0: 03071928 | timestamp
iwm0: 00007080 | flow_handler
iwm0: Start UMAC Error Log Dump:
iwm0: Status: 0x3, count: 7
iwm0: 0x00000070 | ADVANCED_SYSASSERT
iwm0: 0x00000000 | umac branchlink1
iwm0: 0xC0082F64 | umac branchlink2
iwm0: 0xC008940A | umac interruptlink1
iwm0: 0xC0081000 | umac interruptlink2
iwm0: 0x00000800 | umac data1
iwm0: 0xC0081000 | umac data2
iwm0: 0xDEADBEEF | umac data3
iwm0: 0x00000016 | umac major
iwm0: 0x00058404 | umac minor
iwm0: 0xC0886280 | frame pointer
iwm0: 0xC0886280 | stack pointer
iwm0: 0x09F3004E | last host cmd
iwm0: 0x00000000 | isr status reg
iwm0: driver status:
iwm0:   tx ring  0: qid=0  cur=20  queued=1  
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  
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=244 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:   tx ring 30: qid=30 cur=0   queued=0  
iwm0:   rx ring: cur=119
iwm0:   802.11 state 5
iwm0: iwm_intr: controller panicked, iv_state = 5; restarting
Comment 1 Bjoern A. Zeeb freebsd_committer freebsd_triage 2022-09-07 17:56:02 UTC 
I guess if anyone it's me who might look into this ..
Comment 2 Bjoern A. Zeeb freebsd_committer freebsd_triage 2023-10-17 22:35:06 UTC 
Crashed iwm(4) again in a hotel but this time it couldn't even get the errlog.
No idea what changed there but no longer helpful at all.
Someone might want to check how/when this can happen.

iwm0: device timeout
iwm0: dumping device error log
iwm0: errlog not found, skipping


Also (re-)assigning to wireless.
Comment 3 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-03-05 21:05:51 UTC 
Close it;  overcome by events but good to have it for reference.