From: Bob Felderman <feldy@myri.com>
To: linux-kernel@vger.kernel.org
Subject: re: possible bug x86 2.4.2 SMP in IP receive stack
Date: Fri, 23 Feb 2001 15:03:01 -0800 [thread overview]
Message-ID: <200102232303.PAA20963@frisbee.myri.com> (raw)
=> From feldy Fri Feb 23 14:13:08 2001
=>
=> Feb 23 12:42:30 rcc2 kernel: Warning: kfree_skb passed an skb still on a list (from c01f58dc).
=>
=> I'm going to pop out one processor on the receiver
=> and see if that makes the problem go away.
Using a single processor on the receive side makes the problem go away.
I see no problems on the receiver with one cpu removed.
rcc2 29% netstat -i myri0
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 37857 0 0 0 36404 0 0 0 BRU
lo 16192 0 46 0 0 0 46 0 0 0 LRU
myri0 9000 0 20564644 0 0 0 312 0 0 0 BRU
next reply other threads:[~2001-02-23 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 23:03 Bob Felderman [this message]
[not found] <200102232259.OAA20943@frisbee.myri.com>
2001-02-27 19:41 ` possible bug x86 2.4.2 SMP in IP receive stack kuznet
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 22:13 Bob Felderman
2001-02-26 5:10 ` David S. Miller
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=200102232303.PAA20963@frisbee.myri.com \
--to=feldy@myri.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