All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: anand@eis.iisc.ernet.in (SVR Anand)
Cc: davem@redhat.com (David S. Miller), netdev@oss.sgi.com
Subject: Re: Bridging woes after 3 days
Date: Mon, 1 Dec 2003 11:33:12 -0800	[thread overview]
Message-ID: <20031201113312.2ce6ec0f.shemminger@osdl.org> (raw)
In-Reply-To: <200311290944.PAA27304@eis.iisc.ernet.in>

On Sat, 29 Nov 2003 15:14:08 +0530 (GMT+05:30)
anand@eis.iisc.ernet.in (SVR Anand) wrote:

> 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.

Can you hook a serial console to catch the precise wording?

Also if you save copies of /proc/slabinfo on a regular interval (like per hour),
then it is possible to see if there is a memory leak.

  reply	other threads:[~2003-12-01 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 15:27 2.6.0-test9 : bridge freezes SVR Anand
2003-11-22 16:19 ` Gene Heskett
2003-11-22 16:20 ` Linus Torvalds
2003-11-23 23:26   ` David S. Miller
2003-11-24  0:02     ` Markus Hästbacka
2003-11-25 17:21     ` 2.6.0-test9-bk25 : bridge works fine SVR Anand
2003-11-29  9:44     ` Bridging woes after 3 days SVR Anand
2003-12-01 19:33       ` Stephen Hemminger [this message]
2003-11-22 19:18 ` 2.6.0-test9 : bridge freezes Markus Hästbacka
2003-11-24 19:09 ` [Bridge] " Stephen Hemminger
2003-11-24 19:09   ` Stephen Hemminger
2003-11-25  6:39   ` [Bridge] " SVR Anand
2003-11-25  6:39     ` SVR Anand

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=20031201113312.2ce6ec0f.shemminger@osdl.org \
    --to=shemminger@osdl.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.