From: Roland Dreier <rdreier@cisco.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@elte.hu>,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is dropped after ~40 seconds
Date: Fri, 18 Dec 2009 00:16:13 -0800 [thread overview]
Message-ID: <adaskb83df6.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <4B2B35B7.6060703@freemail.hu> ("Németh Márton"'s message of "Fri, 18 Dec 2009 08:56:39 +0100")
> Unfortunately reverting the commit 61cbe54d9479ad98283b2dda686deae4c34b2d59 on
> top of 2.6.32 does not solve the problem.
Is there any possibility that one of the steps of the bisection was
wrong? Could you possibly have accidentally marked a "bad" kernel as
"good"?
Addresses like 169.254.123.251 are RFC 3297 zeroconf link-local
addresses. I think network manager will assign one of those if it
thinks the DHCP negotiation failed.
It might be informative to compare the network manager and dhclient log
output (maybe in /var/log/daemon.log?) in the good and bad cases.
- R.
next prev parent reply other threads:[~2009-12-18 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14794-10286@http.bugzilla.kernel.org/>
2009-12-16 23:47 ` [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is dropped after ~40 seconds Andrew Morton
2009-12-17 20:53 ` Németh Márton
2009-12-17 21:20 ` Peter Zijlstra
2009-12-17 21:24 ` Andrew Morton
2009-12-17 21:44 ` Jarek Poplawski
2009-12-18 7:56 ` Németh Márton
2009-12-18 8:16 ` Roland Dreier [this message]
2009-12-18 11:41 ` Jarek Poplawski
2009-12-18 16:17 ` Németh Márton
2009-12-18 16:57 ` Németh Márton
2009-12-18 17:05 ` Németh Márton
2009-12-18 8:22 ` Roland Dreier
2009-12-18 16:49 ` Németh Márton
2009-12-18 20:09 ` Jarek Poplawski
2009-12-19 10:26 ` Németh Márton
2009-12-19 13:48 ` Jarek Poplawski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adaskb83df6.fsf@roland-alpha.cisco.com \
--to=rdreier@cisco.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=efault@gmx.de \
--cc=jarkao2@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=nm127@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).