All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Göran Runfeldt" <goran@wasadata.se>
To: lartc@vger.kernel.org
Subject: SV: [LARTC] 2.4.20 htb3 oops
Date: Tue, 04 Mar 2003 11:49:18 +0000	[thread overview]
Message-ID: <marc-lartc-104677871700498@msgid-missing> (raw)

I have arranged a serial console with logging to a terminal client, so next
time it happens I will have the output from the panic. 

For the record: 
One of the machines crashed again this night at 11.30 p.m. (local time). 
I noticed that the MRTG graph looks a bit odd: 
http://hem.wasadata.net/goran/mrtg.png 
 
The total limit is set to12Mbit, as you probably can see if you check the
ruleset in my first post. Even about 2-4 hours before the crash the graph
shows two network traffic "spikes". The first one tops at about 22Mbps
of outgoing traffic on the interface and the second one tops 28Mbps of
incoming traffic. 
Could this have anything to do with the crash?

Many Thanks,
Göran

----- Original Message ----- 
From: Abraham van der Merwe <abz@frogfoot.net>
To: Göran Runfeldt <goran@wasadata.se>
Cc: <lartc@mailman.ds9a.nl>
Sent: Monday, March 03, 2003 5:29 PM
Subject: Re: [LARTC] 2.4.20 htb3 oops

Hi G?ran!

Unfortunately that is not going to help much since you can't figure out from
the information below where in the code it crashes. Next time, please copy
the entire kernel panic (including stack trace) and run it through ksymoops
or look up the symbols in vmlinux.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-03-04 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 11:49 Göran Runfeldt [this message]
2003-03-10 20:20 ` SV: [LARTC] 2.4.20 htb3 oops Thomas Kirk
2003-03-11  8:52 ` Göran Runfeldt

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=marc-lartc-104677871700498@msgid-missing \
    --to=goran@wasadata.se \
    --cc=lartc@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 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.