Ping-Ke Shih <pkshih@realtek.com> writes:

> Since I saw 'NetworkManager' and 'hostapd' in code trace, I would like to know
> if you have two virtual interfaces, which for STA and AP modes? (Please check
> this by 'iw dev') If so, is it possible to remove hostapd (AP mode) to see if
> this is a factor causing crash.

I use hostapd as part of a Wi-Fi hotspot setup for this laptop. I REALLY
wish I'd connected the dots earlier and realised that it could be
related to this issue. While running gbcbefbd032 (first bad commit), I
disabled all the components of my setup and the issue went away; then I
enabled them one by one until the issue emerged. I'll walk you through
the relevant details, and my observations during this process.

I create a virtual interface for hostapd using this systemd unit:

```
[Unit]
Requires=sys-subsystem-net-devices-wlo1.device
After=network.target
After=sys-subsystem-net-devices-wlo1.device
[Service]
Type=oneshot
ExecStart=/usr/bin/iw dev wlo1 interface add wlo1_ap type __ap addr "xx:xx:xx:xx:xx:xx"
ExecStart=/usr/bin/ip addr add 192.168.30.1/24 dev wlo1_ap
[Install]
WantedBy=multi-user.target
```

I need the '__ap' type because my card doesn't support two interfaces in
managed mode; see [1] for details.

[1] https://wiki.archlinux.org/title/Talk:Software_access_point#Two_interfaces_on_same_card

Then I configure NetworkManager to ignore this interface.

```
;; in /etc/NetworkManager/conf.d/unmanaged.conf
[keyfile]
unmanaged-devices=interface-name:wlo1_ap
```

Coming to hostapd - this is where it gets rather complicated. First off,
let me mention that when I enabled hostapd.service again, I started
seeing the 'phy0: resume with hardware scan still in progress' warnings,
which had gone away upto this point.

Next - once I enabled hostapd.service, I was able to reproduce the
crashes. However, the dmesg in the crash log was different from what I
see when I have the rest of my setup enabled (I hadn't applied either
patch when this crash happened, and it's on b54846da4 because that's the
earliest bad commit in which I'm able to produce crash logs at all, as I
described in my original message):