mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafał Bilski" <rafalbilski@interia.pl>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Tue, 1 May 2007 09:46:40 +0100	[thread overview]
Message-ID: <20070501084639.GA528@sirena.org.uk> (raw)
In-Reply-To: <20070430205522.abad2481.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

On Mon, Apr 30, 2007 at 08:55:22PM -0700, Andrew Morton wrote:
> On Mon, 30 Apr 2007 22:58:47 +0200 Rafał Bilski <rafalbilski@interia.pl> wrote:
> > > ezri user.info kernel: eth0: DSPCFG accepted after 0 usec.
> > > ezri user.notice kernel: eth0: Wake-up event 0x80000a
> > > ezri user.info kernel: eth0: Setting full-duplex based on negotiated link capability.

Could you please run "ethtool -s eth0 msglvl 0xffffffff" to turn logging
from the driver right up and send a log?  This will spam the log if
there is any traffic but should say why the driver is doing this.

> It seems to be repeatedly setting the same duplex setting.  The closest
> thing I can see in there in recent times is
> 68c90166e4aaa15ddcdd4778ad30bfb8b32534be, "Add support for using MII port
> with no PHY".

It's not just setting the same duplex setting, the WoL message indicates
that it's doing that as part of init_registers() which should only be
happening in error handling paths and during resume or open.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

  parent reply	other threads:[~2007-05-01  9:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 20:58 Rafał Bilski
2007-05-01  3:55 ` Andrew Morton
2007-05-01  7:17   ` Rafał Bilski
2007-05-01  8:23     ` Rafał Bilski
2007-05-01  8:35       ` Andrew Morton
2007-05-01 10:40         ` Rafał Bilski
2007-05-01  8:46   ` Mark Brown [this message]
2007-05-01 10:25     ` Rafał Bilski
2007-05-01 18:08       ` Mark Brown
2007-05-01 19:10         ` Rafał Bilski
2007-05-01 19:52         ` Rafał Bilski
2007-05-01 21:27           ` Mark Brown
     [not found]             ` <b3ece790705011543gdca3a9ei905d3499b6c18dc8@mail.gmail.com>
2007-05-02  5:54               ` Rafał Bilski
     [not found]                 ` <b3ece790705012303x1e5a2d03xddf6c14aec5a99d8@mail.gmail.com>
2007-05-02  6:34                   ` Rafał Bilski
2007-05-02  6:51                     ` Tim Hockin
2007-05-02  8:22                       ` Mark Brown
     [not found]                         ` <b3ece790705020744p2e73bb5fo2c0acad947a5de15@mail.gmail.com>
2007-05-02 20:05                           ` Rafał Bilski
2007-05-02 20:48                             ` Tim Hockin
2007-05-02 21:41                             ` Mark Brown
2007-05-03  6:33                               ` Rafał Bilski

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=20070501084639.GA528@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rafalbilski@interia.pl \
    /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

all inboxes | Powered by JetHome®