Hi,
For the record, after more investigation, this appears not to be
related to the kernel at all (sorry) but ot a misbehaving DHCP server
that only answers on broadcast. My ISP must have changed its config.
$ cat /var/log/daemon.log.1 /var/log/daemon.log 2>/dev/null | grep
dhclient | cut -d':' -
On Tue, 2010-06-15 at 08:07 +0200, Alexandre Rossi wrote:
> > 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
> 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 1
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
> 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 debia
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
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/dae
> 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.
So
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 -22le
[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
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-22len
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
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
-- S
13 matches
Mail list logo
