Date: Sun, 30 Nov 2003 17:57:45 -0600 From: Derek Ragona <derek@computinginnovations.com> To: Scott Long <scottl@freebsd.org>, Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: SiI3112 SATA controller problems - status Message-ID: <6.0.0.22.2.20031130175338.01ce7378@www.computinginnovations.com> In-Reply-To: <3FCA4CAB.2030307@freebsd.org> References: <Pine.NEB.3.96L.1031130143821.66375W-100000@fledge.watson.org> <3FCA4CAB.2030307@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I tried the 11/29 snapshot, it is indeed worse. I got a failure during the=
=20
install's fsck.
The errors I got were:
ad4: Warning - WRITE_DMA recovered from missing interrupt
ad4: Failure - WRITE_DMA status=3Dff<I couldn't copy the codes here, sorry>
followed by lots of:
ad4: timeout sending command=3Dca
ad4: error issuing DMA command
All along I have experienced "missing interrupt" errors, along with DMA=20
write errors.
-Derek
At 02:01 PM 11/30/2003, Scott Long wrote:
>Robert Watson wrote:
>>On Sun, 30 Nov 2003, Joe Marcus Clarke wrote:
>>
>>>On Fri, 2004-01-30 at 09:43, HaggeL wrote:
>>>
>>>>Hi Guys :)
>>>>
>>>>Sorry if i waste your time. I=AEm a freeBSD noob and need some help.
>>>>I want to install freeBSD in januar and have some problems. I want to
>>>>buy me a new harddrive, a serial ATA one, because i got the "Silicon
>>>>ImageR Sil 3112A-Controller" onboard (Asus A7N8X Motherboard). I
>>>>didn=AEt find a driver in the Hardware Notes of FreeBSD 5.1, and on the
>>>>Producer homepage are only ready Linuxkernels avaible
>>>>(http://12.24.47.40/display/2n/searchDirect/?searchString=3DSil+3112A&se=
archType=3Dallwords&searchby=3Dkeywords&r=3D0.8157617).
>>>>So can anyone tell me if i can get a SATA disk run? I don=AEt want to
>>>>boot from it, just read and write. Buying a new disk only for windows
>>>>use is wasted money
>>>
>>>We're having a pretty lengthy discussion about these controllers on this
>>>list right now. I suggest you read the archives. Bottom line, the
>>>controller is supported, but it's problematic. The ATA maintainer has
>>>working controllers, but there are those of us that experience data
>>>corruption, and at least one user that can't use his drive at all when
>>>connected to said controller.
>>
>>I believe a workaround was recently committed to improve behavior on older
>>cards using that chipset. Specifically the following change to
>>ata-chipset.c:
>> revision 1.48
>> date: 2003/11/28 19:01:28; author: sos; state: Exp; lines: +6 -2
>> Workaround for errata on early versions of the sii3112.
>>
>> Approved by: re@
>>Does this make any difference in your configuration?
>>Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
>>robert@fledge.watson.org Senior Research Scientist, McAfee Research
>
>This commit only fixes a silent data corruption issue. I believe that
>the issue at hand involves DMA not working at all.
>
>Scott
>
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20031130175338.01ce7378>