I fixed this recently.
On Mon, Jun 10, 2013 at 11:13:22PM -0400, Thor Lancelot Simon wrote: > On Mon, Jun 10, 2013 at 11:00:05PM -0400, Thor Lancelot Simon wrote: > > I powered back up a machine that very, very long ago was build.netbsd.org, > > to run some tests. It worked fine with its old (5.99) kernel, but with a > > kernel built from yesterday's sources, its disks vanished, evidently > > because: > > > > siisata0 at pci1 dev 5 function 0: vendor 0x1095 product 0x3114 (rev. 0x02) > > siisata0: couldn't map global registers > > It looks like the cause of this is that siisata is trying to use the > SiI3114 in this system, with which it is (as far as I know) not compatible. > > With "no siisata" in the kernel config file, things are much better: > > satalink0 at pci1 dev 5 function 0: Silicon Image SATALink 3114 (rev. 0x02) > satalink0: 33MHz PCI bus > satalink0: bus-master DMA support present > satalink0: using ioapic0 pin 19 for native-PCI interrupt > atabus0 at satalink0 channel 0 > atabus1 at satalink0 channel 1 > atabus2 at satalink0 channel 2 > atabus3 at satalink0 channel 3 > satalink0: port 0: device present, speed: 1.5Gb/s > satalink0: port 1: device present, speed: 1.5Gb/s > wd0(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA) > wd1(satalink0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA) >
