From: CaT <cat@zip.com.au>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
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 11:31:52 +1100 [thread overview]
Message-ID: <20010220113152.G365@zip.com.au> (raw)
In-Reply-To: <20010219144935.D21425@saw.sw.com.sg> <200102200018.f1K0IeC32394@moisil.dev.hydraweb.com>
In-Reply-To: <200102200018.f1K0IeC32394@moisil.dev.hydraweb.com>; from ionut@moisil.cs.columbia.edu on Mon, Feb 19, 2001 at 04:18:40PM -0800
On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote:
> > In my experiments wait_for_cmd timeouts almost always were related to
> > DumpStats command.
> > I think, we need to investigate what time constraints are related to this
> > command.
>
> Nothing documented...
>
> CaT, can you apply this debugging patch and let us know what you get in the
> logs? It should allow us to pinpoint the error a bit more precisely.
patched, old removed, new installed, waiting for fubar. :)
still with 2.2.18
--
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
next prev parent reply other threads:[~2001-02-20 0:33 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 [this message]
2001-02-20 7:40 ` CaT
2001-02-20 10:00 ` Ion Badulescu
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=20010220113152.G365@zip.com.au \
--to=cat@zip.com.au \
--cc=ionut@moisil.cs.columbia.edu \
--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).