From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: udelay
Date: Sat, 02 Aug 2003 16:41:59 -0400 [thread overview]
Message-ID: <3F2C2217.5010006@gentoo.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0308021401150.543-100000@vervain.sonytel.be>
Geert Uytterhoeven wrote:
> Any kernel messages (e.g. transmit timed out) from the tulip driver when it
> dies?
None that I can see. If I'm using SSH, input/output just stops cold.
In some cases, I have noticed that if you send a single character (like
you were in a text editor when input/output died), and you wait a minute
or so, it will appear. This seems to mean the interface hasn't died
completely, but seems to havce slowed down to the point of complete
unsuability, like >1bps would be my guess.
Restarting the interface fixes it for several seconds until it drops
again. I usually disconnect from the serial console before trying any
SSH activity, as serial console work + network activity can halt the
kernel (which I have confirmed does occur in 2.4.21 CVS).
As an experiment, I did try replacing the udelay(1000) line in the
cobalt patch with mdelay(1) to see if this udelay() brokeness was the
issue, but it still drops out after several 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 20: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 ` udelay Kumba
2003-08-02 12:01 ` udelay Geert Uytterhoeven
2003-08-02 20:41 ` Kumba [this message]
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=3F2C2217.5010006@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.