All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: vido@ldh.org
Cc: 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 03:00:10 -0800	[thread overview]
Message-ID: <200102081100.f18B0Am17975@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <20010208194156.A19161@ldh.org>

On Thu, 8 Feb 2001 19:41:56 +0900, Augustin Vidovic <vido@ldh.org> wrote:

> You can see a kind of sudden blackout which lasts about 3 hours, and then the
> situation resumes to normality.
> 
> At the same time, the /var/log/messages receives thousands of messages from the
> NET: subsystem.

So what _were_ those messages? Can you post them?

> Since the dmesg of the kernel tells about a work-around for such a bug, I was assuming
> that the work around was activated, but I had a doubt and after looking at the source,
> I discovered that it wasn't.

Well, your patch disables the work-around exactly for those (really old) cards
that actually need it and enables it for those that don't need it.

> Now, as Ion says, maybe it is not the "receiver lock-up bug" itself which is
> worked-around, frankly I don't know.

There is a very simple way to tell. Check your logs for messages like:

eth0: Sending a multicast list set command from a timer routine........."

If you find such messages, the work-around really did something. Otherwise,
it's the placebo effect...


Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.
-
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/

  reply	other threads:[~2001-02-08 11:00 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 [this message]
2001-02-08 11:15           ` Augustin Vidovic
2001-02-08 11:26             ` Ion Badulescu
2001-02-08 11:44               ` Augustin Vidovic
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=200102081100.f18B0Am17975@moisil.dev.hydraweb.com \
    --to=ionut@moisil.cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --cc=vido@ldh.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.