Bug#583139: linux-2.6: no DHCP offers on r8169
 

On Tue, May 25, 2010 at 07:43:00PM +0200, Alexandre Rossi wrote:
> Package: linux-2.6
> Version: 2.6.26-22lenny1
> Severity: important
>
> Hi,
>
> I get no DHCP offers on the r8169 device since the upgrade to 2.6.26-22lenny1.
>
> Reverting to 2.6.26-22 does not fix the problem.
>
> Reverting to 2.6.26-21lenny4 *does* fix the problem.
>
> Please contact me for more info.

Alex,
Thanks for the report. I don't see anything in -22 that looks like it
would've affected your setup, but in -22lenny1 there is a security fix
for the r8169 driver. Would you mind retesting -22 just to be sure?

Also, please supply the output of 'dmesg' on your system after the
dhcp fails on -22lenny1. It might be useful to see the output on
-21lenny4 as well for comparison.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100525195948.GA8078@lackof.org">http://lists.debian.org/20100525195948.GA8078@lackof.org

Bug#583139: linux-2.6: no DHCP offers on r8169
 

On Tue, 2010-05-25 at 13:59 -0600, dann frazier wrote:
> On Tue, May 25, 2010 at 07:43:00PM +0200, Alexandre Rossi wrote:
> > Package: linux-2.6
> > Version: 2.6.26-22lenny1
> > Severity: important
> >
> > Hi,
> >
> > I get no DHCP offers on the r8169 device since the upgrade to 2.6.26-22lenny1.
> >
> > Reverting to 2.6.26-22 does not fix the problem.
> >
> > Reverting to 2.6.26-21lenny4 *does* fix the problem.
> >
> > Please contact me for more info.
>
> Alex,
> Thanks for the report. I don't see anything in -22 that looks like it
> would've affected your setup, but in -22lenny1 there is a security fix
> for the r8169 driver. Would you mind retesting -22 just to be sure?
>
> Also, please supply the output of 'dmesg' on your system after the
> dhcp fails on -22lenny1. It might be useful to see the output on
> -21lenny4 as well for comparison.

I suspect that this is bug #573007, which sometimes causes the MAC
address to be set incorrectly. It doesn't always trigger, and the
differing behaviour between kernel versions would just be a matter of
chance (or dependent on whether you use a cold or warm boot). There is
a pending patch for lenny which should fix it.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Bug#583139: linux-2.6: no DHCP offers on r8169
 

[Please keep the bug # in the CC]

On Thu, May 27, 2010 at 11:08:09AM +0200, Alexandre Rossi wrote:
> Hi,
>
> > Thanks for the report. I don't see anything in -22 that looks like it
> > would've affected your setup, but in -22lenny1 there is a security fix
> > for the r8169 driver. Would you mind retesting -22 just to be sure?
>
> Yep me neither, that's why I tested multiple times...
>
> But just to be sure, I just tested another time, and my first results
> are not consistent with what I found again.
>
> I've been running for about a day with 2.6.26-22 and I could not reproduce.
>
> I'll try again to upgrade to -22lenny1 tonight.

Ok, sounds good.

> > Also, please supply the output of 'dmesg' on your system after the
> > dhcp fails on -22lenny1. It might be useful to see the output on
> > -21lenny4 as well for comparison.
>
> Not much interesting in those. In the following, r8169=eth0 and eth1
> is another interface running with 8139too.
>
> For 2.6.26-22lenny1 :
> --
> [ 0.000000] Linux version 2.6.26-2-openvz-amd64 (Debian 2.6.26-22lenny1) (dan
> nf@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SM
> P Wed May 12 18:14:56 UTC 2010
> [...]
> [ 23.631312] r8169: eth0: link up
> [ 86.387430] eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
> [ 86.863726] NET: Registered protocol family 10
> --
>
> For 2.6.26-22 :
> --
> [ 0.000000] Linux version 2.6.26-2-openvz-amd64 (Debian 2.6.26-22) (dannf@deb
> ian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Tue
> Mar 9 17:24:55 UTC 2010
> [...]
> [ 22.893548] r8169: eth0: link up
> [ 71.346600] r8169: eth0: link down
> [ 89.546732] eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
> --
>
> For 2.6.26-21lenny4 (eth1, the next inerface, is up earlier because
> DHCP on eth0=r8169 succeeds) :
> --
> [ 0.000000] Linux version 2.6.26-2-openvz-amd64 (Debian
> 2.6.26-21lenny4) (dannf@debian.org) (gcc version 4.1.3 20080704
> (prerelease) (Debian 4.1.2-25)) #1 SMP Tue Mar 9 23:10:10 UTC 2010
> [...]
> [ 32.418312] r8169: eth0: link up
> [ 37.406798] eth1: link up, 100Mbps, full-duplex, lpa 0x41E1



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100527142100.GB25996@lackof.org">http://lists.debian.org/20100527142100.GB25996@lackof.org

Bug#583139: linux-2.6: no DHCP offers on r8169
 

Hi,

>> But just to be sure, I just tested another time, and my first results
>> are not consistent with what I found again.
>>
>> I've been running for about a day with 2.6.26-22 and I could not reproduce.
>>
>> I'll try again to upgrade to -22lenny1 tonight.

I cannot reproduce anymore with -22lenny1.

I do not understand since I had checked with another computer on the
same link to rule out a failure from my ISP.

I guess if I cannot reproduce through the WE, this can be closed.

Alex



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTikc4vZkcNtrSOr0EMsTQ4gd80pCWiBRF3si2vwF@mail .gmail.com">http://lists.debian.org/AANLkTikc4vZkcNtrSOr0EMsTQ4gd80pCWiBRF3si2vwF@mail .gmail.com

Bug#583139: linux-2.6: no DHCP offers on r8169
 

> I cannot reproduce anymore with -22lenny1.
>
> I do not understand since I had checked with another computer on the
> same link to rule out a failure from my ISP.
>
> I guess if I cannot reproduce through the WE, this can be closed.

Cannot reproduce anymore, playing with DHCP, and -22lenny1.

Sorry for the noise.

Alex



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTinOlATjWLqhS7s2NlGgI310YuDGRDc6cqjhVW1B@mail .gmail.com">http://lists.debian.org/AANLkTinOlATjWLqhS7s2NlGgI310YuDGRDc6cqjhVW1B@mail .gmail.com

Bug#583139: linux-2.6: no DHCP offers on r8169
 

reopen 583139
thanks

Happenned again today when I had to reboot. Reverting to -22 fixed the
problem, and I guess it triggers with the DHCP leases. Do not know how
to go further on investigating this issue. I could not reproduce
because I wasn't clearing the DHCP state.

Interestingly, /var/log/daemon.log has been filling with lines like
the following (I hadn't notitced that) :
Jun 11 09:32:58 ripley0 dhclient: DHCPREQUEST on eth0 to 1.2.3.4 port 67
while running with -22lenny1, every 20 seconds or so.

Bug triggering timeline :
May 31 19:20:22 ripley0 : boot
May 31 19:23:52 ripley0 dhclient: Listening on LPF/eth0/00:ff:ff:ff:ff:ff
May 31 19:23:52 ripley0 dhclient: Sending on LPF/eth0/00:ff:ff:ff:ff:ff
May 31 19:23:52 ripley0 dhclient: Sending on Socket/fallback
May 31 19:23:55 ripley0 dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 3
May 31 19:23:55 ripley0 dhclient: DHCPOFFER from 1.2.3.4
May 31 19:23:55 ripley0 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 31 19:23:55 ripley0 dhclient: DHCPACK from 1.2.3.4
May 31 19:23:56 ripley0 dhclient: bound to 1.2.3.4 -- renewal in 255769 seconds.
[3 days pass, exactly the renewal time]
Jun 3 18:26:45 ripley0 dhclient: DHCPREQUEST on eth0 to 1.2.3.4 port 67
Jun 3 18:26:52 ripley0 dhclient: DHCPREQUEST on eth0 to 1.2.3.4 port 67
Jun 3 18:27:02 ripley0 dhclient: DHCPREQUEST on eth0 to 1.2.3.4 port 67
Jun 3 18:27:15 ripley0 dhclient: DHCPREQUEST on eth0 to 1.2.3.4 port 67
[many more like those, every 20 seconds]

I must reboot under -22 to renew my IP address.

Alex



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTil6SbTRsmhDsD0rqcg6WGEG3-HpbYfNszZb2j4C@mail.gmail.com">http://lists.debian.org/AANLkTil6SbTRsmhDsD0rqcg6WGEG3-HpbYfNszZb2j4C@mail.gmail.com

Bug#583139: linux-2.6: no DHCP offers on r8169
 

On Fri, 2010-06-11 at 15:17 +0200, Alexandre Rossi wrote:
> reopen 583139
> thanks
>
> Happenned again today when I had to reboot. Reverting to -22 fixed the
> problem, and I guess it triggers with the DHCP leases. Do not know how
> to go further on investigating this issue. I could not reproduce
> because I wasn't clearing the DHCP state.

Is the net device's MAC address set correctly when this happens, or does
it begin with 00:00:00:00?

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Bug#583139: linux-2.6: no DHCP offers on r8169
 

> Is the net device's MAC address set correctly when this happens, or does
> it begin with 00:00:00:00?

The device's MAC address, as shown by /sbin/ifconfig, is set
correctly, while I get DHCP troubles.

I'll wait the renewal time to see if that changes.

Alex



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTinfas3zwpVcE85f32k8fKsiirfuEc-K9xzHrBzv@mail.gmail.com">http://lists.debian.org/AANLkTinfas3zwpVcE85f32k8fKsiirfuEc-K9xzHrBzv@mail.gmail.com

Bug#583139: linux-2.6: no DHCP offers on r8169
 

On Mon, 2010-06-14 at 07:49 +0200, Alexandre Rossi wrote:
> > Is the net device's MAC address set correctly when this happens, or does
> > it begin with 00:00:00:00?
>
> The device's MAC address, as shown by /sbin/ifconfig, is set
> correctly, while I get DHCP troubles.
>
> I'll wait the renewal time to see if that changes.

Please report the net device statistics (from '/proc/net/dev') and the
PCI ID for this device (run 'lspci -nn -d 10ec:').

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Bug#583139: linux-2.6: no DHCP offers on r8169
 

> Please report the net device statistics (from '/proc/net/dev') and the
> PCI ID for this device (run 'lspci -nn -d 10ec:').

Attached are the current /proc/net/dev stats for the device, I'll
resend those when the bug triggers (I assume you want to see if there
are drop packets).

$ lspci -nn -d 10ec:
01:02.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
01:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8110SC/8169SC Gigabit Ethernet [10ec:8167] (rev 10)

(eth0, which triggers the bug, is the second one)