Date: Fri, 16 Aug 2019 05:45:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239822] deadlock since FreeBSD 12.0 p9 Message-ID: <bug-239822-227-DkDCztc47o@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239822-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239822-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=3D239822 --- Comment #8 from Martin Birgmeier <d8zNeCFG@aon.at> --- I am not sure the following is of relevance, but /var/log/messages yesterday was spammed like this: Aug 15 23:00:00 mizar newsyslog[10909]: logfile turned over due to size>100= 0K Aug 15 23:00:00 mizar wpa_supplicant[394]: wlan0: Reject scan trigger since= one=20 is already pending Aug 15 23:00:00 mizar wpa_supplicant[394]: wlan0: Failed to initiate AP scan Aug 15 23:00:01 mizar wpa_supplicant[394]: wlan0: Reject scan trigger since= one=20 is already pending Aug 15 23:00:01 mizar wpa_supplicant[394]: wlan0: Failed to initiate AP scan Aug 15 23:00:02 mizar wpa_supplicant[394]: wlan0: Reject scan trigger since= one=20 is already pending Aug 15 23:00:02 mizar wpa_supplicant[394]: wlan0: Failed to initiate AP scan Aug 15 23:00:03 mizar wpa_supplicant[394]: wlan0: Reject scan trigger since= one=20 is already pending But is it doing this since at least Aug 10 (which is the oldest messages le= ft due to excessive rotation because of this). --=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-239822-227-DkDCztc47o>