Date: Sun, 05 Oct 2003 20:33:09 -0500 From: Derek Ragona <derek@computinginnovations.com> To: Soren Schmidt <sos@spider.deepcore.dk>, current@freebsd.org Subject: Re: SiI3112 SATA controller problems - status Message-ID: <5.2.1.1.2.20031005201310.011a2b08@www.computinginnovations.com> In-Reply-To: <5.2.1.1.2.20030930160757.011dcc00@www.computinginnovations .com> References: <200309302006.h8UK6ec0025565@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
S=F8ren,
The SATA seems better, but is still not working. I tried the Oct 5=20
snapshot, doing a clean install. I CVSup'd and did
make buildworld
make buildkernel KERNCONF=3DGENERIC
make installkernel KERNCONF=3DGENERIC
reboot to single user
mount -a
swapon -a
mergemaster -p
make installworld
System has the same DMA write problems. In this recent case it was=20
installing termcap. I tried the Oct 1 snapshot and it was the same, it=20
errored in installworld installing tar.
The SATA is stabler as I can buildworld, but not stable enough to handle=20
the installworld copies.
Here is what I copied from the console after it went into the debugger:
spec_getpages I/O Read failure(error=3D5)
vm_fault: pager read error
panic: initiate_write_inodeblock_ufs2: already started
Let me know if you want more information. I will have to reinstall to get=
=20
a dmesg, if you want a new one.
-Derek
At 04:09 PM 9/30/2003 -0500, Derek Ragona wrote:
>Great news to hear S=F8ren.
>
>Do you know when a snapshot with the fix will be available? Since I=20
>cannot complete a buildworld using the SATA drive without the fix.
>
>Thanks for the fix.
>
> -Derek
>
>
>At 10:06 PM 9/30/2003 +0200, Soren Schmidt wrote:
>
>>I have now found a way to reproduce the DMA problems some setups seems
>>to be having with the SiI3112A SATA chip.
>>
>>Now, if I use real SATA drives, (and I mean real SATA drives, the
>>WD Raptor fx is not a real SATA device but just a PATA device
>>with a build in PATA->SATA converter chip) it works just fine
>>no matter what I try.
>>
>>If however I use an older PATA drive and a certain PATA->SATA "dongle"
>>(in this case 1 out of 4 samples) I can reproduce the problem pretty
>>easily.
>>
>>This suggests to me that we are looking at a timing problem of sorts
>>the question is where.
>>
>>I'll work on the problem as time permits...
>>
>>-S=F8ren
>>_______________________________________________
>>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"
>_______________________________________________
>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?5.2.1.1.2.20031005201310.011a2b08>