https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546
--- Comment #17 from Robin Haberkorn <robin.haberk...@googlemail.com> ---
Well except, that it doesn't. Because it's obviously a memory corruption issue:
(kgdb) f 8
#8 iwl_mvm_bt_notif_per_link (mvm=0xfffffe00f1bb2508, vif=0xfffffe00f33cde80,
data=0xfffffe00c294bd40, link_id=0) at
/usr/src/sys/contrib/dev/iwlwifi/mvm/coex.c:292
292 chanctx_conf->def.chan->band != NL80211_BAND_2GHZ)) {
(kgdb) f 8
#8 iwl_mvm_bt_notif_per_link (mvm=0xfffffe00f1bb2508, vif=0xfffffe00f33cde80,
data=0xfffffe00c294bd40, link_id=0) at
/usr/src/sys/contrib/dev/iwlwifi/mvm/coex.c:292
292 chanctx_conf->def.chan->band != NL80211_BAND_2GHZ)) {
(kgdb) p chanctx_conf->def.chan
$1 = (struct linuxkpi_ieee80211_channel *) 0x8086b85b
(kgdb) p *chanctx_conf->def.chan
Cannot access memory at address 0x8086b85b
It's only sometimes resulting in unexpected NULL pointers.
b...@freebsd.org, perhaps it would be worth to pull in upstream patches? The
last
update was in May of 2023. Actually, considering that this driver is supposed
to be synced with the Linux kernel version, shouldn't that be the first thing
we try?
--
You are receiving this mail because:
You are on the CC list for the bug.
