LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Patrick Ale <patrick.ale@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hdparm for lib_pata
Date: Sat, 03 Feb 2007 13:14:50 -0600	[thread overview]
Message-ID: <45C4DF2A.1070501@shaw.ca> (raw)
In-Reply-To: <fa.L/RjDlo6Njb5Jt7/9ENZuiASoV0@ifi.uio.no>

> Hi guys,
> 
> Me again, sorry.
> 
> Is it possible to make hdparm work with libata?
> I have some drives that for some reason fall back to lower UDMA
> settings (like UDMA/44) while the drive is UDMA/100. I blame the way I
> set-up my raid arrays for this and the bus not being able to handle
> all the data that goes trough it but that isnt really the case now.
> 
> Anyway, I used to be able to force the drive back with using hdparm
> -X68 -d 1 /dev/sdk
> But with the new lib_pata drivers I get "Inappropriate iotcl for
> device" and HD_IO_DRIVE_CMD Input/Output errors.
> 
> Or! Is there some other way to force the drive not to failback to
> lower UDMA settings? (Yep, I know, if this is answer, it's my risk, I
> cant and wont blame you for destructing my pr0n or severe trauma I
> suffer from losing data)

Only some of the hdparm functionality is supported in libata, which is 
partially by design. Presently there's no way to override the DMA 
settings in libata, it starts out at the fastest supported settings and 
falls back if it gets too many errors of certain types.

You shouldn't be seeing errors like this unless you have bad IDE cables 
or are using 40-wire cables with high UDMA modes. Can you post the 
output you're seeing?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-03 19:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.L/RjDlo6Njb5Jt7/9ENZuiASoV0@ifi.uio.no>
2007-02-03 19:14 ` Robert Hancock [this message]
2007-02-03 23:15   ` Stephen Clark
2007-02-03 23:28     ` Robert Hancock
2007-02-06 17:44       ` Bill Davidsen
2007-02-06 18:45         ` Mark Lord
2007-02-06 21:05         ` Jeff Garzik
2007-02-06 23:45         ` Robert Hancock
2007-02-03 23:44     ` Patrick Ale
2007-02-04  0:11       ` Stephen Clark
2007-02-04  0:18         ` Patrick Ale
2007-02-05 11:00           ` Patrick Ale
2007-02-05 14:23             ` Robert Hancock
2007-02-05 16:21               ` Patrick Ale
2007-02-05 18:15   ` Mark Lord
2007-02-06 17:49     ` Bill Davidsen
2007-02-08  2:16 Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2007-02-07 10:55 Adam J. Richter
2007-02-07 11:47 ` Patrick Ale
2007-02-03  8:41 Patrick Ale
2007-02-03  8:55 ` Patrick Ale
2007-02-03 12:07   ` Rene Rebe
2007-02-05 18:13 ` Mark Lord
2007-02-05 19:09   ` Alan
2007-02-05 21:19     ` Jeff Garzik
2007-02-05 19:21   ` Patrick Ale

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=45C4DF2A.1070501@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.ale@gmail.com \
    --subject='Re: hdparm for lib_pata' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).