From: Richard Kennedy <richard@rsk.demon.co.uk>
To: netdev@vger.kernel.org
Subject: v3.0-rc* intermittent network failure: how to debug?
Date: Thu, 21 Jul 2011 14:49:54 +0100 [thread overview]
Message-ID: <1311256194.2980.18.camel@castor.rsk> (raw)
I keep seeing a total network failure on v3.0.0-rc* , it is highly
intermittent, anything from 1 hour to 12+, and I don't have a reliable
test case.
When it fails I lose all network comms, but there are no errors in the
system log, no hung tasks reported, nothing. But after it fails the
machine hangs during shutdown, it just never turns off. So I guess
something is getting stuck but I can't find it.
Can you suggest how to find out what going on?
Or how collect more information as to what's failing?
I'm going to add a serial console and see if that helps.
this is on a x86_64, via_velocity currently running 3.0.0-rc7 latest.
all suggestions gratefully received
regards
Richard
next reply other threads:[~2011-07-21 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 13:49 Richard Kennedy [this message]
2011-07-21 14:32 ` v3.0-rc* intermittent network failure: how to debug? Francois Romieu
2011-07-21 15:18 ` Richard Kennedy
2011-07-25 12:01 ` v3.0-rc* intermittent network failure: Test case found! Richard Kennedy
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=1311256194.2980.18.camel@castor.rsk \
--to=richard@rsk.demon.co.uk \
--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).