From: Alexander Huemer <alexander.huemer@sbg.ac.at>
To: linux-kernel@vger.kernel.org
Subject: kernel panics with net_rx_action on kernels >2.6.26
Date: Sat, 13 Dec 2008 19:43:55 +0100 [thread overview]
Message-ID: <4944026B.40301@sbg.ac.at> (raw)
hi,
one of my machines (x86) crashes under heavy network load with kernels
>2.6.26, i tried quite everything possible between 2.6.27 and 2.6.28-rc8.
lspci -vv: http://xx.vu/~ahuemer/lspci_vv.txt
of the quad nic 2 ports are used, the machine is acting as a iptables
firewall/router.
kernel config (2.6.26) http://xx.vu/~ahuemer/config
screenshot of the panic:
http://xx.vu/~ahuemer/kernel_panic_net_rx_action.jpg
as i do not have any problems with kernels <=2.6.26, i doubt that this
is a hardware problem.
in case of the panic, nothing is written to the system log.
any hints welcome.
please CC me on replies, i am not subscribed to the mailing list.
thanks in advance.
--
alex
next reply other threads:[~2008-12-13 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 18:43 Alexander Huemer [this message]
2008-12-20 23:00 ` kernel panics with net_rx_action on kernels >2.6.26 Rafael J. Wysocki
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=4944026B.40301@sbg.ac.at \
--to=alexander.huemer@sbg.ac.at \
--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