public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Corry <erik@arbat.com>
To: linux-kernel@vger.kernel.org, "Andrey V . Savochkin" <saw@saw.sw.com.sg>
Subject: eepro100/2.2.19: failure when switching to promiscuous mode
Date: Tue, 18 Sep 2001 09:47:43 +0200	[thread overview]
Message-ID: <20010918094743.A17515@arbat.com> (raw)

Hi

Kernel 2.2.19, SMP, PIII-800

I've been seeing the eepro100 ethernet driver stop working when VMWare
puts it in promiscuous mode.  /var/log/messages looks like this:

Sep 18 08:35:18 gna kernel: bridge-eth0: set IFF_PROMISC
Sep 18 08:35:32 gna sshd[531]: Generating new 768 bit RSA key.
Sep 18 08:35:32 gna sshd[531]: RSA key generation complete.
Sep 18 08:35:36 gna kernel: nfs: server noatun is not responding
Sep 18 08:35:36 gna kernel: rtc: lost some interrupts at 256Hz.
Sep 18 08:35:42 gna kernel: eth0: Transmit timed out: status f048  0c00 at 911685345/911685405 command 000ca000.
Sep 18 08:35:52 gna kernel: nfs: server noatun still not responding
Sep 18 08:35:52 gna kernel: rtc: lost some interrupts at 256Hz.
Sep 18 08:36:07 gna kernel: nfs: server noatun still not responding
Sep 18 08:36:07 gna kernel: rtc: lost some interrupts at 256Hz.
Sep 18 08:36:23 gna kernel: nfs: server noatun still not responding

/proc/pci says:

Bus  0, device  14, function  0:
  Ethernet controller: Intel 82557 (rev 8).
    Medium devsel.  Fast back-to-back capable.  IRQ 21.  Master Capable.  Latency=64.  Min Gnt=8.Max Lat=56.
    Non-prefetchable 32 bit memory at 0xf4102000 [0xf4102000].
    I/O at 0x2800 [0x2801].
    Non-prefetchable 32 bit memory at 0xf4000000 [0xf4000000].

Yours,

-- 
Erik Corry erik@arbat.com           Ceterum censeo, Microsoftem esse delendam!

                 reply	other threads:[~2001-09-18  7:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010918094743.A17515@arbat.com \
    --to=erik@arbat.com \
    --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