From: Martijn Klingens <mklingens@ism.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange log messages with CBQ?
Date: Thu, 14 Nov 2002 16:36:25 +0000 [thread overview]
Message-ID: <marc-lartc-103729138531445@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103718271922293@msgid-missing>
On Wednesday 13 November 2002 14:55, bert hubert wrote:
> On Wed, Nov 13, 2002 at 12:06:33PM +0100, Martijn Klingens wrote:
> > On Wednesday 13 November 2002 11:17, Martijn Klingens wrote:
> > > Thanks in advance for any help.
> >
> > Oops, forgot to mention the machine config.
> >
> > It's a kernel 2.4.16 box using a stock kernel with only the IMQ patch and
> > the mangle5hooks patch, and the Cyclades HDLC driver. The IMQ device
> > itself is the aggregate of our three 2Mbit HDLC links (hdlc0-2).
>
> Figure out what the initial message is - this just lists the fact that
> messages have been suppressed.
Doh... I should have thought of that myself :-/
Anyway, these messages are *followed* by things like
Nov 14 17:02:10 firewall kernel: NET: 1 messages suppressed.
Nov 14 17:02:10 firewall kernel: protocol 0008 is buggy, dev hdlc1
Nov 14 17:02:10 firewall kernel: protocol 0008 is buggy, dev hdlc2
But there are no messages (besides rather big iptables logs, but what do you
expect on a frontend firewall with a class-C behind it ;-) preceding the
'messages suppressed' warnings.
I have no idea what '1 messages suppressed' means, much less where it comes
from. All I know is that I get it since we started using CBQ.
Martijn
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-11-14 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 10:17 [LARTC] Strange log messages with CBQ? Martijn Klingens
2002-11-13 11:06 ` Martijn Klingens
2002-11-13 13:55 ` bert hubert
2002-11-14 16:36 ` Martijn Klingens [this message]
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-103729138531445@msgid-missing \
--to=mklingens@ism.nl \
--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.