From: Steve Lazaridis <slaz@fortresstech.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: netdev@vger.kernel.org, bridge@osdl.org
Subject: Re: ip_sabotage_out crash...
Date: Tue, 27 Dec 2005 10:42:36 -0500 [thread overview]
Message-ID: <43B160EC.1010705@fortresstech.com> (raw)
In-Reply-To: <20051227153502.GA6294@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Tue, Dec 27, 2005 at 10:24:06AM -0500, Steve Lazaridis wrote:
>
>
>>Hi,
>
>
> Hello,
>
>
>
>>I'm running on a MIPSbe(AMD au1550) CPU and I'm getting kernel crashes
>>when pumping a lot of traffic through two bridges using iperf.
>
>
> Can you reproduce it without the binary-only kernel modules loaded?
I'm unable todo so, I only have 1 etherenet interface and 2 wifi
intefaces, both of which are atheros cards.
slaz
>
>
> --L
prev parent reply other threads:[~2005-12-27 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 15:24 ip_sabotage_out crash Steve Lazaridis
2005-12-27 15:35 ` Lennert Buytenhek
2005-12-27 15:42 ` Steve Lazaridis [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=43B160EC.1010705@fortresstech.com \
--to=slaz@fortresstech.com \
--cc=bridge@osdl.org \
--cc=buytenh@wantstofly.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).