Subject: Re: Noisy wm output during boot
To: None <current-users@NetBSD.org>
From: Bernd Ernesti <firstname.lastname@example.org>
Date: 02/25/2006 19:58:56
On Sat, Feb 25, 2006 at 07:02:09PM +0100, dieter Roelants wrote:
> On 02/24/06 14:49:11, Bernd Ernesti wrote:
> >Note the DOWN and UP events.
> >At least the DOWN even looks wrong.
> Are you sure? My laptop's fxp also goes 2 times down (and then comes
> back up) while booting, but watching my switch, that seems to be
> reality and is no different to older kernels, where this message is not
Thats maybe true, but printing an down event while the network will be
configured for the first time looks wrong.
And yes, I get that for other network interfaces too and fxp seems to going
down twice, but that maybe related that i use it for my pppoe session.
Joerg: Juergen Hannken-Illjes pointed out in another reply that this
message is related to one change from you to sys/dev/mii/mii_physubr.c, Rev 1.46
Hmm, if_link_state_change seems to be introduced by dyoung in rev 1.159 of
sys/net/if.c, which does contain the log function for "link state changed to".
IMHO this kind of message should be proteced by a verbose kernel option.
> >P.S how do I increase number of lines for the wsoncs scrollback?
> options MSGBUFSIZE=integer
I'm not talking about the dmesg buffer, which is affected by MSGBUFSIZE.