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
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
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
It seems Joe Marcus Clarke wrote:
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
