From: anand@eis.iisc.ernet.in (SVR Anand)
To: davem@redhat.com (David S. Miller)
Cc: netdev@oss.sgi.com
Subject: Bridging woes after 3 days
Date: Sat, 29 Nov 2003 15:14:08 +0530 (GMT+05:30) [thread overview]
Message-ID: <200311290944.PAA27304@eis.iisc.ernet.in> (raw)
In-Reply-To: <20031123152601.67646dc1.davem@redhat.com> from "David S. Miller" at Nov 23, 2003 03:26:01 PM
Hi,
After a continous run for 3 days the bridge came down crashing with the
following kernel panic screen dump. The kernel is 2.6.0-test9-bk25 with
kernel preemption disabled.
The following call stack is what I have seen on the console. The ethernet
cards are RTL8139. Please let me know if you want more information or finer
debugging method, I will pass it on when the bridge fails the next time.
When it worked it really worked.
Anand
----------------------------------------------------------------------------
nf_hook_slow
br_nf_pre_routing_finish
br_nf_pre_routing
br_nf_pre_finish
nf_iterate
br_handle_frame_finish
nf_hook_slow
br_handle_frame_finish
br_handle_frame
br_handle_frame_finish
netif_recieve_skb
process_backlog
net_rx_action
do_selfirq
do_IRQ
common_interrupt
default_idle
default_idle
cpu_idle
printk
code: 8b 40 18 85 c0 75 7f 85 ff 74 44 89 7b 70 0f ba 6b 40 00 89
<0> kernel panic : Fatal exception in interrupt
In interrupt handles - not syncing
----------------------------------------------------------------------------
next prev parent reply other threads:[~2003-11-29 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200311221527.UAA29684@eis.iisc.ernet.in>
2003-11-22 16:20 ` 2.6.0-test9 : bridge freezes Linus Torvalds
2003-11-23 23:26 ` David S. Miller
2003-11-25 17:21 ` 2.6.0-test9-bk25 : bridge works fine SVR Anand
2003-11-29 9:44 ` SVR Anand [this message]
2003-12-01 19:33 ` Bridging woes after 3 days Stephen Hemminger
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=200311290944.PAA27304@eis.iisc.ernet.in \
--to=anand@eis.iisc.ernet.in \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).