From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Tom Murphy <freyason@yahoo.com>
Cc: Dragan Stancevic <visitor@valinux.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test12-pre7 shutdowns and eepro100 woes
Date: Tue, 12 Dec 2000 14:28:46 +0800 [thread overview]
Message-ID: <20001212142846.A14979@saw.sw.com.sg> (raw)
In-Reply-To: <20001211185219.28022.qmail@web2006.mail.yahoo.com>
In-Reply-To: <20001211185219.28022.qmail@web2006.mail.yahoo.com>; from "Tom Murphy" on Mon, Dec 11, 2000 at 10:52:19AM
Hello,
On Mon, Dec 11, 2000 at 10:52:19AM -0800, Tom Murphy wrote:
> Also, regarding the eepro100 driver, are there any plans to fix
> support for the following chipset (given by lspci):
>
[snip]
> I have one of these at work and I will get the following messages:
>
> Dec 11 10:46:13 morpheus kernel: eepro100: cmd_wait for(0xffffff80)
> +timedout with(0xffffff80)!
> Dec 11 10:46:20 morpheus last message repeated 6 times
>
> (using eepro100 from 2.2.18pre27.. I guess it's not 2.2.18 proper)
Last time you asked the similar question, my answer to you bounced.
This debug output was submitted by Dragan Stancevic <visitor@valinux.com>.
The current timeout values are high enough to try to increase them more.
The question I'm interested in is how command 0x80 appeared in the command
register...
To answer your question in short, yet, we hope to fix the problem sooner or
later.
Regards
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-12 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 18:52 2.4.0-test12-pre7 shutdowns and eepro100 woes Tom Murphy
2000-12-12 6:28 ` Andrey Savochkin [this message]
2000-12-20 22:28 ` Dragan Stancevic
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=20001212142846.A14979@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=freyason@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=visitor@valinux.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