From: "Németh Márton" <nm127@freemail.hu>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Linux PM List <linux-pm@lists.linux-foundation.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
DRI <dri-devel@lists.sourceforge.net>
Subject: Re: 2.6.33-rc2: Reported regressions 2.6.31 -> 2.6.32
Date: Tue, 29 Dec 2009 21:55:13 +0100 [thread overview]
Message-ID: <4B3A6CB1.3030305@freemail.hu> (raw)
In-Reply-To: <4B3A5BC2.10207@gmail.com>
Jarek Poplawski wrote:
> Rafael J. Wysocki wrote, On 12/29/2009 04:26 PM:
>
> ...
>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14794
>> Subject : IP address assigned by DHCP is dropped after ~40 seconds
>> Submitter : Márton Németh <nm127@freemail.hu>
>> Date : 2009-12-13 08:59 (17 days old)
>>
>
>
> IMHO this bug might be considered as fixed by updating a userspace tool
> (KNetworkManager) - unless somebody wants to seek for the exact reason...
For me (I am the reporter) the problem was solved by upgrading a userspace
tool, so I think the bug filed against the kernel can be closed marking
that this was not really a kernel bug.
Regards,
Márton Németh
next prev parent reply other threads:[~2009-12-29 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 15:26 2.6.33-rc2: Reported regressions 2.6.31 -> 2.6.32 Rafael J. Wysocki
2009-12-29 15:47 ` Gertjan van Wingerde
2009-12-29 22:15 ` Rafael J. Wysocki
2009-12-29 19:42 ` Jarek Poplawski
2009-12-29 20:55 ` Németh Márton [this message]
2009-12-29 22:00 ` Jarek Poplawski
2009-12-29 21:49 ` Rafael J. Wysocki
2009-12-30 16:58 ` Larry Finger
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=4B3A6CB1.3030305@freemail.hu \
--to=nm127@freemail.hu \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jarkao2@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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).