lkml.org 
[lkml]   [1999]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: UDMA lockup in 2.0.36


On Thu, 10 Jun 1999, Victor Orlikowski wrote:

> Hi all,
>
> Hate to bother with 2.0.x stuff, but.....
> Recently my ailing Western Digital HD started spitting bad blocks at a
> rapid rate, and so I purchased a brand spanking new Seagate Medalist to
> replace it. Nice, shiny fast, supports UDMA, and hook it into my UDMA
> enabled motherboard.
> Kernel detects it as UDMA, and treats it with kid gloves, till it reached
> the spot where DMA is enabled with hdparm in my rc.local.

Try _not_ to use hdparm. There is an option in the kernel "dma by default"
and kernel should recognize the drive and turn the dma on. Some of the
settings in hdparm are interfering with normal udma operation. (I had this
problem too).

Vladimir Dergachev


> Approximately 5 seconds later, total lockup. No keyboard. No syslog. Hit
> the reset switch. No fs errors (thank goodness), but no useful log of
> what happened.
> Now, if I disable UDMA in the BIOS, the drive acts fine, and drive
> reports itself as capable of DMA. Enabling DMA at this point causes no
> problems.
> As I said, the new drive is a Seagate Medalist, UDMA, 128k cache, 4.3G.
> Motherboard is an Intel TX, NOT TX Pro.
> Ideas?
>
> Thanks in advance,
> Victor
>
> -
> 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/

\
 
 \ /
  Last update: 2005-03-22 13:52    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site