Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Jun 2007 11:57:26 +0200
From:      Roberto Nunnari <roberto.nunnari@supsi.ch>
To:        freebsd-questions@freebsd.org
Cc:        Kevin Downey <redchin@gmail.com>
Subject:   Re: em0 net interface Link state changed to UP too late at boot time
Message-ID:  <4684D786.7080800@supsi.ch>
In-Reply-To: <1d3ed48c0706281423y2915af7dka05c35873dda716f@mail.gmail.com>
References:  <4683ED4A.2040602@supsi.ch> <4683F051.8040201@supsi.ch>	<44ps3gx7z4.fsf@be-well.ilk.org> <46840212.7070405@supsi.ch>	<1d3ed48c0706281311k60041069k3d7eb0c817b5571c@mail.gmail.com>	<4684228D.8030208@supsi.ch> <1d3ed48c0706281423y2915af7dka05c35873dda716f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kevin.

Ok. I'll try that.

Thank you.

-- 
Robi


Kevin Downey wrote:
> On 6/28/07, Roberto Nunnari <roberto.nunnari@supsi.ch> wrote:
>> Hi Kevin.
>>
>> No DHCP. The box gets a static address. From rc.conf:
>>
>> ifconfig_em0="inet aaa.bbb.ccc.ddd  netmask 255.255.252.0 media 
>> 1000baseTX"
>>
>> as you see, I also tried to use a fixed speed (both on the server
>> NIC and the switch port) instead of autoconfiguration, but it
>> doesn't help.
>>
>>
>>
>>
>> Kevin Downey wrote:
>> > On 6/28/07, Roberto Nunnari <roberto.nunnari@supsi.ch> wrote:
>> >> Thank you Gilbert.
>> >>
>> >> I think I will give that a try.
>> >>
>> >> But it seams to me that is not the solution.. it may
>> >> be a workaround but not a solution.. It seams to me
>> >> that early_late_divider is in case you mount a FS
>> >> like /usr/local where there are startup scripts executed
>> >> at the late stages of the boot process.. and that's
>> >> not my case.. my case is that the em0 interface, somehow
>> >> gets ready too late.. it doesn't react in a responsive
>> >> way to the up command.. I have other boxes with different
>> >> NICs, mounting that FS without problem and without
>> >> the early_late_divider option.
>> >>
>> >> Can anybody tell why this strange behaviour started
>> >> after upgrading from 5.3-RELEASE to 6.1-RELEASE (that
>> >> was last summer or early fall). May it be related with
>> >> the problems of the em driver? Is there a solution?
>> >>
>> >> is there a way to tell the boot system to wait until
>> >> ifconfig_em0 is be up?
>> >>
>> >> or a way to have em0 responde up before in the boot stage?
>> >>
>> >> Thank you again.
>> >> Best regards.
>> >>
>> >> --
>> >> Robi
>> >>
>> >>
>> >> Lowell Gilbert wrote:
>> >> > Roberto Nunnari <roberto.nunnari@supsi.ch> writes:
>> >> >
>> >> >> ..but on the other box (the em0 one that at the second
>> >> >> retry will succed to mount the NFS FS) is there since
>> >> >> I upgraded it from 5.3-RELEASE to 6.1-RELEASE
>> >> >>
>> >> >> Again.. any hints?
>> >> >
>> >> > I think you're looking for the early_late_divider as described in 
>> the
>> >> > manual for rc.conf(5).
>> >> >
>> >
>> > if you are using dhcp there is an option to run dhcp in the
>> > background, which means the system doesn't stop and wait for dhcp to
>> > configure the address. So if you are using dhcp take a look at the
>> > dhcp variables in the rc.conf manpage
>> >
>>
>>
> 
> try adding an "up" in there.
> ifconfig_em0="up inet aaa.bbb.ccc.ddd  netmask 255.255.252.0 media 
> 1000baseTX"
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4684D786.7080800>