On Wed, 2003-11-26 at 13:28, Soren Schmidt wrote:
> It seems Joe Marcus Clarke wrote:
> > atapci1: <SiI 3112 SATA150 controller> port
> > 0x14b0-0x14bf,0x14c0-0x14c3,0x14c8-0x14cf,0x14c4-0x14c7,0x14d0-0x14d7
> > mem 0xe800a000-0xe800a1ff irq 9 at device 16.0 on pci0
> > GEOM: create disk ad4 dp=0xc5246460
> > ad4: 78167MB <Maxtor 6Y080M0> [158816/16/63] at ata2-master UDMA133
> > 
> > Nothing else was changed in the machine except the specific version of
> > -CURRENT since the time things worked and now.  In addition to replacing
> > the drive, I have replaced the SATA cable as well.  My plan is to revert
> > the ATA drivers to two weeks ago, and see if the problem persists. 
> > Failing that, I will test to see if this is a cooling problem.  Failing
> > that, I will replace the SATA controller.  However, I wanted to know if
> > I'm barking up the wrong tree, and perhaps this is a software issue. 
> 
> There are some early issues of the SiI3112 chips that has problems that
> can cause datacorruption etc etc..
> You can try the following patch (which btw re@ has for approval), 
> otherwise I'd try another controller as there seem to be no end of the
> troubles with the Sii 3112 chips (brings back to mind the horror times
> from when they where called CMD and did the CMD640 disaster)...

Thanks, but this patch immediately causes an Input/Output error trying
to do a large rm.  A few seconds later, and the machine is locked up
(probably spewing the same DMA timeouts, but I won't be able to check
until I get back home).

Joe

[ATA patch elided]
-- 
PGP Key : http://www.marcuscom.com/pgp.asc


Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to