All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul P Komkoff Jr <i@stingr.net>
To: linux-kernel@vger.kernel.org
Cc: linux.nics@intel.com, Andrey Nekrasov <andy@spylog.ru>
Subject: Re: NIC on Intel STL2 - bad work with eepro100 & e100
Date: Fri, 4 Oct 2002 17:50:16 +0400	[thread overview]
Message-ID: <20021004135016.GJ6318@stingr.net> (raw)
In-Reply-To: <20021004113128.GA31145@an.local>

Replying to Andrey Nekrasov:
> 			Intel Server Board STL2.
>       Network: onboard NIC "Intel(R) 82559 single chip PCI LAN controller"

I have almost the same behavior here except that eepro100 works
without freezes. Maybe spylog servers' NIC load is much more higher
than mine :)

Intel support guys advised me to test both versions of e100 driver.

ftp://aiedownload.intel.com/df-support/2896/eng/e100-2.1.15.tar.gz
ftp://aiedownload.intel.com/df-support/2896/eng/e100-1.8.38.tar.gz

Unfortunately, I haven't tested it yet. My investigation shows that
the following fragment of e100_main.c code fails:

<code from="e100_hw_init">
     if (!e100_wait_exec_cmplx(bdp, 0, SCB_RUC_LOAD_BASE))
            return false;
</code>

we returning false here.

And I am stalled for now till the end of next week until the ACM ICPC
Qfinal is over :(

-- 
Paul P 'Stingray' Komkoff 'Greatest' Jr /// (icq)23200764 /// (http)stingr.net
  When you're invisible, the only one really watching you is you (my keychain)

  reply	other threads:[~2002-10-04 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 11:31 NIC on Intel STL2 - bad work with eepro100 & e100 Andrey Nekrasov
2002-10-04 13:50 ` Paul P Komkoff Jr [this message]
2002-10-04 17:03   ` Kallol Biswas

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=20021004135016.GJ6318@stingr.net \
    --to=i@stingr.net \
    --cc=andy@spylog.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.nics@intel.com \
    /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.