Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-35squeeze2

On an NFS root boot with this version, the boot fails after reporting
"IP-Config: no response after __ seconds - giving up" once "__" reaches
100. It then outputs "/inet:...can't open '/tmp/net-*.conf'" and
"Kernel panic" etc. (Sorry, these message are from memory, since I'm
sending this from the machine that fails, and no logs get written.)

The old release still boots fine (though I'm using the newer modules for
now):
----------
$ uname -rvm
2.6.32-5-amd64 #1 SMP Wed May 18 23:13:22 UTC 2011 x86_64
----------

The DHCP server is dhcp3-server 3.1.1-6+lenny6. When the newer kernel
boots, it logs the DHCPDISCOVER/OFFER, but no DHCPREQUEST/ACK. There is
iptables firewalling on the DHCP server, but no blocked packets are
reported. Otherwise the server and client are directly connected.

Client boot options are:
----------
append root=/dev/nfs nfsroot=__.__.__.__:/___ ip=dhcp rw
----------



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110923234342.GA816@64-142-29-25.dsl.static.sonic.net">http://lists.debian.org/20110923234342.GA816@64-142-29-25.dsl.static.sonic.net

Hi all,

Bug confirmed here. vmlinuz/initramfs from linux-image-2.6.32-5-686 fails
to get an IP address in ipconfig during network boot. 2.6.38-1-486 (from
the GParted live CD) doesn't have this problem.


I can see the DHCPACK packets being sent from the DHCP server to the
client, but apparently it doesn't receive or understand them. It's a bit
early in the boot process to run a packet sniffer on the client. Also I
don't have physical access to this machine (it's 3000 miles away) and
every attempt ends in a hang after "/inet:...can't open
'/tmp/net-*.conf'", requiring me to request a manual reboot.


Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 760887
The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES

Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: alpine.DEB.2.00.1110191716270.4468@lap-x201">http://lists.debian.org/alpine.DEB.2.00.1110191716270.4468@lap-x201

This is still a problem with version 2.6.32-41.

Comparing the packets sent between the DHCP client and server, I notice
that the latest kernel sets the DHCP 'secs' field. The DHCP server,
which should return 0 in 'secs', returns the client's 'secs' value
instead in its DHCPOFFER. Perhaps the client is discarding the response
because of this?



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120129052343.GA769@64-142-29-25.dsl.static.sonic.net">http://lists.debian.org/20120129052343.GA769@64-142-29-25.dsl.static.sonic.net