From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Stefan Hoffmeister <lkml.2001@econos.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.6: eepro100 does not survive warm boot
Date: Wed, 11 Jul 2001 11:13:56 -0700 [thread overview]
Message-ID: <20010711111356.A15553@saw.sw.com.sg> (raw)
In-Reply-To: <gg4oktks8jch0sqsdivo2m5071t2h0q1jp@4ax.com>
In-Reply-To: <gg4oktks8jch0sqsdivo2m5071t2h0q1jp@4ax.com>; from "Stefan Hoffmeister" on Wed, Jul 11, 2001 at 10:47:35AM
Hi,
Apparently, the card is unaccessible after warm reboot.
It should be a PCI initialization problem.
What lspci shows after the warm reboot?
Andrey
On Wed, Jul 11, 2001 at 10:47:35AM +0200, Stefan Hoffmeister wrote:
> For testing purposes, I am running a stock 2.4.6 kernel on a Sony VAIO
> Z600 NE notebook (Sony Z505 JS in the US).
>
> On a cold boot, I get this information in dmesg:
>
> >eth0: OEM i82557/i82558 10/100 Ethernet, 08:00:46:07:49:99, IRQ 9.
> > Receiver lock-up bug exists -- enabling work-around.
> > Board assembly 100001-001, Physical connectors present: RJ45
[snip]
>
> With the exact same kernel, after a warm boot ('reboot'), the picture
> changes to
>
> >eth0: Invalid EEPROM checksum 0xff00, check settings before activating this device!
> >eth0: OEM i82557/i82558 10/100 Ethernet, FF:FF:FF:FF:FF:FF, IRQ 9.
> > Board assembly ffffff-255, Physical connectors present: RJ45 BNC AUI MII
> > Primary interface chip unknown-15 PHY #31.
> > Secondary interface chip i82555.
> >Self test failed, status ffffffff:
> > Failure to initialize the i82557.
> > Verify that the card is a bus-master capable slot.
>
>
> Result: The network essentially is dead; I cannot make HTTP requests to a
> server on the LAN, for instance. Shut down the system and go through a
next prev parent reply other threads:[~2001-07-11 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 8:47 Stefan Hoffmeister
2001-07-11 18:13 ` Andrey Savochkin [this message]
2001-07-11 23:07 ` Stefan Hoffmeister
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=20010711111356.A15553@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.2001@econos.de \
/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
all inboxes | Powered by JetHome®