linux-mips
[Top] [All Lists]

Re: udelay

To: linux-mips@linux-mips.org
Subject: Re: udelay
From: Kumba <kumba@gentoo.org>
Date: Sat, 02 Aug 2003 16:41:59 -0400
In-reply-to: <Pine.GSO.4.21.0308021401150.543-100000@vervain.sonytel.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.4.21.0308021401150.543-100000@vervain.sonytel.be>
Reply-to: kumba@gentoo.org
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
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


<Prev in Thread] Current Thread [Next in Thread>