> I got a similar problem just now on a Western Digital 3.2 GB disk. It
> occurred while testing Andre Hedrick's patches, but I was able to reproduce
> it on a vanilla 2.2.7 system. The command line was
afaik, my computer crashed because the chipset on my board (MVP3) is
flakey for non-UDMA to UDMA transfers (Dan spoke of his cdrom drive, I
have two 1-gig non-UDMA and a 17.2 gig UDMA).
>
> hdparm -c 3 -t -d1 -X34 /dev/hda
>
My guess is that the specified 'X34' flag you enabled was either
not-supported by the drive (from man page):
Apart from that, use of this flag
is seldom necessary since most/all modern IDE
drives default to their fastest PIO transfer mode
at power-on.
So you may not support multiword DMA mode2 transfers. What type of
chipset is on your motherboard?
Here's the big question (for Andre especially). In your uniform ide patch
you state:
Since ali15x3.c, via82c586.c, or piix.c do not have (U)DMA setup code
started or ready for testing, if your BIOS fails to perform its task
correctly, there is not help yet.
So am I right in saying that my bios is not initializing my (probably
via82c56) chip properly and thus will not work properly with UDMA enabled?
So there is no hope (yet) for me or for Nick?
And my second question to anyone who will answer: Can I disable UDMA but
leave DMA enabled? Sounds like a hdparm parameter but the -X stuff deals
with PIO modes and I don't know what I'd set to leave DMA w/o UDMA
enabled.
Sorry about all the time/confusion!
-V
*************************
* Vasilios F. Hoffman *
* Physics Unix Admin *
* Wesleyan University *
* www.con.wesleyan.edu *
*************************
"Like I said, Love wouldn't be so blind if the braille weren't so damned
great!" -- Armistead Maupin
> After a few seconds I got:
> hda: timeout waiting for DMA
>
> and then nothing. Every key sequence was dead. After two nostalgic minutes
> contemplating how standard this was under MS-DOS, I reached for the reset
> switch.
>
> hdparm is 3.3. I think there are newer versions, but I take what Debian
> gives me. Without the "-X34" it works fine, but I'm new to this, so I was
> following the suggestions in the man pages. In any case, I guess the crash
> is not what's meant to happen.
>
> As with Vasilios, I can test any solutions on my crash-and-burn system.
> Only limit is how much time my wife will let me spend in front of the PC
> :-(.
>
> Nick Brown, Strasbourg, France (Nick(dot)Brown(at)coe(dot)int)
>
>
>
>
>
>
>
>
> __________________________________________________________
>
> email address updates : @coe.int replaces @coe.fr
> for more information, http://dct.coe.int/info/emfci001.htm
> __________________________________________________________
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/