From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <86fe18cae58b72e94b51df4965c3a7dc@quanstro.net> From: erik quanstrom Date: Wed, 6 Feb 2008 15:04:40 -0500 To: 9fans@cse.psu.edu Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 49c6d958-ead3-11e9-9d60-3106f5b1d025 > Now this is very interesting! A friend gave me an Adaptec (it really is an SiL) 2xSATA > PCI controller [1] for testing, and i was able to generate I/O errors just by reading from > both drives in paralel! Does anybody run multiple SATA drives in IDE-mode without > problems under Plan9? > > [1] pci -v > 0.20.0: disk 01.80.01 1095/3112 15 0:0000fb01 16 1:0000fa01 16 2:0000f901 16 3:0000f801 16 4:0000f701 16 5:fdffd000 512 > Silicon Image, Inc. SiI 3112 SATALink/SATARaid Controller > > cinap yes. i have a cpu server with an nforce-based motherboard and two sata hard drives recognized as ide. i have never had a problem with the ide emulation on this motherboard. i think there is insufficient evidence to jump to the conclusion that plan 9 has trouble with >1 sata drive accessed via ide emulation. if linux uses ide emulation with the same ata commands & transfer sizes, do you get the same errors? (do you notice any performance funnies?) we have a sata protcol analyzer. we've seen some mighty interesting things with it. for instance, some hard drive firmware generates sata protocol violations when pushed hard. and some hard drive firmware generates sata protocol violations with very little load. generally hard drives, when they do this send a few data FISes but forget to finish the transaction. this causes the chipset to wait forever. this can look something like what you are seeing. on the other hand, there are reports of via chipsets having trouble dealing with concurrent access and we have also seen chipsets generating sata protocol violations. it could be that the linux driver has exactly this problem but notices that it's hung up and has a few tricky moves to get the device unstuck. - erik