Re: kern/38056: ahcisata fails to attach with a ServerWorks HT-1000 SATA

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

The following reply was made to PR kern/38056; it has been noted by GNATS.

From: jnemeth%victoria.tc.ca@localhost (John Nemeth)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%NetBSD.org@localhost, 
gnats-admin%NetBSD.org@localhost,
        netbsd-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/38056: ahcisata fails to attach with a ServerWorks HT-1000 
SATA
Date: Mon, 18 Feb 2008 16:43:15 -0800

 On Jun 5,  4:07am, Simon Burge wrote:
 }
 } >Number:         38056
 } >Synopsis:       ahcisata fails to attach with a ServerWorks HT-1000 SATA
 } >Arrival-Date:   Mon Feb 18 16:00:00 +0000 2008
 } >Originator:     Simon Burge
 } >Release:        NetBSD 4.99.54
 } >Environment:
 } System: NetBSD opteron.thistledown.com.au 4.99.54 NetBSD 4.99.54 (GENERIC) 
#0: Sat Feb 16 08:50:17 PST 2008  
builds@wb28:/home/builds/ab/HEAD/amd64/200802160002Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/GENERIC
 amd64
 } Architecture: x86_64
 } Machine: amd64
 } >Description:
 }      Booting a -current kernel on a Tyan S3850 gives:
 } 
 }     ahcisata0 at pci1 dev 14 function 0: ServerWorks HT-1000 SATA
 }     ahcisata0: interrupting at irq 11
 }     ahcisata0: AHCI revision 0x0, 1 ports, 1 command slots, features 0x0
 }     atabus0 at ahcisata0 channel 0 
 }     ahcisata0: more ports than announced
 } 
 }      and then fails to attach.
 } 
 }      A netbsd-4 kernel doesn't attach ahcisata to this, even though
 }      the kernel config has achisata in it.  netbsd-4 attaches with:
 } 
 }     svwsata0 at pci1 dev 14 function 0
 }     svwsata0: ServerWorks HT-1000 SATA Controller (rev. 0x00)
 }     svwsata0: bus-master DMA support present
 }     svwsata0: using irq 11 for native-PCI interrupt
 }     svwsata0: primary channel wired to native-PCI mode
 }     atabus0 at svwsata0 channel 0
 }     svwsata0: secondary channel wired to native-PCI mode
 }     atabus1 at svwsata0 channel 1
 }     svwsata0: secondary channel wired to compatibility mode
 }     atabus2 at svwsata0 channel 2
 }     svwsata0: secondary channel configured to compatibility mode
 }     atabus3 at svwsata0 channel 3
 }     ...
 }     svwsata0 port 0: device present, speed: 1.5Gb/s
 }     wd0 at atabus0 drive 0: <FUJITSU MHT2080BH>
 }     wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 }     wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 
sectors
 }     wd0: 32-bit data port
 }     wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 }     wd0(svwsata0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using 
DMA)
 }     svwsata0 port 1: PHY offline
 }     svwsata0 port 2: PHY offline
 }     svwsata0 port 3: PHY offline 
 } 
 } >How-To-Repeat:
 }      Boot a -current kernel on a Tyan Tomcat K8SH (S3850) motherboard
 }      with a ServerWorks HT1000 SATA controller.
 } 
 } >Fix:
 }      None given.  A workaround is to just disable achisata(4) and fall
 }      back to the still working svwsata(4).
 
      In src/sys/dev/pci/svwsata.c in svwsata_match(), find the "return (2)"
 and make it "return (4)" so that svwsata(4) will take the controller in
 preference to ahcisata(4).  If you want, you can also KNF the file (it
 should really be "return 4").
 
 }-- End of excerpt from Simon Burge