From: Augustin Vidovic <vido@ldh.org>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
Cc: Alan Cox <alan@redhat.com>, Andrey Savochkin <saw@saw.sw.com.sg>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eepro100.c, kernel 2.4.1
Date: Thu, 8 Feb 2001 20:44:15 +0900 [thread overview]
Message-ID: <20010208204415.A19308@ldh.org> (raw)
In-Reply-To: <20010208201539.A19229@ldh.org> <200102081126.f18BQpS18016@moisil.dev.hydraweb.com>
In-Reply-To: <200102081126.f18BQpS18016@moisil.dev.hydraweb.com>; from ionut@moisil.cs.columbia.edu on Thu, Feb 08, 2001 at 03:26:51AM -0800
On Thu, Feb 08, 2001 at 03:26:51AM -0800, Ion Badulescu wrote:
> syslogd does not suppress messages, it suppresses *identical* messages.
> So what was the *first* message logged by syslogd, the one followed by
> "last message repeated XXX times"?
It's not "last message repeatead XXX times", it's :
...
Jan 30 00:01:18 XXX kernel: NET: 8298 messages suppressed.
Jan 30 00:01:24 XXX kernel: NET: 2929 messages suppressed.
Jan 30 00:01:38 XXX kernel: NET: 1225 messages suppressed.
Jan 30 00:01:43 XXX kernel: NET: 4397 messages suppressed.
Jan 30 00:01:48 XXX kernel: NET: 2342 messages suppressed.
...
(ad nauseam)
This suppression of thousands of lines was described as a DOS-protection
in the docs I read.
> Umm, no. With your patch, both the diagnostic and the activation are wrong,
> whereas before only the diagnostic was wrong.
With my patch, the test becomes (eeprom[3] & 0x03), which is not null
for every possible non-null value of the two lower bits :
bit1 bit0 [bit1,bit0]&[1,1]
0 0 00
0 1 01
1 0 10
1 1 11
Whereas the other test is more restrictive, because it excludes the "11"
from the results.
The old cards still get the workaround enabled this this wider test.
> > Now, I do not get _any_ message in the logs, which means that the network
> > cards activity is closer to normality than before the patch.
>
> So your patch did not do you any good. Case closed, as far as the work-around
> is concerned.
To the contrary, it seems to do a lot of good, because the NET subsystem
does not send any more panic messages to the kernel, and the cluster has
not meltdown again so far.
> If you post the original log messages, we might be able to find the real
> bug...
Sorry, I can't, as they were suppressed (as you can see in the example
I copy-pasted before in this mail), and now I don't get any other one.
> [and please don't drop the Cc:]
Ok, if you insist.
--
Augustin Vidovic http://www.vidovic.org/augustin/
"Nous sommes tous quelque chose de naissance, musicien ou assassin,
mais il faut apprendre le maniement de la harpe ou du couteau."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-08 11:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 5:53 [PATCH] eepro100.c, kernel 2.4.1 Augustin Vidovic
2001-02-08 7:23 ` Ion Badulescu
2001-02-08 7:37 ` Augustin Vidovic
2001-02-08 7:42 ` Alan Cox
2001-02-08 7:55 ` Andrey Savochkin
2001-02-08 7:59 ` [PATCH] " Ion Badulescu
2001-02-08 10:41 ` Augustin Vidovic
2001-02-08 11:00 ` Ion Badulescu
2001-02-08 11:15 ` Augustin Vidovic
2001-02-08 11:26 ` Ion Badulescu
2001-02-08 11:44 ` Augustin Vidovic [this message]
2001-02-08 11:53 ` Ion Badulescu
2001-02-08 12:08 ` Augustin Vidovic
2001-02-12 5:32 ` Andrey Savochkin
2001-02-12 9:00 ` Ion Badulescu
2001-02-20 6:30 ` Augustin Vidovic
2001-02-20 7:21 ` Andrey Savochkin
2001-02-20 8:18 ` Augustin Vidovic
2001-02-20 23:38 ` Andrey Savochkin
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 14:38 [PATCH] " Peter Lund
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=20010208204415.A19308@ldh.org \
--to=vido@ldh.org \
--cc=alan@redhat.com \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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