All of lore.kernel.org
 help / color / mirror / Atom feed
From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.6] eepro100 vs e100?
Date: Wed, 19 May 2004 07:11:31 +0000 (UTC)	[thread overview]
Message-ID: <c8f1b3$fvv$1@news.cistron.nl> (raw)
In-Reply-To: 200405190858.44632.lkml@kcore.org

Jan De Luyck  <lkml@kcore.org> wrote:
>I'm wondering what driver is the "best" one to use? Judging by the comments in 
>the files, the e100 driver seems to be the best maintained, though I'm 
>probably wrong ;p

We have a usenet server we use with 2.6.6 kernel and the eepro100 gives
IRQ problems:

May 16 01:35:58 enterprise kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
May 16 01:35:58 enterprise kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
May 16 01:35:58 enterprise kernel: eth0: OEM i82557/i82558 10/100 Ethernet, 00:90:27:BE:B6:85, IRQ 18.
May 16 01:35:58 enterprise kernel:   Board assembly 734938-001, Physical connectors present: RJ45
May 16 01:35:58 enterprise kernel:   Primary interface chip i82555 PHY #1.
May 16 01:35:58 enterprise kernel:   General self-test: passed.
May 16 01:35:58 enterprise kernel:   Serial sub-system self-test: passed.
May 16 01:35:58 enterprise kernel:   Internal registers self-test: passed.
May 16 01:35:58 enterprise kernel:   ROM checksum self-test: passed (0x04f4518b).
May 16 01:35:58 enterprise kernel: eth0: freeing mc frame.
May 16 01:47:12 enterprise kernel: eth0: TX underrun, threshold adjusted.
May 16 01:47:27 enterprise last message repeated 26 times

Where as the e100 is rocksolid (knock wood) under sometimes heavy load:

Linux 2.6.6-bk2 (root@enterprise) (gcc 3.3.3 ) #1 Sun May 16 10:50:59 CEST 2004 1CPU [enterprise.cistron.nl]

Memory:      Total        Used        Free      Shared     Buffers      
Mem:       1037228     1031548        5680           0      624540
Swap:      1027144        9424     1017720

Bootup: Sun May 16 11:34:58 2004    Load average: 1.88 1.77 1.69 5/87 9230

user  :       6:03:53.43   8.7%  page in :        0
nice  :       0:51:24.39   1.2%  page out:        0
system:       9:22:34.92  13.5%  swap in :        0
idle  :      12:48:17.34  18.4%  swap out:        0
uptime:   2d 21:35:04.35         context :483979334

irq  0: 250377255 timer                 irq 12:         3                      
irq  1:         3                       irq 14:  11055492 ide0                 
irq  3:         2                       irq 15:  11058878 ide1                 
irq  4:       193 serial                irq 16:  27773698 sym53c8xx            
irq  8:         3 rtc                   irq 18: 996592375 eth0                 
irq  9:         0 acpi                  irq 19:  22025755 ide2, ide3    


So _i_ would advise the e100 driver.

Danny 
(personal view etc)

-- 
 /"\                        | Dying is to be avoided because
 \ /  ASCII RIBBON CAMPAIGN | it can ruin your whole career 
  X   against HTML MAIL     | 
 / \  and POSTINGS          | - Bob Hope


  reply	other threads:[~2004-05-19  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  6:58 [2.6.6] eepro100 vs e100? Jan De Luyck
2004-05-19  7:11 ` Danny ter Haar [this message]
2004-05-19 11:12 ` Meelis Roos
2004-05-19 11:19 ` J. Ryan Earl
2004-05-19 15:46 ` Bill Davidsen
2004-05-19 22:48 ` Darren Williams

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='c8f1b3$fvv$1@news.cistron.nl' \
    --to=dth@ncc1701.cistron.net \
    --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.