[lkml]   [2001]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PDC20265, disk corruption and NMI watchdog...
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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.029 / U:2.940 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site