From: Ion Badulescu <ionut@cs.columbia.edu>
To: CaT <cat@zip.com.au>
Cc: <linux-kernel@vger.kernel.org>,
Dragan Stancevic <visitor@valinux.com>,
Andrey Savochkin <saw@saw.sw.com.sg>
Subject: Re: eepro100 + 2.2.18 + laptop problems
Date: Tue, 20 Feb 2001 02:00:31 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.30.0102200156090.1971-100000@age.cs.columbia.edu> (raw)
In-Reply-To: <20010220184028.A503@zip.com.au>
On Tue, 20 Feb 2001, CaT wrote:
> > patched, old removed, new installed, waiting for fubar. :)
>
> Ok. this is what I got in my kern.log. this is on a fresh reboot.
>
> Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)!
> Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)!
> Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0xffffff90) timedout with(0xffffff90)!
> Feb 20 18:32:21 theirongiant last message repeated 29 times
> Feb 20 18:33:15 theirongiant last message repeated 31 times
Are you sure this driver has my patch applied? There is no way you could
have gotten these messages without getting the other printk as well..
Can you check it again, please?
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-02-20 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 11:40 eepro100 + 2.2.18 + laptop problems CaT
2001-02-13 1:26 ` Andrey Savochkin
2001-02-13 4:14 ` CaT
2001-02-19 22:21 ` CaT
2001-02-19 22:49 ` Andrey Savochkin
2001-02-20 0:18 ` Ion Badulescu
2001-02-20 0:31 ` CaT
2001-02-20 7:40 ` CaT
2001-02-20 10:00 ` Ion Badulescu [this message]
2001-02-20 10:18 ` CaT
2001-02-19 23:37 ` Dragan Stancevic
2001-02-19 22:33 ` CaT
2001-02-19 23:44 ` Dragan Stancevic
2001-02-19 22:42 ` CaT
2001-03-04 22:23 ` CaT
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=Pine.LNX.4.30.0102200156090.1971-100000@age.cs.columbia.edu \
--to=ionut@cs.columbia.edu \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--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;
as well as URLs for NNTP newsgroup(s).