From: Alex Samad <alex@samad.com.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: kernel oops when system under network stress
Date: Thu, 16 Oct 2008 18:09:34 +1100 [thread overview]
Message-ID: <20081016070934.GA10150@samad.com.au> (raw)
In-Reply-To: <20081016064142.GA5064@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Thu, Oct 16, 2008 at 02:41:42PM +0800, Herbert Xu wrote:
> On Thu, Oct 16, 2008 at 04:08:10PM +1100, Alex Samad wrote:
> >
> > The thing to note was (for example), when I was doing a nfs transfer, it
> > would not be nfs that would crash, it would be other network based
> > application that would cause the problem, for ex sshd, apache etc
>
> So are you able to reproduce this at will?
just about, within a 5-10 min window
>
> Thanks,
> --
> Visit Openswan at http://www.openswan.org/
> Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
>
--
"I don't think we need to be subliminable about the differences between our views on prescription drugs."
- George W. Bush
09/12/2000
Orlando, FL
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-16 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081016030416.GA5551@samad.com.au>
2008-10-16 4:55 ` kernel oops when system under network stress David Miller
2008-10-16 5:08 ` Alex Samad
2008-10-16 6:41 ` Herbert Xu
2008-10-16 7:09 ` Alex Samad [this message]
2008-10-16 7:15 ` Alex Samad
2008-10-16 9:10 ` Herbert Xu
2008-10-24 2:09 ` Alex Samad
2008-10-16 5:41 ` Herbert Xu
2008-10-16 5:48 ` Alex Samad
2008-10-16 7:07 ` Herbert Xu
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=20081016070934.GA10150@samad.com.au \
--to=alex@samad.com.au \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-net@vger.kernel.org \
--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).