From: Jarek Poplawski <jarkao2@gmail.com>
To: Tuomas Jormola <tj@solitudo.net>
Cc: netdev@vger.kernel.org
Subject: Re: PROBLEM: A set of networking related oopses
Date: Sat, 08 Mar 2008 10:53:05 +0100 [thread overview]
Message-ID: <47D26201.2060201@gmail.com> (raw)
In-Reply-To: <D04F01C2-03F0-4FBC-933D-62899456BEE9@solitudo.net>
Tuomas Jormola wrote, On 03/06/2008 08:05 PM:
> Hello,
Hi,
> [1.] One line summary of the problem:
> My gateway machine is suffering from kernel oopses that don't kill the
> machine, but do occur every now and then
Do you have irq balancing enabled for your eths (are eth interrupts shown
for more than one cpu in /proc/interrupts)? If so, try to disable this.
This link could be helpful:
http://marc.info/?l=linux-netdev&m=120349568512423&w=2
Regards,
Jarek P.
next prev parent reply other threads:[~2008-03-08 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:05 PROBLEM: A set of networking related oopses Tuomas Jormola
2008-03-08 9:53 ` Jarek Poplawski [this message]
2008-03-08 16:13 ` Tuomas Jormola
2008-03-08 17:57 ` Jarek Poplawski
2008-03-09 16:58 ` Tuomas Jormola
2008-03-09 17:31 ` Jarek Poplawski
2008-04-24 14:25 ` Tuomas Jormola
2008-04-24 20:01 ` Jarek Poplawski
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=47D26201.2060201@gmail.com \
--to=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@solitudo.net \
/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).