public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kallol Biswas <kallol@efi.com>
To: Paul P Komkoff Jr <i@stingr.net>
Cc: linux-kernel@vger.kernel.org, linux.nics@intel.com,
	Andrey Nekrasov <andy@spylog.ru>
Subject: Re: NIC on Intel STL2 - bad work with eepro100 & e100
Date: Fri, 04 Oct 2002 10:03:29 -0700	[thread overview]
Message-ID: <3D9DC9E1.44D7AF7A@efi.com> (raw)
In-Reply-To: 20021004135016.GJ6318@stingr.net

I believe the problem is due to the sleep mode bit,
I  think the errata of Intel-STL2 documents it. We had a similar problem with our

STL2 based board,
clearing the sleep mode fixed it.

Paul P Komkoff Jr wrote:

> 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)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2002-10-04 16:56 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
2002-10-04 17:03   ` Kallol Biswas [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=3D9DC9E1.44D7AF7A@efi.com \
    --to=kallol@efi.com \
    --cc=andy@spylog.ru \
    --cc=i@stingr.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox