public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Nekrasov <andy@spylog.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Fu <michael.fu@linux.co.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] e100 driver fails to initialize the hardware after kernel bootup through kexec
Date: Fri, 24 Jan 2003 17:57:55 +0300	[thread overview]
Message-ID: <20030124145754.GA1116@an.local> (raw)
In-Reply-To: <m18yxaeje3.fsf@frodo.biederman.org>

Hello Eric W. Biederman,

Once you wrote about "Re: [BUG] e100 driver fails to initialize the hardware after kernel bootup through kexec":
> Michael Fu <michael.fu@linux.co.intel.com> writes:
> 
> > After kernel was bootup through kexec command, the NIC failed to
> > initialize. The 2.5.52 kernel was patched with kexec and kexec-hwfix
> > patch.
> 
> Interesting...  The patch goes cleanly onto newer kernels so feel
> free to play with them.  You are running a single cpu system
> so the kexec-hwfix patch should not make a difference at this point.
> 
> Your interrupt routing is via ACPI interesting...
> 
> > 
> > the following was is the dmesg output:
> 
> [snip]
> > Intel(R) PRO/100 Network Driver - version 2.1.24-k2
> > Copyright (c) 2002 Intel Corporation
> > 
> > 
> > 
> > 
> > 
> > 
> > PCI: Enabling device 02:09.0 (0000 -> 0003)
> > PCI: Setting latency timer of device 02:09.0 to 64
> > e100: selftest timeout
> > e100: Failed to initialize, instance #0

use NIC EEPro100+ on INTEL STL2 motherboard, with "eepro100" driver - all work ok.

or "e100" driver and with patch:


--- drivers/net/e100/e100.h-    Wed Dec  4 15:16:08 2002 
+++ drivers/net/e100/e100.h     Wed Dec  4 15:16:20 2002 
@@ -100,7 +100,7 @@
 
 #define E100_MAX_NIC 16
 
-#define E100_MAX_SCB_WAIT      100     /* Max udelays in wait_scb */ 
+#define E100_MAX_SCB_WAIT      5000    /* Max udelays in wait_scb */ 
 #define E100_MAX_CU_IDLE_WAIT  50      /* Max udelays in wait_cus_idle */
 
 /* HWI feature related constant */

all work ok.


  reply	other threads:[~2003-01-24 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1042450072.1744.75.camel@aminoacin.sh.intel.com>
2003-01-24  6:49 ` [BUG] e100 driver fails to initialize the hardware after kernel bootup through kexec Michael Fu
2003-01-24 14:01   ` Eric W. Biederman
2003-01-24 14:57     ` Andrey Nekrasov [this message]
2003-01-24 16:07       ` Jeff Garzik
2003-01-26 21:56         ` Henning P. Schmiedehausen
     [not found] ` <mailman.1043391842.14884.linux-kernel2news@redhat.com>
2003-01-24 16:49   ` Pete Zaitcev

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=20030124145754.GA1116@an.local \
    --to=andy@spylog.ru \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.fu@linux.co.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