On Fri, Dec 24, 2004 at 02:14:12AM +0100, Daniel Eriksson wrote: > Ruslan Ermilov wrote: > > > Finally, I had time today to track it down to a single > > commit. So, the following change breaks my Promise > > SATA150 controller: > > I'm running a Promise SATA150 TX4 on a recent 6-CURRENT > (2004.12.20.16.00.00) machine without any problems. I only have 3 discs > hooked up to it though (plus 2 more on the on-board VIA SATA controller). > Also, I had some problems with ACPI and ATA/SATA on this machine after the > last big commit (a few weeks ago) so I turned it off. You might want to try > that if you haven't already. The machine is head-less, so I haven't tried > re-enabling ACPI since then. > Nope, turning ACPI off doesn't make any difference except for assigning a different IRQ: : 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: <Promise PDC20378 SATA150 controller> port 0xd000-0xd07f,0xd400-0xd40f,0xd800-0xd83f mem 0xfc960000-0xfc97ffff,0xfc99f000-0xfc99ffff irq 11 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 Besides, I love my ACPI, and it's a clear regression -- if I revert this commit, it all works again. Cheers, -- Ruslan Ermilov ru_at_FreeBSD.org FreeBSD committer
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC