From: manu <hislen@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: SiI2112 + Seagate + nFroce2: no DMA!
Date: Tue, 31 Dec 2002 21:55:59 -0800 [thread overview]
Message-ID: <3E1282EF.30300@mindspring.com> (raw)
Hi,
Forgive me for intruding in this list as an outsider.
I'm about to give up on my SATA drive as I can't get it to work properly.
So I thought I may try asking the experts before falling back to PATA.
I have seen many mails reporting the same issue, some of them 6-month old:
- SATA drive comes up in pio mode, not in dma
- trying to turn on dma with hdparm is a nightmare: I/O errors, crash
with data corruption... I tried both:
hddarm -d1 /dev/hde
and:
hdparm -u1 -c3 -d1 -X66 /dev/hde
crash in both cases :-((
Here's my equipment:
ABIT AN7 motherboard (nForce2 chipset, SiI3112 SATA controller)
AMD Athlon XP 2600+ (+ 512 DDR / 400 MHz)
SATA HD Seagate Barracuda 160 Gb
The SATA HD is my only drive. The only thing connected to my IDE
controllers is a DVD/CD combo.
Running Linux Redhat 9.0
kernel 2.4.20-28.9
Traces from dmesg:
<<<<<<<<<<
...
Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
AMD_IDE: PCI device 10de:0065 (nVidia Corporation) (rev a2) UDMA100
controller o
n pci00:09.0
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
, BIOS settings: hde:pio, hdf:pio
, BIOS settings: hdg:pio, hdh:pio
hda: PIONEER DVD-RW DVR-106D, ATAPI CD/DVD-ROM drive
hde: ST3160023AS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xe080d080-0xe080d087,0xe080d08a on irq 11
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63
ide-floppy driver 0.99.newide
Partition check:
hde: hde1 hde2 hde3
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
>>>>>>>>>>
I've been googling for days now and could not come accross a solution,
on the contrary I came under the impression that the combination of
SiI3112 +and Seagate was doomed.
I cannot use this brand new computer for anything else then mail and
web, performance is catastrophic:
<<<<<<<<<<
[root]# hdparm -Tt /dev/hde
/dev/hde:
Timing buffer-cache reads: 128 MB in 0.33 seconds =387.88 MB/sec
Timing buffered disk reads: 64 MB in 48.49 seconds = 1.32 MB/sec
>>>>>>>>>>
1.32 MB !!!!! I should be getting 50 MB at least.
Isn't there a solution??
I am willing to try patches of experimental code. At this point I am
looking at reinstalling everything on a PATA drive anyway, so I have
nothing to loose.
Thanks,
Emmanuel.
PS: please CC me in the reply as I am not subscribed to this list.
next reply other threads:[~2004-01-20 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 5:55 manu [this message]
2004-01-20 8:58 ` SiI2112 + Seagate + nFroce2: no DMA! Hugo Mills
2003-01-01 17:06 ` manu
2004-01-24 9:27 ` Emmanuel Hislen
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=3E1282EF.30300@mindspring.com \
--to=hislen@mindspring.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.