From: Marek Kierdelewicz <marek@koba.pl>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.23.1-smp kernel panic (network-related)
Date: Wed, 7 Nov 2007 19:38:43 +0100 [thread overview]
Message-ID: <20071107193843.1f3fa2f4@catlap> (raw)
In-Reply-To: <20071107095120.237366d2@freepuppy.rosehill>
>What is the test input that causes the crash??
Test box is treated with mirrored traffic that is routed by production
linux router (with non-smp kernel). It's usual traffic generated by
broadband clients. Some of the characteristics:
bandwidth used: ~40/40 Mbit (up/down)
pps: ~15k
number of clients: ~550
dump of packet sizes:
Packet size | Count
1 to 75: 186501
76 to 150: 14145
151 to 225: 3285
226 to 300: 2088
301 to 375: 3632
376 to 450: 2097
451 to 525: 1513
526 to 600: 3069
601 to 675: 20081
676 to 750: 1294
751 to 825: 1189
826 to 900: 885
901 to 975: 2207
976 to 1050: 1333
1051 to 1125: 1192
1201 to 1275: 3036
1276 to 1350: 3709
1351 to 1425: 3453
1426 to 1500+: 185318
protocol breakdown:
most of the traffic is IPv4, some UDP and a little bit of ICMP
Don't know if it's important, but box is connected to switch by a
802.1q trunk. Each of vlan interfaces has egress shaping on it +
dedicated ifb device attached to ingress qdisc and ingress shaping on
ifb device.
Is any additional information needed?
--
Marek Kierdelewicz
Kierownik Działu Systemów Sieciowych, KoBa
Manager of Network Systems Department, KoBa
tel. (85) 7406466; fax. (85) 7406467
e-mail: admin@koba.pl
next prev parent reply other threads:[~2007-11-07 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 17:51 Fw: 2.6.23.1-smp kernel panic (network-related) Stephen Hemminger
2007-11-07 18:38 ` Marek Kierdelewicz [this message]
2007-11-07 18:47 ` Stephen Hemminger
[not found] <20071107175211.1a12c8c9@catlap>
2007-11-07 20:23 ` Andrew Morton
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=20071107193843.1f3fa2f4@catlap \
--to=marek@koba.pl \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).