Date: Fri, 19 Nov 2010 00:44:54 +0000 From: Paul B Mahol <onemda@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD current mailing list <current@freebsd.org> Subject: Re: net.link.log_link_state_change broken? Message-ID: <AANLkTi=dzGoW09ho9dYsCzuBgHsepF8ekbEr-DuZozE%2B@mail.gmail.com> In-Reply-To: <20101118072341.V24596@maildrop.int.zabbadoz.net> References: <AANLkTimPoVaZ-syEog7Xmkinv5GLqqFNfzCvFqEqBD0j@mail.gmail.com> <20101118072341.V24596@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/18/10, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote: > On Tue, 2 Nov 2010, Paul B Mahol wrote: > > Hi, > >> It appears we do not log such events anymore (at least with wlan >> devices) in console. >> >> I set this sysctl to 0 via sysctl.conf, if I set it to 1, nothing will >> change. >> >> Because I had loging disabled for very long time I encountered this >> problem just now. > > not sure. Might be, might not be. Have you further looked into this? > > I at least see: > ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, > LINK_STATE_UP); > ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, > LINK_STATE_DOWN); That part is not problematic, klog part is. Messages of link state changes are not available in console but are available in klog and in console once you open it with cat. Reading comment it appears that logic is inverted in code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=dzGoW09ho9dYsCzuBgHsepF8ekbEr-DuZozE%2B>