mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Volker Sauer <vsauer@dvs.tu-darmstadt.de>
To: linux-kernel@vger.kernel.org
Cc: adi@postpi.com
Subject: D-Link DFE-580TX and snmpd problems, who's maintainer of sundance.c ?
Date: Wed, 24 Oct 2007 19:11:29 +0200	[thread overview]
Message-ID: <20071024171129.GA14255@volker-sauer.de> (raw)

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

Hi,

there already was a thread on this topic in summer but with no result:

http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4b433f881e3585b2/a36ccba40ef2e59d?hl=en&lnk=gst&q=Re%3A+D-Link+DFE-580TX+4+port+NIC+problems#a36ccba40ef2e59d

Adi tracked down, that the messages in the syslog (in my case appearing
exactly every 30 seconds), come from snmpd running on the same machine
calling SIOCDEVPRIVATE.

This behaviour still exists in 2.6.23.1

I'm neither a skilled C-programmer nor a kernel-expert, but looking at
drivers/net/sundance.c:1605 I see, that SIOCDEVPRIVATE does
nothing else then printing this debug message.

So the questions is: why? What is this good for?
And: can I remove it? I can not abandon snmpd and the messages spam my
syslog.
Or: do I have to patch snmpd?

Regards
Volker

-> Please CC: me, I'm not on the list <-

P.S.: there's no one in the MAINTAINERS file for sundance.c. Is someone
here who still cares about this driver?


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

             reply	other threads:[~2007-10-24 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 17:11 Volker Sauer [this message]
2007-10-24 21:46 ` Francois Romieu
2007-10-25 15:13   ` Volker Sauer

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=20071024171129.GA14255@volker-sauer.de \
    --to=vsauer@dvs.tu-darmstadt.de \
    --cc=adi@postpi.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome