From: Michel Lanners <mlan@cpu.lu>
To: linuxppc-dev@lists.linuxppc.org, andre@linux-ide.org
Subject: ide_delay_50ms() freezing on PPC?
Date: Sun, 25 Jun 2000 20:13:46 +0200 (CEST) [thread overview]
Message-ID: <200006251813.UAA00680@piglet.grunz.lu> (raw)
Hi all,
The latest 2.4.0 kernels don't boot on my machine anymore. They just
freeze in detecting the Promise Ultra66 IDE controller, specifically in
ide_delay_50ms(). Here is the code:
void ide_delay_50ms (void)
{
#ifndef CONFIG_BLK_DEV_IDECS
unsigned long timeout = jiffies + ((HZ + 19)/20) + 1;
while (0 < (signed long)(timeout - jiffies));
#else
__set_current_state(TASK_UNINTERRUPTIBLE);
schedule_timeout(HZ/20);
#endif /* CONFIG_BLK_DEV_IDECS */
}
CONFIG_BLK_DEV_IDECS is support for PCMCIA IDE devices, which is not
configured in my kernel. So that function hangs if using the 'manual'
delay. Everything is OK if I force it to use schedule_timeout(), which
by the way was always the case until a few kernels ago.
So, why does the 'manual' way hang? (I suppose interrupts are not
disabled at this point, are they?)
And why can we only use schedule_timeout() if compiling with
CONFIG_BLK_DEV_IDECS?
Thanks
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-06-25 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-25 18:13 Michel Lanners [this message]
2000-06-26 5:29 ` ide_delay_50ms() freezing on PPC? Andre Hedrick
2000-06-26 20:04 ` Michel Lanners
2000-06-26 20:11 ` Andre Hedrick
2000-06-27 8:30 ` Benjamin Herrenschmidt
2000-06-29 6:02 ` Michel Lanners
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=200006251813.UAA00680@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=andre@linux-ide.org \
--cc=linuxppc-dev@lists.linuxppc.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 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).