client hangs after eth0 becomes ready

[W Forum W]

On 11/16/2011 08:21 AM, Carsten Aulbert wrote:
> Hi
>
> On Tuesday 15 November 2011 19:54:14 Sylvain Milot wrote:
>> # generated by fai-chboot for host james with IP 172.16.178.144
>> default fai-generated
>>
>> label fai-generated
>> kernel vmlinuz-2.6.38-grml64
>> append initrd=initrd.img-2.6.38-grml64 ethdevice=eth0
>> ip=172.16.178.144:172.16.178.229:172.16.178.1:255.255.255.0:james:eth0:non
>> e root=/dev/nfs boot=live nfsroot=/export/home/fai/squeeze/nfsroot-amd64
>> FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install
>>
> Specifying eth0 will not help as the kernel "arbitrarily" changes the names
> upon reboot. The machine I'm currently struggling with is choosing eth0 for
> the first on-board NIC for ~50-60% of the time (no hard numbers on that one)
> and the first add-on NIC otherwise (currently only these two are connected).
>
> I think it highly depends on timing when the kernel is scanning for available
> devices. As long as you only have NICs handled by a single driver/module I
> think you are fine, but add different cards into the same machine and you will
> run into trouble...
>
> Cheers
>
> Carsten
>
Is there a solution for clients with multiple NICs??

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20111116/d43927ae/attachment.html>