https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
ma...@mky.waw.pl changed:
What|Removed |Added
CC||ma...@mky.waw.pl
--- Comment #10
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #110 from ma...@mky.waw.pl ---
(In reply to marek from comment #109)
I am sorry. This comment should be pasted to:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286493
--
You are receiving this mail because:
You are on the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #107 from commit-h...@freebsd.org ---
A commit in branch releng/14.3 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=36174c38f9e3433e7fdb8b2f2923499dff67b2e7
commit 36174c38f9e3433e7fdb8b2f2923499dff67b2e7
Aut
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #106 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e0692e7bb6e8abcc55a2510dceea5f83e823a827
commit e0692e7bb6e8abcc55a2510dceea5f83e823a827
Autho
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #105 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=16d987fe781780100a31df30b9edd79ebb54f957
commit 16d987fe781780100a31df30b9edd79ebb54f957
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #104 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=84ca9ab010dc9bf1ce4f748100d5b15cf39f7b29
commit 84ca9ab010dc9bf1ce4f748100d5b15cf39f7b29
Autho
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #103 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=4a4eee553307a2e02c6ed4796d575bfce2857049
commit 4a4eee553307a2e02c6ed4796d575bfce2857049
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Eric Joyner changed:
What|Removed |Added
CC||e...@freebsd.org
--- Comment #102 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Joel Bodenmann changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #101
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Erik Inge Bolsø changed:
What|Removed |Added
CC||knan-...@modirum.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Alexander Ziaee changed:
What|Removed |Added
CC||zi...@runbox.com
--- Comment #99
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #98 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=618afeb7f3751ffb93a3d7ebbace4ec07b3e90cb
commit 618afeb7f3751ffb93a3d7ebbace4ec07b3e90cb
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #97 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=fe6e275dc6f7527961ceaf7ce2912a29cdbb00b3
commit fe6e275dc6f7527961ceaf7ce2912a29cdbb00b3
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Rene Ladan changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #96 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #95 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
commit 2372f8cc640c2f4ab82831e6ac0e27ab6c18321a
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
fly...@gmail.com changed:
What|Removed |Added
CC||fly...@gmail.com
--- Comment #94
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #93 from Al Hoang ---
Created attachment 255936
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255936&action=edit
/var/log/messages from today with message occurring
--
You are receiving this mail because:
You are o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Keywords|tracking|
--- Comment #92 from Bjoern A. Z
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Al Hoang changed:
What|Removed |Added
CC||hoa...@gmail.com
--- Comment #91 from A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #90 from Sergey A. Osokin ---
(In reply to Bjoern A. Zeeb from comment #85)
I'm talking about 14.1-p5, which is latest security release for 14.1, not sure
why are you switching to 14.1-RC.
In case that's the bug for release, i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #89 from Sergey A. Osokin ---
(In reply to Bjoern A. Zeeb from comment #87)
I'm looking for a way how to fix the issue, probably create an errata for the
FreeBSD 14.1-RELEASE.
I also found that the wlan0 network interface (bas
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Padukajorat changed:
What|Removed |Added
CC||fbugzi...@gmail.com
--- Comment #88
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #87 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Sergey A. Osokin changed:
What|Removed |Added
Resolution|FIXED |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Sergey A. Osokin changed:
What|Removed |Added
Resolution|FIXED |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Sergey A. Osokin changed:
What|Removed |Added
CC||o...@freebsd.org
--- Comment #8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Flags|mfc-stable14?, |mfc-stable14+,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Status|In Progress |Closed
Summary|iwlwifi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #81 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b5e3a31ac050dd376d19682fe0e595692ec3379f
commit b5e3a31ac050dd376d19682fe0e595692ec3379f
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #80 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=07da0ad63aa52999c0a381440104122a770decb5
commit 07da0ad63aa52999c0a381440104122a770decb5
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #79 from Cheng Cui ---
I happened to have a VM that can reproduce the "Invalid TXQ" by the method
listed as [3] in comment# 57. After commit 886653492945, the "Invalid TXQ" is
gone.
=== console output before commit 886653492945
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #78 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2ab1b827d49f473e30a91382d2ce03e268af45c5
commit 2ab1b827d49f473e30a91382d2ce03e268af45c5
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #77 from Bjoern A. Zeeb ---
(In reply to Vladislav Shabanov from comment #76)
Please open a new bug report with this information.
I would also be curious if anything got logged before the Queue stuck message.
If so please attac
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #76 from Vladislav Shabanov ---
(In reply to Ed Maste from comment #75)
Sorry. Maybe, my comment is not relevant to initial bug report. But I started
to resolve the wifi card issue with 'Invalid TXQ id' message and after update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #75 from Ed Maste ---
(In reply to Vladislav Shabanov from comment #74)
I don't see the Invalid TXQ message in your logs - can you confirm (or explain
what you mean by being the same problem)?
--
You are receiving this mail be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Vladislav Shabanov changed:
What|Removed |Added
CC||vlad.shaba...@gmail.com
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #73 from Ed Maste ---
(In reply to justinlbouchard from comment #72)
This issue may be fixed as of Bjoern's commit referenced in comment #71 (it is
for me). It should be merged into stable/14 before long, and after that will be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
justinlbouch...@icloud.com changed:
What|Removed |Added
CC||justinlbouch...@icloud.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
Flags||mfc-stable14?,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #71 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=886653492945f7e945eb9bdaf5bc2ae26df96236
commit 886653492945f7e945eb9bdaf5bc2ae26df96236
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #70 from rkober...@gmail.com ---
This is more of an "it didn't seem to screw up the AX211" report. No problems.
orksfine.With the patched code I get the following on loading:
Jun 6 16:25:41 ptavv kernel: Intel(R) Wireless WiFi b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #69 from Bjoern A. Zeeb ---
(In reply to Tom Jones from comment #68)
Thanks Tom for testing so quickly and reporting back.
I'll likely put the change into main the next days and by then others also have
a bit of time to test.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #68 from Tom Jones ---
With the patch applied I've been running for 4 hours without any issue. I'm not
sure if the environment to reproduce has existed as it is later in the day.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #67 from Bjoern A. Zeeb ---
Can people please try the patch from:
https://reviews.freebsd.org/D45508
If you don't use arc there's a "Download Raw Diff" link on the right side.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Tom Jones changed:
What|Removed |Added
CC||t...@freebsd.org
--- Comment #66 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Olivier Certner changed:
What|Removed |Added
CC||o...@freebsd.org
--- Comment #65
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #64 from rkober...@gmail.com ---
(In reply to Bjoern A. Zeeb from comment #62)
While I am not certain, I suspect that this issue was the result of a typo in
/etc/wpa_supplicant. I will be unable to test this until I try to connec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Chris Hutchinson changed:
What|Removed |Added
CC||portmas...@bsdforge.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #62 from Bjoern A. Zeeb ---
(In reply to rkoberman from comment #61)
Hi,
thanks for reporting. I have another question though:
> This is not my usual network. I am using my phone as a hotspot as my system
> has been unable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #61 from rkober...@gmail.com ---
Just rebooted my system after my network would not restart after the link to my
hotspot went down. The hotspot outage was unrelated to FreeBSD, but I was
usable to get the interface to associate w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
nunziotocci2...@gmail.com changed:
What|Removed |Added
CC||nunziotocci2...@gmail.co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #59 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=1665ef979d3adab05d178480077674ab5978e4f0
commit 1665ef979d3adab05d178480077674ab5978e4f0
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Maxim Usatov changed:
What|Removed |Added
CC||maxim.usa...@bcsatellite.ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #57 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #56)
What I understand after reading the comment #49, is that there is still
remaining work to do to fix this `Invalid TXQ id` problem. And if I understand
correct
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #56 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #54)
See Comment 49 -- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382#c49
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #55 from Cheng Cui ---
(In reply to Cheng Cui from comment #54)
Same in the other VM. D43944 and D43967 on top of latest main does not fix the
`Invalid TXQ id` problem.
=== dmesg snip ===
..
[1.417096] pci0: driver added
[1.61
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #54 from Cheng Cui ---
If the remaining patches are only D43944 and D43967 for this PR, it looks the
problem still exists (see below) after applying the two patches. I will test
again on the other VM which can also reproduce the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #53 from m...@dymek.me ---
not in front of my laptop right now but i’m using the latest staging of 14.0
because i was having a issue with iwlwifi.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #52 from Ed Maste ---
(In reply to mark from comment #50)
> well i now have a new issue. wifi was working for a bit then with me not
> changing anything
What version of FreeBSD are you trying? I.e., `uname -a`
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #51 from m...@dymek.me ---
(In reply to mark from comment #50)
uh… as mysteriously as it stopped working it has now started working again.
clearly something is unhappy.
--
You are receiving this mail because:
You are on the CC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
m...@dymek.me changed:
What|Removed |Added
CC||m...@dymek.me
--- Comment #50 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #49 from Bjoern A. Zeeb ---
(In reply to Bjoern A. Zeeb from comment #48)
Thanks Ed for all the traces in private.
I believe at this point we have to bite the bullet and do a full pass over
net80211 and all the wireless driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #48 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #47)
I am currently trying to track it down with Ed testing.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #47 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #43)
It's better to have a separate patch for the extra print.
With D43944 and D43879 on top of the latest main kernel, the "Invalid TXQ id"
still shows up:
root
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Bjoern A. Zeeb changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #46 from commit-h...@freebsd.org ---
A commit in branch releng/13.3 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=401dbf9cfc0cfb2a02355d41bf73e146bd3dfb74
commit 401dbf9cfc0cfb2a02355d41bf73e146bd3dfb74
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #45 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=763b10806cd4ebdcbd2b6753d4f50ec088dc57fb
commit 763b10806cd4ebdcbd2b6753d4f50ec088dc57fb
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #44 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=035424535b09c57971df2064ad7678e90bd8cb3a
commit 035424535b09c57971df2064ad7678e90bd8cb3a
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #43 from Bjoern A. Zeeb ---
Anyone who's seen this, can you please test:
https://reviews.freebsd.org/D43944
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #42 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=fa4e4257943650c0b5f58c01bb0bdfadea61dfb2
commit fa4e4257943650c0b5f58c01bb0bdfadea61dfb2
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #41 from Ed Maste ---
dmesg snippit from the Framework laptop which produces one 'Invalid TXQ id' at
boot, with the additional debugging:
iwlwifi0: lkpi_iv_update_bss:2574: lvif 0xfe01424ae000 vap
0xfe01424ae010 iv_bss
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #40 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #39)
Thanks. With these extra prints. The dmesg after booting shows:
[1.427073] pci0: driver added
[1.632542] wlan0: bpf attached
[1.632744] iwlwifi0: lkpi_iv_upda
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #39 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #38)
sta is added to FW and in state IEEE80211_STA_NONE sta->lsta->ni is
0xfe00ab574000
IEEE80211_STA_NONE can be from scan-to-auth, assoc-down, run-init.
Gi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #38 from Cheng Cui ---
After applying D43879 and D43909 with the latest Feb 15 main kernel, still
seeing the "Invalid TXQ" print from the vm4 I managed to reproduce the story.
root@n2fbsdtmp:~ # uname -a
FreeBSD n2fbsdtmp 15.0-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #37 from Ed Maste ---
On boot I get at startup (same Framework laptop case as comment #26):
Invalid TXQ id
iwl_mvm_tx_mpdu:1208: fc 0x00b0 tid 8 txq_id 65535 mvm 0xfe0142c3a448 skb
0xf800029a6000 { len 30 } info 0xf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #36 from Cheng Cui ---
(In reply to Cheng Cui from comment #35)
Fortunately, I have kept my World build log and did the same way this time. And
finally I figured out how to reproduce the "panic: lkpi_sta_auth_to_scan"
crash.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #35 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #33)
Please find the extra debug info in attached "repro after applying D43879 on
top of D43389, D43725, D43753".
Meanwhile, I have an idea to create a new VM but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #34 from Cheng Cui ---
Created attachment 248462
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=248462&action=edit
repro after applying D43879 on top of D43389, D43725, D43753
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #33 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #32)
Can you apply https://reviews.freebsd.org/D43879
it's not been tested or even compiled so you may have to make it work but
you'll get the idea. It should d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #32 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #30)
It is reliably reproduced. I have attached the "iwl_mvm_tx_mpdu log messages"
from console after running the below script. Please let me know if there is any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #31 from Cheng Cui ---
Created attachment 248461
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=248461&action=edit
iwl_mvm_tx_mpdu log messages
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #30 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #29)
> [..] The patches does not prevent "please report to PR 274382" from showing
> up.
Can you reliably reproduce it? There's some more debugging to be added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #29 from Cheng Cui ---
The patches from D43389, D43725, D43753 in combination seem to work and
prevented the crash "panic: lkpi_sta_auth_to_assoc" from "service netif
restart" or simply booting the kernel. The patches does not p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #28 from rkober...@gmail.com ---
(In reply to Ed Maste from comment #26)
This was a problem I was seeing with the lkpi prior to the update from
drm-515-kmod to drm-61-kmod. I see nothing likely to be involved between the
two. I w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #27 from Bjoern A. Zeeb ---
(In reply to Ed Maste from comment #26)
Thanks for the update. I'll try to add a lot more logging to this one once
other things are in. It seems we are trying to send an ASSOC REQ with a sta
which
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #26 from Ed Maste ---
(In reply to Bjoern A. Zeeb from comment #25)
For reference this is on my Framework laptop (i7-1165G7 Tiger Lake CPU,
8086:2725 "Wi-Fi 6 AX210/AX211/AX411 160MHz"). It occurs on on startup, with
wpa_supplic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #25 from Bjoern A. Zeeb ---
(In reply to Ed Maste from comment #24)
Did you have an accompanying log from wpa_supplicant of that time?
Was there a re-assoc event or something?
--
You are receiving this mail because:
You are o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #24 from Ed Maste ---
With the three patches applied iwlwifi worked fine for several hours.
dmesg snippet:
iwlwifi0: mem 0x7a20-0x7a203fff at device 0.0 on pci2
iwlwifi0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #23 from Ed Maste ---
I'll grab the patches from Phab, or grab from a public git repo, and try later
today.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #22 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #21)
I am about to send the same recommendation of applying the combined D43389,
D43725 and D43753.
I have been testing it for a few hours now, so far so good.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #21 from Bjoern A. Zeeb ---
(In reply to Ed Maste from comment #19)
Can you try the patches pending in Phabricator? D43389, D43725 and D43753? I
am waiting on review...
--
You are receiving this mail because:
You are on the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #20 from Cheng Cui ---
(In reply to Ed Maste from comment #19)
Hi Ed,
You can try my workaround mentioned in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276562#c9, to bypass this
"service netif restart" panic. Hope it wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #19 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #18 from rkober...@gmail.com ---
Just to update to my current status, since my update to head on Jan 13 I have
not had a single incident of "Invalid TXQ id". Possibly related, drm-61-kmod no
longer fails to load firmware on my Al
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #17 from Bjoern A. Zeeb ---
Tracking myself:
iwl_mvm_tx_mpdu:1204: fc 0x00b0 tid 8 txq_id 65535 mvm 0xfe00b09dc448 skb
0xf80001b59000 { len 30 } info 0xfe000edf5ce8 sta 0xf8002320f080
(if you see this please rep
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
rkober...@gmail.com changed:
What|Removed |Added
CC||rkober...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
Hiroki Sato changed:
What|Removed |Added
CC||h...@freebsd.org
--- Comment #15 fro
1 - 100 of 116 matches
Mail list logo
