From: "Németh Márton" <nm127@freemail.hu>
To: Jarek Poplawski <jarkao2@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: 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 08:56:39 +0100 [thread overview]
Message-ID: <4B2B35B7.6060703@freemail.hu> (raw)
In-Reply-To: <4B2AA64C.50709@gmail.com>
Hi,
Jarek Poplawski wrote:
> Andrew Morton wrote, On 12/17/2009 10:24 PM:
>
>> On Thu, 17 Dec 2009 21:53:20 +0100
>> Németh Márton <nm127@freemail.hu> wrote:
>>
>>> Hi,
>>>
>>> I bisected the problem, see http://bugzilla.kernel.org/show_bug.cgi?id=14794
>>> for details. Any idea what is the relation between this problem and the found
>>> patch?
>>>
>> : 61cbe54d9479ad98283b2dda686deae4c34b2d59 is the first bad commit
>> : commit 61cbe54d9479ad98283b2dda686deae4c34b2d59
>> : Author: Mike Galbraith <efault@gmx.de>
>> : Date: Wed Sep 9 15:41:37 2009 +0200
>> :
>> : sched: Keep kthreads at default priority
>>
>> Strange. Might be a timing thing bu a) I doubt if any kernel threads
>> are involved in maintaining a DHCP lease and b) even if they were, such
>> a race wouldn't be this repeatable.
>>
>
> "Removes kthread/workqueue priority boost[...]" - if there could be
> workqueues involved - maybe something with link-watch?
Unfortunately reverting the commit 61cbe54d9479ad98283b2dda686deae4c34b2d59 on
top of 2.6.32 does not solve the problem.
I use KDE, and the KNetworkManager icon is visible on the task bar. When
I unplug the network cable the "disconnected" icon appears. After I plug the
network cable again, a rotating wheel appears. Here comes the difference: *when*
the rotating wheel changes to "connected" state. One case, when the IP address
is kept the "connected" icon appears right after the IP address assigned by
DHCP appears in the ifconfig output. In the wrong case this rotating wheel is
still there for about 60 seconds while the the assigned IP address is dropped
and an IP address like 169.254.123.251 is assigned.
There is a workaround, too. If the IP address 169.254.123.251 was assigned and
I execute "dhclient eth0" as root, an IP address will be assigned by DHCP and
this address is not dropped anymore until I again unplug and replug the network
cable.
My driver for the network card is 8139too. My network card is:
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: CLEVO/KAPOK Computer Device 4702
Flags: bus master, medium devsel, latency 64, IRQ 19
I/O ports at 1000 [size=256]
Memory at d0004000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Kernel driver in use: 8139too
Kernel modules: 8139too
Regars,
Márton Németh
next prev parent reply other threads:[~2009-12-18 8:03 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 [this message]
2009-12-18 8:16 ` Roland Dreier
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=4B2B35B7.6060703@freemail.hu \
--to=nm127@freemail.hu \
--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 \
/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).