Ruslan Ermilov wrote: > On Fri, Dec 24, 2004 at 05:22:52PM +0100, S?ren Schmidt wrote: > >>OK, saw this thread a little late, but I committed some updates to this >>area earlier today, let me know if that changes anything... >> > Unfortunately not. With > > $FreeBSD: src/sys/dev/ata/ata-chipset.c,v 1.97 2004/12/24 13:36:04 sos Exp $ > $FreeBSD: src/sys/dev/ata/ata-lowlevel.c,v 1.51 2004/12/24 13:38:25 sos Exp $ > > I still get, > > atapci0: <nVidia nForce3 UDMA133 controller> port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > atapci1: <Promise PDC20378 SATA150 controller> port 0xd000-0xd07f,0xd400-0xd40f,0xd800-0xd83f mem 0xfc960000-0xfc97ffff,0xfc99f000-0xfc99ffff irq 5 at device 8.0 on pci1 > atapci1: failed: rid 0x20 is memory, requested 4 > ata2: channel #0 on atapci1 > ata3: channel #1 on atapci1 > ata4: channel #2 on atapci1 > ad0: 76319MB <ST380011A/3.04> [155061/16/63] at ata0-master UDMA100 > ata1-slave: DMA limited to UDMA33, non-ATA66 cable or device > acd0: CDRW <COM4824/VER 1.01> at ata1-slave UDMA33 > ata4-master: FAILURE - ATA_IDENTIFY timed out > ata4-master: FAILURE - ATA_IDENTIFY timed out > ata4-master: FAILURE - ATA_IDENTIFY timed out > > followed by the instant panic. The panic message and traceback would be helpfull, as I have a semilar setup here that works "just fine" (tm)... -- -SørenReceived on Fri Dec 24 2004 - 21:45:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC