public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: New IDE code and DMA failures
Date: Thu, 11 Apr 2002 14:52:59 +0200	[thread overview]
Message-ID: <3CB5872B.9090708@evision-ventures.com> (raw)
In-Reply-To: <200204111236.g3BCaMX10247@Port.imtp.ilyichevsk.odessa.ua> <3CB57C1F.9060607@evision-ventures.com> <200204111341.g3BDfJX10546@Port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:

> # hdparm -i /dev/hda
>  Model=Maxtor 51369U3, FwRev=DA620CQ0, SerialNo=EK3HAE61C
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>  BuffType=3(DualPortCache), BuffSize=2048kB, MaxMultSect=16, MultSect=16
>  DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=0(slow)
>  CurCHS=17475/15/63, CurSects=16513875, LBA=yes
>  LBA CHS=512/511/63 Remapping, LBA=yes, LBAsects=26520480
>  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
>  UDMA modes: mode0 mode1 *mode2

To answer an later question.
The asterix here denotes the active UDMA mode!

> 
> # hdparm -i /dev/hdc
>  Model=ST31277A, FwRev=0.75, SerialNo=VAE07701
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>  RawCHS=2482/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=0(?), BuffSize=0kB, MaxMultSect=16, MultSect=16
>  DblWordIO=no, maxPIO=1(medium), DMA=yes, maxDMA=2(fast)
>  CurCHS=2482/16/63, CurSects=2501856, LBA=yes
>  LBA CHS=620/64/63 Remapping, LBA=yes, LBAsects=2501856
>  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
>  IORDY=on/off, tPIO={min:383,w/IORDY:120}, PIO modes: mode3 mode4
> 
> I have problems with hdc. hda is mostly unused, so maybe it is DMA errors
> prone too but I have not seen that yet.
> 
> 
>>3. Some timeout values got increased to more generally used values (in esp.
>>    IBM microdrives advice about timeout values. Could you see whatever
>>    the data doesn't eventually go to the disk after georgeous
>>    amounts of time.
> 
> 
> Erm.. my English comprehension fails here... do you say my disk
> does not like bigger timeouts?

Please just wait and look whatever the driver actually recovers (can be
minutes...)

> 
>>4. Could you try to set the DMA mode lower then it's set up
>>    per default by using hdparm and try whatever it helps?
> 
> 
> Current params:
> 
> # hdparm /dev/hda /dev/hdc
> /dev/hda:
>  multcount    = 16 (on)
>  I/O support  =  1 (32-bit)
>  unmaskirq    =  1 (on)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Could you try to disable this please? This can cause trouble
as well.

>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  BLKRAGET failed: Invalid argument
>  geometry     = 1754/240/63, sectors = 26520480, start = 0
> 
> /dev/hdc:
>  multcount    = 16 (on)
>  I/O support  =  1 (32-bit)
>  unmaskirq    =  1 (on)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  BLKRAGET failed: Invalid argument
>  geometry     = 620/64/63, sectors = 2501856, start = 0
> 
> I can't quite figure what MW/UDMA mode is active.

See above.


  reply	other threads:[~2002-04-11 13:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 17:39 New IDE code and DMA failures Denis Vlasenko
2002-04-11 12:05 ` Martin Dalecki
2002-04-11 18:44   ` Denis Vlasenko
2002-04-11 12:52     ` Martin Dalecki [this message]
2002-04-11 19:17       ` Denis Vlasenko
2002-04-11 15:48     ` Vojtech Pavlik
2002-04-12 14:47       ` Denis Vlasenko
2002-04-11 13:05 ` Ted Deppner
2002-04-11 14:10   ` Oleg Drokin
2002-04-13  0:58     ` Ted Deppner
2002-04-13  7:07       ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11 16:27 Petr Vandrovec
2002-04-13  1:02 ` Ted Deppner

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=3CB5872B.9090708@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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