From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: PDC20265, disk corruption and NMI watchdog...
Date: Mon, 29 Jan 2001 03:35:23 +0100 [thread overview]
Message-ID: <20010129033523.C16593@platan.vc.cvut.cz> (raw)
In-Reply-To: <20010129032315.K1085@ppc.vc.cvut.cz>
In-Reply-To: <20010129032315.K1085@ppc.vc.cvut.cz>; from vandrove@vc.cvut.cz on Mon, Jan 29, 2001 at 03:23:15AM +0100
On Mon, Jan 28, 2001 at 17:36 Andre Hedrick wrote:
>
> Everything but a kernel version :-(
Sorry. Corruption happens since I have this motherboard just before
christmas - something about 2.4.0-test13-pre2. It was not so massive
as today - with 2.4.0-ac10 (before it just died, today it damaged
hdh in addition). I got corruption/lockup with other versions (test13-pre3,
test13-pre7, 2.4.0, 2.4.0-ac3, 2.4.0-ac8, 2.4.0-ac9) too,
but as this one (ac10) does NMI watchdog on UP, I finally found
what's wrong instead of silent death - it is why I finally wrote
this letter - so you can either __sti() or mdelay() in ide_delay_50ms.
So others will not suffer from silent death instead of IDE reset...
Then I can test whether promise recovers from this - I doubt, as it
looks like that some data for /dev/hde landed on /dev/hdh (impossible,
I know...).
> On Mon, 29 Jan 2001, Petr Vandrovec wrote:
>
> > why on Earth ide_delay_50ms uses jiffies instead of mdelay(50) ?!
> > It is invoked with interrupts disabled, causing NMI watchdog detected
> > on my system, leading to complete crash of system.
For now I said that both disks should use PIO4 and it looks stable...
But there is visible difference in speed between PIO4 and UDMA5 ;-)
I have no idea whether TOSHIBA can do UDMA CRCs, but it works fine
at work, where I connected it to i440BX, and since November I
connect it to VIA694X/686A. Both in UDMA2 mode without troubles.
Best regards,
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 parent reply other threads:[~2001-01-29 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010129032315.K1085@ppc.vc.cvut.cz>
2001-01-29 2:35 ` Petr Vandrovec [this message]
2001-01-29 0:58 Petr Vandrovec
2001-01-29 1:36 ` Andre Hedrick
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=20010129033523.C16593@platan.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®