From: Ken Moffat <zarniwhoop@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: Lost network connectivity in 4.0.x
Date: Sun, 24 May 2015 03:43:52 +0100 [thread overview]
Message-ID: <20150524024352.GA15747@milliways> (raw)
Anybody else suffering frm lost network connectivity in 4.0.x
kernels ? A couple of times this week, vim on an nfs-3 mount hung
and I had to reboot. Both of those occasions were on an AMD desktop
with the r8169 driver, running 4.0.3. I thought it might be
specific to that machine. For the last two or three days I've been
using an intel, and about 10 minutes ago it suffered the same problem
while running 4.0.4. Using ping from another term showed that it
had no connectivity to the server on my local network.
This is a bit hard to diagnose - nothing in the logs.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
next reply other threads:[~2015-05-24 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 2:43 Ken Moffat [this message]
2015-05-24 3:29 ` Lost network connectivity in 4.0.x Ken Moffat
2015-05-28 5:53 ` Cong Wang
2015-05-28 14:41 ` Ken Moffat
2015-05-28 16:11 ` Ken Moffat
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=20150524024352.GA15747@milliways \
--to=zarniwhoop@ntlworld.com \
--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