Date: Wed, 28 Dec 2022 21:51:31 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Marco <freebsd-wireless@lordsith.net> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: New laptop: AC 9461/9560: iwm or iwlwifi? Message-ID: <69oq98r0-4r8-16s6-3779-82q158sp044@mnoonqbm.arg> In-Reply-To: <Y6DtNJZ%2BWvzP%2BLEH@freedom.nl> References: <srp28qr-1p8r-qsp7-6197-67359o129r35@mnoonqbm.arg> <a04c03db-3c0c-037b-3a81-221e6abd2151@netfence.it> <537f4871-5184-394e-1f93-bf625dc088cf@netfence.it> <q35r8954-195o-3rr6-9055-124sqo62o29p@SerrOFQ.bet> <Y5OueCTI/obivzkR@freedom.nl> <psr5s1os-9qn9-73q7-pr43-p3pp8s01164@mnoonqbm.arg> <Y6DP4j8AApeotsVo@freedom.nl> <Y6DWyDbEcLB1MPaS@freedom.nl> <Y6DZJT5mNJB8vuwi@freedom.nl> <s0s6p86n-325-7r4q-12r2-164r929r4775@mnoonqbm.arg> <Y6DtNJZ%2BWvzP%2BLEH@freedom.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Dec 2022, Marco wrote: > On Mon, Dec 19, 2022 at 10:07:50PM +0000, you (Bjoern A. Zeeb) sent the following to [freebsd-wireless] : >> You could try a devctl reset ... between detach and set driver. >> >> Also you could try to stop the iwm0 (wlan0) before detaching and see if >> that gets a clean(er) shutdown (service netif destroy wlan0 && devctl >> detach ...) > > I rebooted with both wlans_ entries in rc.conf but not having any > devmatch_blocklist active. > wlan0 got autocreated with iwm0 as parent and is fuctioning. > So at least having 2 wlans_ entries doesn't seem to hurt. > Also if_iwlwifi.ko is listed in the kldstat output: > > # kldstat | grep -e wlan -e wi-fi -e wifi -e iwm > 3 1 0xffffffff82141000 3130 wlan_xauth.ko > 17 1 0xffffffff850c7000 880c8 if_iwlwifi.ko > 18 1 0xffffffff85150000 17310 if_iwm.ko > 21 1 0xffffffff85200000 28fee8 iwm9000fw.ko > > I stopped wlan0 and performed the devctl reset in between the detach and > set driver steps but still wasn't successful: > > # service netif stop wlan0 && devctl detach pci0:0:20:3 && devctl reset pci0:0:20:3 && devctl set driver pci0:0:20:3 iwlwifi > > wlan0 got destroyed and the following was logged in /var/log/messages: > > Dec 19 22:31:42 harbinger wpa_supplicant[73966]: wlan0: CTRL-EVENT-DISCONNECTED bssid=72:a7:41:9b:4f:da reason=3 locally_generated=1 > Dec 19 22:31:42 harbinger wpa_supplicant[73966]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all > Dec 19 22:31:42 harbinger syslogd: last message repeated 1 times > Dec 19 22:31:42 harbinger wpa_supplicant[73966]: wlan0: CTRL-EVENT-TERMINATING > Dec 19 22:31:42 harbinger kernel: [680] wlan0: link state changed to DOWN > Dec 19 22:31:42 harbinger rtsold[63523]: <rtsock_input_ifannounce> interface wlan0 removed > Dec 19 22:31:42 harbinger kernel: [680] iwm0: detached > Dec 19 22:31:42 harbinger kernel: [680] pci0:0:20:3: Transition from D0 to D3 > Dec 19 22:31:42 harbinger root[97472]: /etc/rc.d/netif: WARNING: wlan0 does not exist. Skipped. > Dec 19 22:31:42 harbinger kernel: [681] pci0:0:20:3: Transition from D0 to D3 > Dec 19 22:31:42 harbinger kernel: [681] iwlwifi0: <iwlwifi> mem 0xea238000-0xea23bfff irq 16 at device 20.3 on pci0 > Dec 19 22:31:42 harbinger kernel: [681] iwlwifi0: HW_REV=0xFFFFFFFF, PCI issues? > Dec 19 22:31:42 harbinger kernel: [681] device_attach: iwlwifi0 attach returned 5 > > Despite pci0:0:20:3 seeemingly "attached" to iwlwifi0 I can't seem to > get wlan0 created using iwlwifi as parent. So you by any chance have any power saving sysctl (or tunables) set? I see two transiotions from D0 to D3 logged but nothing taking the device out of D3 gets logged (could be an omission elsewhere). Can you show a pciconf -lBbcevV iwlwifi0 or pciconf -lBbcevV pci0:0:20:3 (which ever one works in that state)? /bz -- Bjoern A. Zeeb r15:7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69oq98r0-4r8-16s6-3779-82q158sp044>