Date: Thu, 28 Nov 2024 00:47:41 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283015] iwlwifi: kernel panic: sleeping thread holds lvif Message-ID: <bug-283015-227-uuu85Xbw4k@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283015-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283015-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283015 --- Comment #1 from Graham Perrin <grahamperrin@gmail.com> --- Created attachment 255501 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D255501&action= =3Dedit A photograph of the primary screen during the panic, frozen at 09:39:04 Greyscale. The original colour version (too large) failed to attach at comm= ent 0. <https://bsd-hardware.info/?probe=3Dc8d95da1f8>; was the result of a probe at 06:02 UTC the day before the panic (2024-11-26). Notable, before the panic on 2024-11-27:=20 - at home, I would have routinely ifconfig gif0 down && ifconfig em0 down because (a) I rarely require the gif0 tunnel for IPv6 with em0;=20 and (b) usually I prefer em(4), but recently I'm testing iwlwifi(4) - sleep of the OS at home, whilst connected to ssid 'piano5' - wake of the OS at work, miles away, apparently still connected to the=20 home network ifconfig wlan1 down ifconfig wlan1 up - not connected to the required network (ssid eduroam) route delete default ; ifconfig gif0 down ; service netif stop em0 > & /dev/null ; ifconfig wlan0 destroy ; sleep 1 ; service netif start em0 > & /dev/null ; sleep 15 ; resolvconf -i ; route show default ; ping -4 -c 2 freshports.org --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283015-227-uuu85Xbw4k>