From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: udelay
Date: Fri, 01 Aug 2003 22:42:41 -0400 [thread overview]
Message-ID: <3F2B2521.2060508@gentoo.org> (raw)
In-Reply-To: <1059788948.9224.62.camel@zeus.mvista.com>
Pete Popov wrote:
> Looks like the latest udelay in 2.4 is borked. Anyway else notice that
> problem? I did a 10 sec test: mdelay works, udelay is broken, at least
> for the CPU and toolchain I'm using.
>
> Pete
What's one way of testing this brokeness? I've been trying to find some
explanation for a bug of some sort in a cobalt RaQ2 in which the tulip
driver (eth0) just stops dead after several minutes of use. One of the
notable features of the tulip driver patch needed to work on the RaQ2
adds a "udelay(1000)" into the tulip source. Without it, the eth0 on
the RaQ2 is dead, so I wonder if these are related.
If they are related, then this behavior has been slowly getting worse it
seems, as eth0 on the RaQ2 apparently has had smaller and smaller
amounts of time needed before the interface died. 2.4.18, it took most
of a day, by 2.4.21, it happens within seconds.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
next prev parent reply other threads:[~2003-08-02 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 1:49 udelay Pete Popov
2003-08-02 2:42 ` Kumba [this message]
2003-08-02 12:01 ` udelay Geert Uytterhoeven
2003-08-02 20:41 ` udelay Kumba
2003-08-04 1:41 ` udelay Ralf Baechle
2003-08-04 17:29 ` udelay Pete Popov
2003-08-04 21:38 ` udelay Ralf Baechle
2003-08-04 22:04 ` udelay Pete Popov
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=3F2B2521.2060508@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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.