All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Juergen Hasch <Hasch@t-online.de>
Cc: linux-kernel@vger.kernel.org, J Sloan <jjs@pobox.com>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Thu, 1 Nov 2001 09:03:48 +0100	[thread overview]
Message-ID: <20011101090348.E2102@stud.ntnu.no> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDCD06E.8AF8FF69@pobox.com> <20011031090125.B10751@stud.ntnu.no> <15yzpC-26N6dEC@fwd04.sul.t-online.com>
In-Reply-To: <15yzpC-26N6dEC@fwd04.sul.t-online.com>; from Hasch@t-online.de on Wed, Oct 31, 2001 at 07:10:49PM +0100

Juergen Hasch:
> If you use the e100 driver, you can look at 
> /proc/net/PRO_LAN_ADAPTERS/eth0.info
> If the "Tx_TCO_Packets" entry isn't zero after NFS times out,
> this may be your problem.
> With the eepro100 driver you will only see overruns with ifconfig.

Here's the full /proc/net/PRO_LAN_Adapters/eth0.info output (after NFS
timeouts):

gekko:~# cat /proc/net/PRO_LAN_Adapters/eth0.info 
Description               Intel(R) 8255x-based Ethernet Adapter
Driver_Name               e100
Driver_Version            1.6.22
PCI_Vendor                0x8086
PCI_Device_ID             0x1229
PCI_Subsystem_Vendor      0x1028
PCI_Subsystem_ID          0x009b
PCI_Revision_ID           0x0008
PCI_Bus                   2
PCI_Slot                  4
IRQ                       16
System_Device_Name        eth0
Current_HWaddr            00:B0:D0:F0:8B:65
Permanent_HWaddr          00:B0:D0:F0:8B:65
Part_Number               07195d-000

Link                      up
Speed                     100
Duplex                    full
State                     up

Rx_Packets                27747043
Tx_Packets                25999146
Rx_Bytes                  1730389022
Tx_Bytes                  21884644
Rx_Errors                 0
Tx_Errors                 0
Rx_Dropped                0
Tx_Dropped                0
Multicast                 0
Collisions                0
Rx_Length_Errors          0
Rx_Over_Errors            0
Rx_CRC_Errors             0
Rx_Frame_Errors           0
Rx_FIFO_Errors            0
Rx_Missed_Errors          0
Tx_Aborted_Errors         0
Tx_Carrier_Errors         0
Tx_FIFO_Errors            0
Tx_Heartbeat_Errors       0
Tx_Window_Errors          0

Rx_TCP_Checksum_Good      0
Rx_TCP_Checksum_Bad       0
Tx_TCP_Checksum_Good      0
Tx_TCP_Checksum_Bad       0

Tx_Abort_Late_Coll        0
Tx_Deferred_Ok            0
Tx_Single_Coll_Ok         0
Tx_Multi_Coll_Ok          0
Rx_Long_Length_Errors     0
Rx_Align_Errors           0

Tx_Flow_Control_Pause     0
Rx_Flow_Control_Pause     0
Rx_Flow_Control_Unsup     0

Tx_TCO_Packets            0
Rx_TCO_Packets            1
scbp = 0xf89da000        bddp = 0xf77568c0


-- 
Thomas

  reply	other threads:[~2001-11-01  8:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  1:13 Intel EEPro 100 with kernel drivers Thomas Langås
2001-10-29  1:57 ` Jim Hull
2001-10-29  3:43 ` J Sloan
2001-10-31  8:01   ` Thomas Langås
2001-10-31 15:22     ` Andrey Savochkin
2001-10-31 15:52       ` Kirill Ratkin
2001-11-01  7:55       ` Thomas Langås
2001-11-01  9:47         ` Andrey Savochkin
2001-11-01 10:00           ` Thomas Langås
2001-10-31 18:10     ` Juergen Hasch
2001-11-01  8:03       ` Thomas Langås [this message]
2001-11-01  8:48         ` Juergen Hasch
2001-11-01  9:06           ` Thomas Langås
2001-11-01  9:43             ` Juergen Hasch
2001-11-01 11:11       ` Andrey Savochkin
2001-11-01 12:00         ` Thomas Langås
2001-11-01 12:15           ` Juergen Hasch
2001-11-01 13:39       ` Henning P. Schmiedehausen
2001-10-29 10:44 ` Alan Cox
2001-10-29 11:40   ` Michael Rozhavsky
2001-10-29 11:49     ` Alan Cox
2001-10-29 11:45       ` Michael Rozhavsky
2001-10-29 13:52   ` Thomas Langås
2001-10-30  8:36 ` Jarmo Järvenpää
2001-10-30  8:54   ` Dead2
2001-10-30  9:02     ` Jarmo Järvenpää

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=20011101090348.E2102@stud.ntnu.no \
    --to=tlan@stud.ntnu.no \
    --cc=Hasch@t-online.de \
    --cc=jjs@pobox.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 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.