Re: em0 net interface Link state changed to UP too late at boot time
Hi Kevin. Ok. I'll try that. Thank you. -- Robi Kevin Downey wrote: On 6/28/07, Roberto Nunnari [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
net interface Link state changed to UP too late at boot time
Hello list. I have a couple of FreeBSD boxes here that when booting the network interface Link state is changed to UP too late. .. as the systems mount at boot time a NFS FS, it hangs there and after that I get the following kernel message: xl0: Link state changed to UP or (depending on the box booting) em0: Link state changed to UP Any hints? Is there a way to tune it by some sysctl? Thanks in advance and best regards -- Robi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: net interface Link state changed to UP too late at boot time
Roberto Nunnari [EMAIL PROTECTED] 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). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0 net interface Link state changed to UP too late at boot time
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 [EMAIL PROTECTED] 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). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0 net interface Link state changed to UP too late at boot time
On 6/28/07, Roberto Nunnari [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 -- i'll unhook my oily pink mini-kimono, you kill him in honolulu -- www.thelastcitadel.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0 net interface Link state changed to UP too late at boot time
On 6/28/07, Roberto Nunnari [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 -- i'll unhook my oily pink mini-kimono, you kill him in honolulu -- www.thelastcitadel.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
net interface Link state changed to UP too late at boot time
Hello list. Sorry to post again.. I just realized I was not subscribed (now I am) and also forgot to tell the OS version: # uname -rms FreeBSD 6.1-RELEASE-p15 i386 I have a couple of FreeBSD boxes here that when booting, the network interface Link state is changed to UP too late. .. as the systems mounts at boot time a NFS FS, it hangs there and after that I get the following kernel message: xl0: Link state changed to UP or (depending on the box booting) em0: Link state changed to UP on one box, after a timeout, at the next retry, the FS will be mounted. on the second box, even after the timeout, the FS will not be mounted as the interface will not be configured at all. I'll have to go through ifconfig manually and then every thing will be ok. Any hints? Is there a way to tune it by some sysctl? Thanks in advance and best regards -- Robi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: net interface Link state changed to UP too late at boot time
On one of the boxes the problem is solved.. it was a mistake of mine.. ..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? Roberto Nunnari wrote: Hello list. Sorry to post again.. I just realized I was not subscribed (now I am) and also forgot to tell the OS version: # uname -rms FreeBSD 6.1-RELEASE-p15 i386 I have a couple of FreeBSD boxes here that when booting, the network interface Link state is changed to UP too late. .. as the systems mounts at boot time a NFS FS, it hangs there and after that I get the following kernel message: xl0: Link state changed to UP or (depending on the box booting) em0: Link state changed to UP on one box, after a timeout, at the next retry, the FS will be mounted. on the second box, even after the timeout, the FS will not be mounted as the interface will not be configured at all. I'll have to go through ifconfig manually and then every thing will be ok. Any hints? Is there a way to tune it by some sysctl? Thanks in advance and best regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
