From: Ondrej Zary <linux@rainbow-software.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network died completely in 2.6.29
Date: Sat, 28 Mar 2009 20:29:35 +0100 [thread overview]
Message-ID: <200903282029.37128.linux@rainbow-software.org> (raw)
In-Reply-To: <20090327.155346.98210435.davem@davemloft.net>
On Friday 27 March 2009 23:53:46 David Miller wrote:
> From: Ondrej Zary <linux@rainbow-software.org>
> Date: Fri, 27 Mar 2009 23:51:36 +0100
>
> > upgraded to 2.6.29 today. It appeared to work fine for a couple of hours.
> > But suddenly the network stopped. I wasn't even able to ping my local IP.
> > Even pinging 127.0.0.1 did not work. There were no errors in dmesg and
> > the system appeared to work fine otherwise. Had to reboot (into 2.6.28).
> >
> > Never seen this before. Anyone with the same problem?
>
> It's a known problem, the following fix will be submitted
> to 2.6.29.1 over the weekend.
Thanks, it seems to work now.
--
Ondrej Zary
prev parent reply other threads:[~2009-03-28 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 22:51 Network died completely in 2.6.29 Ondrej Zary
2009-03-27 22:53 ` David Miller
2009-03-28 19:29 ` Ondrej Zary [this message]
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=200903282029.37128.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@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