public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Devin Henderson <linux@devhen.com>
To: Pauli Borodulin <boro@fixel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SiI3112 DMA? (2.6.0-test6)
Date: Sun, 05 Oct 2003 20:38:52 -0600	[thread overview]
Message-ID: <3F80D5BC.4040004@devhen.com> (raw)
In-Reply-To: <3F809382.3060201@fixel.org>

Pauli Borodulin wrote:

>> On Sun, Oct 05, 2003 at 11:50:29AM +0200, Jurgen Kramer wrote:
>>
>>> I am currently running 2.6.0-test6 on an old PII which has a SiI3112
>>> SATA PCI card in one of its PCI slots. It seems that the SiI3112 is not
>>> using DMA so now it is even running slower then the onboard PIIX4 IDE
>>> controller.
>>>
>>> Is DMA supported on the Si3112? DMA is not being enabled by the SiI3112
>>> card's BIOS (this is a cheap PCI card):
>>
> >> [...]
>
> Hugo Mills wrote:
>
>>    I get this, too, on 2.4.22-ac2, and I've had someone else tell me
>> about the same issue with their card (don't know what kernel he's
>> running).
>
> > [...]
>
> Same problems here. My kernel version is 2.4.22, but more important is 
> that the driver version is 1.06. My card is manufactured by "VScom" 
> and it looks almost identical compared to the evaluation card made my 
> Silicon Image.
>
> Here are my snippets:
>
> dmesg:
> [snip]
> SiI3112 Serial ATA: IDE controller at PCI slot 00:09.0
> PCI: Found IRQ 11 for device 00:09.0
> SiI3112 Serial ATA: chipset revision 1
> SiI3112 Serial ATA: not 100% native mode: will probe irqs later
> ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
> ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
> hde: Maxtor 6Y120M0, ATA DISK drive
> blk: queue c03426a8, I/O limit 4095Mb (mask 0xffffffff)
> hdg: Maxtor 6Y120M0, ATA DISK drive
> blk: queue c0342afc, I/O limit 4095Mb (mask 0xffffffff)
> [/snip]
>
> server:/var/log# cat /proc/ide/siimage
> Controller: 0
> SiI3112 Chipset.
> MMIO Base 0xec003000
> MMIO-DMA Base 0xec003000
> MMIO-DMA Base 0xec003008
>
> server:/var/log# hdparm /dev/hde
>
> /dev/hde:
>  multcount    = 16 (on)
>  IO_support   =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 238216/16/63, sectors = 240121728, start = 0
>
> server:/var/log# hdparm -I /dev/hde
>
> [snip]
> /dev/hde:
>
> ATA device, with non-removable media
>     Model Number:       Maxtor 6Y120M0
>     Serial Number:      Y3JZGQYE
>     Firmware Revision:  YAR51BW0
> Standards:
>     Supported: 7 6 5 4
>     Likely used: 7
> Configuration:
>     Logical         max     current
>     cylinders       16383   16383
>     heads           16      16
>     sectors/track   63      63
>     --
>     CHS current addressable sectors:   16514064
>     LBA    user addressable sectors:  240121728
>     device size with M = 1024*1024:      117246 MBytes
>     device size with M = 1000*1000:      122942 MBytes (122 GB)
> Capabilities:
>     LBA, IORDY(can be disabled)
>     Queue depth: 1
>     Standby timer values: spec'd by Standard, no device specific minimum
>     R/W multiple sector transfer: Max = 16  Current = 16
>     Advanced power management level: unknown setting (0x0000)
>     Recommended acoustic management value: 192, current value: 254
>     DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
>          Cycle time: min=120ns recommended=120ns
>     PIO: pio0 pio1 pio2 pio3 pio4
>          Cycle time: no flow control=120ns  IORDY flow control=120ns
> [/snip]
>
> server:/var/log# hdparm -i /dev/hde
>
> /dev/hde:
>
>  Model=Maxtor 6Y120M0, FwRev=YAR51BW0, SerialNo=Y3JZGQYE
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>  BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: (null):  1 2 3 4 5 6 7
>
>
> Oh, and running 'hdparm -X[anything here] -d1 -c1 -K1' makes my system 
> get stuck and I have to reset.
>
I'm having the same problems and I'm using the ol' 2.4.20-20.9 kernel 
with RH 9. I had to give up on my Serial to IDE convertor so now I'm 
using IDE again (I couldn't stand the 1.3 MB/sec transfer rate with the 
SiI3112 so I reinstalled using IDE). Anyway, I too am looking for a fix 
for this but it looks to me like very little if anything has changed 
since 2.4.x. My system also crashes (to say the least! I lose all access 
to my HD) when I try hdparm -X66 -d1 /dev/hdg.

-- 
Devin



  reply	other threads:[~2003-10-06  2:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05  9:50 SiI3112 DMA? (2.6.0-test6) Jurgen Kramer
2003-10-05 17:07 ` Hugo Mills
2003-10-05 21:56   ` Pauli Borodulin
2003-10-06  2:38     ` Devin Henderson [this message]
2003-10-06  5:29       ` Andre Hedrick
2003-10-06  7:53         ` Hugo Mills
2003-10-06  8:00           ` Andre Hedrick
2003-10-06 10:51         ` Arve Knudsen
2003-10-07  1:47         ` Devin Henderson

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=3F80D5BC.4040004@devhen.com \
    --to=linux@devhen.com \
    --cc=boro@fixel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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