From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: sajjad@vgkk.com (A.Sajjad Zaidi), linux-kernel@vger.kernel.org
Subject: Re: Promise, DMA and RAID5 problems running 2.4.1
Date: Wed, 7 Feb 2001 20:40:21 MET-1 [thread overview]
Message-ID: <14D3DB587F98@vcnet.vc.cvut.cz> (raw)
On 7 Feb 01 at 19:33, Alan Cox wrote:
> > It is known bug which I reported to Andre already. Open
> > drivers/ide/ide.c in favorite text editor, and replace strange
> > body of ide_delay_50ms() with simple mdelay(50). Promise driver
> > invokes ide_delay_50ms with interrupts disabled, so it freezes
> > here forever. If you have NMI watchdog, you'll get nice oopses.
>
> Its a bug in the promise driver. ide_delay_50ms() is being friendly to the
> rest of the box. If the reset path for the promise cant be polite then it
> should use mdelay() itself.
Iff CONFIG_BLK_DEV_IDECS is set then yes, doing schedule is better.
But I do not see any benefit in doing
unsigned long timeout = jiffies + ((HZ + 19)/20) + 1;
while (0 < (signed long)(timeout - jiffies));
over
mdelay(50);
And on my box, busy while loop is executed, not schedule(HZ/20)...
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-07 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 20:40 Petr Vandrovec [this message]
2001-02-07 20:06 ` Promise, DMA and RAID5 problems running 2.4.1 Alan Cox
2001-02-07 20:53 ` Andre Hedrick
2001-02-09 8:09 ` Vojtech Pavlik
[not found] <Pine.LNX.4.10.10102070924340.19012-100000@coffee.psychology.mcmaster.ca>
2001-02-08 2:00 ` A.Sajjad Zaidi
2001-02-08 2:06 ` Stephen Wille Padnos
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 13:15 Petr Vandrovec
2001-02-07 19:33 ` Alan Cox
2001-02-08 5:07 ` A.Sajjad Zaidi
2001-02-07 10:12 A.Sajjad Zaidi
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=14D3DB587F98@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sajjad@vgkk.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