public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Jeroen Geusebroek <Jeroen.Geusebroek@osc.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.17 & Eepro(10)
Date: Thu, 30 Nov 2000 15:43:28 -0500	[thread overview]
Message-ID: <20001130154328.W26953@ns> (raw)
In-Reply-To: <NCBBJKHJIKHIFECNNOAMKEDLDLAA.Jeroen.Geusebroek@osc.nl>
In-Reply-To: <NCBBJKHJIKHIFECNNOAMKEDLDLAA.Jeroen.Geusebroek@osc.nl>; from Jeroen.Geusebroek@osc.nl on Thu, Nov 30, 2000 at 09:13:32PM +0100

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

* Jeroen Geusebroek (Jeroen.Geusebroek@osc.nl) wrote:
> 
> I'm having troubles with the eepro driver included in kernel 2.2.17.
> It stops sometimes with no apparent reason. The one thing i noticed
> is that it seems to have a lot of carrier problems(998!)
> 
> This is part of the result from ifconfig:
> 
> eth1      Link encap:Ethernet  HWaddr 00:AA:00:A6:05:01  
>           inet addr:24.132.xx.xxx  Bcast:24.132.xx.xxx  Mask:255.255.254.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:248714 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:64711 errors:1925 dropped:0 overruns:0 carrier:998
>           collisions:832 txqueuelen:100 
>           Interrupt:10 Base address:0x230

	I have similar problems, though I don't have any carrier problems:

eth0      Link encap:Ethernet  HWaddr 00:A0:C9:66:12:9B  
          inet addr:xx.xx.xx.xx  Bcast:xx.xx.xx.xx  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:214835 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33050 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:9 Base address:0xe0e0 

	Seems to just drop out when there hasn't been any activity for
a while for me though.  Give it about 10-15 seconds and it comes back.

> Needless to say i didn't have this problem with previous kernels
> (including 2.2.16).

Linux junior 2.2.17-raid #1 Wed Nov 8 07:48:57 EST 2000 i686 unknown

	I didn't run this machine very long w/ 2.2.16 so I don't really
know if previous versions had the same problem.  If I have some time,
perhaps over the weekend, I'll try and find out.

		Stephen

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

      reply	other threads:[~2000-11-30 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 20:13 2.2.17 & Eepro(10) Jeroen Geusebroek
2000-11-30 20:43 ` Stephen Frost [this message]

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=20001130154328.W26953@ns \
    --to=sfrost@snowman.net \
    --cc=Jeroen.Geusebroek@osc.nl \
    --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