All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Andriy Korud <akorud@polynet.lviv.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EEpro100 bug in 2.2.18
Date: Wed, 14 Feb 2001 21:43:57 +1100	[thread overview]
Message-ID: <20010214214356.C384@zip.com.au> (raw)
In-Reply-To: <118235361582.20010214101920@polynet.lviv.ua>
In-Reply-To: <118235361582.20010214101920@polynet.lviv.ua>; from akorud@polynet.lviv.ua on Wed, Feb 14, 2001 at 10:19:20AM +0200

On Wed, Feb 14, 2001 at 10:19:20AM +0200, Andriy Korud wrote:
> Hello all,
> My setup is Intel 440GX MB with intergrated EEPro100.
> When using Linux 2.2.18 the following happen: after reboot, I got:
>      eepro100: cmd_wait for (0xffffff90) timedout with (0xffffff90)!

I reported the same hassle a while back. A patch was suggested and am
using it now. It's in the thread titled 'eepro100 + 2.2.18 + laptop problems'.

> After power cycle, first boot works fine and all following boots (without
> power off) - see above. Very seldom (I've noticed this 2 times during
> 2 monthes) this happen during normal operation.

I jsut take the interface down and up and eventually it goes ok. It
doesn't happen all the time either.

-- 
CaT (cat@zip.com.au)		*** Jenna has joined the channel.
				<cat> speaking of mental giants..
				<Jenna> me, a giant, bullshit
				<Jenna> And i'm not mental
					- An IRC session, 20/12/2000


      reply	other threads:[~2001-02-14 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14  8:19 EEpro100 bug in 2.2.18 Andriy Korud
2001-02-14 10:43 ` CaT [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=20010214214356.C384@zip.com.au \
    --to=cat@zip.com.au \
    --cc=akorud@polynet.lviv.ua \
    --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.