From: Marc MERLIN <marc@merlins.org>
To: David Miller <davem@davemloft.net>,
James Courtier-Dutton <james.dutton@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.2.8/amd64 full interrupt hangs and deadlocks under big network copies (page allocation failure)
Date: Thu, 29 Mar 2012 07:05:26 -0700 [thread overview]
Message-ID: <20120329140526.GG24933@merlins.org> (raw)
In-Reply-To: <CAAMvbhHGeZMrTcc6DiOAtk7Vg3Qu1KE7bs8D3E3N-sCtRPzmwg@mail.gmail.com> <20120329.024910.1984119977666436533.davem@davemloft.net>
On Thu, Mar 29, 2012 at 02:49:10AM -0400, David Miller wrote:
> From: Marc MERLIN <marc@merlins.org>
> Date: Wed, 28 Mar 2012 22:31:11 -0700
>
> > This is a pretty bad failure. Someone please tell me there is
> > something I can do to work around the problem, and get the
> > underlying problem fixed.
>
> First step would be to report this to the proper mailing list,
> most networking and wireless developers do not read linux-kernel.
>
> I'd start with linux-wireless@vger.kernel.org and netdev@vger.kernel.org
On Thu, Mar 29, 2012 at 09:36:02AM +0100, James Courtier-Dutton wrote:
> That looks like a network card problem. Probably a hardware bug. Try a
> different network card if you can.
Thanks both for the answer. I don't think it's a network hardware
problem since it happens with both e1000e wired and iwlwifi wireless.
I wasn't quite sure if it was a memory allocation problem that caused the
hangs, but you're right that it's most likely a networking issue regardless
of the fact that it happens on both wired and wireless.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
prev parent reply other threads:[~2012-03-29 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 18:32 3.2.8/amd64 full interrupt hangs and deadlocks under big network copies (page allocation failure) Marc MERLIN
2012-03-29 5:31 ` Marc MERLIN
2012-03-29 6:49 ` David Miller
2012-03-29 14:05 ` Marc MERLIN [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=20120329140526.GG24933@merlins.org \
--to=marc@merlins.org \
--cc=davem@davemloft.net \
--cc=james.dutton@gmail.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