On Thu, 2009-09-10 at 23:11 +0200, Vincent Lefevre wrote: > Package: linux-image-2.6.30-1-amd64 > Version: 2.6.30-6 > Severity: normal > > During the last boot, a DHCP server has been started even though there > is no Ethernet cable plugged in. You mean DHCP client? [...] > So, it seems that the problem occurs during "ifup -a" (run by > /etc/init.d/networking start). /etc/network/interfaces contains: > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > (it hadn't changed since 2009-06-25). So, it seems that during the > second boot, the system thought that an Ethernet cable was plugged > in. [...] Several drivers had a longstanding bug in reporting of the initial link status, which was mostly benign until a recent change to the networking core. These drivers have mostly been fixed in 2.6.31, and e1000e certainly has. We probably will not update 2.6.30 to fix this. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody.
Attachment:
signature.asc
Description: This is a digitally signed message part