From nobody@FreeBSD.org  Wed May 26 17:23:31 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 11910106564A
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 May 2010 17:23:31 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id EB0A88FC14
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 May 2010 17:23:30 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o4QHNUD7033179
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 May 2010 17:23:30 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o4QHNUAf033161;
	Wed, 26 May 2010 17:23:30 GMT
	(envelope-from nobody)
Message-Id: <201005261723.o4QHNUAf033161@www.freebsd.org>
Date: Wed, 26 May 2010 17:23:30 GMT
From: Ryan Holt <ryan@ryanholt.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: AHCI not being enabled on PC
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         147086
>Category:       kern
>Synopsis:       AHCI not being enabled on PC
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 17:30:13 UTC 2010
>Closed-Date:    Thu Apr 28 19:03:40 UTC 2011
>Last-Modified:  Thu Apr 28 19:03:40 UTC 2011
>Originator:     Ryan Holt
>Release:        8.0-Stable-201004
>Organization:
>Environment:
FreeBSD fs.holthome.local 8.0-STABLE-201004 FreeBSD 8.0-STABLE-201004 #0: Mon Apr  5 15:59:06 UTC 2010     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Hello,

I've got a fresh install of FreeBSD 8.0-Stable-201004 built on a Gigabyte GA-K8U-754 Motherboard (http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=1876). The boot drives are plugged directly into the Motherboard's SATA ports, which I believe is powered by a ULi M1689 chipset. I also have a Supermicro AOC-SAT2-MV8 PCI-X HBA card (http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm) which has a Hercules-2 Rev. C0 SATA host controller built in. I've added ahci_load="YES" in my /boot/loader.conf and I can see that ahci.ko was loaded using klstat, but I do not see any drives appearing that use the ahci module. All drives are labeled /dev/ad* instead of /dev/ada* and hotswap doesn't work properly. Running dmesg |grep -i ahci comes back empty.
>How-To-Repeat:
1. Boot computer
2. Run dmesg |grep -i ahci
3. Unplug drive, watch PC kernel panic
>Fix:


>Release-Note:
>Audit-Trail:

From: Alexander Motin <mav@FreeBSD.org>
To: Ryan Holt <ryan@ryanholt.net>
Cc: Garrett Cooper <yanefbsd@gmail.com>, bug-followup@freebsd.org
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 21:38:20 +0300

 Ryan Holt wrote:
 >> I've got a fresh install of FreeBSD 8.0-Stable-201004 built on a Gigabyte GA-K8U-754 Motherboard. The boot drives are plugged directly into the Motherboard's SATA ports, which I believe is powered by a ULi M1689 chipset. I also have a Supermicro AOC-SAT2-MV8 PCI-X HBA card which has a Hercules-2 Rev. C0 SATA host controller built in. I've added ahci_load="YES" in my /boot/loader.conf and I can see that ahci.ko was loaded using klstat, but I do not see any drives appearing that use the ahci module. All d rives are labeled /dev/ad* instead of /dev/ada* and hotswap doesn't work properly. Running dmesg |grep -i ahci comes back empty.
 
 I can't say about ULi SATA - I haven't tried any of them. Make sure that
 you have AHCI mode enabled in BIOS. ahci(4) driver should attach to any
 hardware that reporting AHCI compatibility via PCI class/subclass.
 
 Supermicro AOC-SAT2-MV8 - is not AHCI compatible. New driver for it
 named mvs(4). It was merged to 8-STABLE just a few weeks ago. You may
 update your system and try it.
 
 -- 
 Alexander Motin

Date: Wed, 26 May 2010 10:48:21 -0700
From: Garrett Cooper <yanefbsd@gmail.com>
To: Ryan Holt <ryan@ryanholt.net>
Subject: Re: kern/147086: AHCI not being enabled on PC

 Hi Ryan,
     A few requests:
     1. Can you please try a CURRENT CD to see if the drives detect and
 attach themselves to ahci(4) properly?
     2. Could you please provide us with the device IDs for the controller?
 Thanks!
 -Garrett

From: "ryan@ryanholt.net" <ryan@ryanholt.net>
To: Garrett Cooper <yanefbsd@gmail.com>
Cc: Alexander Motin <mav@freebsd.org>, bug-followup@freebsd.org
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 14:56:37 -0400 (EDT)

 ------=_Part_46482_1005083949.1274900197056
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Hi Garrett,
 =C2=A0
 How can I get the device IDs? pciconf?
 =C2=A0
 
 [root@fs /usr/src]# pciconf -lv
 hostb0@pci0:0:0:0: =C2=A0 =C2=A0 =C2=A0class=3D0x060000 card=3D0x50001458 c=
 hip=3D0x168910b9 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ULi M1689 K8 Northbridge with =
 AGP and hypertransport'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 pcib1@pci0:0:1:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060400 card=3D0x00000000 c=
 hip=3D0x524610b9 rev=3D0x00
 hdr=3D0x01
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ULi AGP 3.0 Controller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-PCI
 pcib2@pci0:0:2:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060401 card=3D0x00000000 c=
 hip=3D0x524910b9 rev=3D0x00
 hdr=3D0x01
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'HyperTransport to PCI Bridge (=
 M5249)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-PCI
 isab0@pci0:0:3:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060100 card=3D0x50011458 c=
 hip=3D0x156310b9 rev=3D0x70
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ALI M1563 South Bridge with Hy=
 pertransport Support'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-ISA
 none0@pci0:0:3:1: =C2=A0 =C2=A0 =C2=A0 class=3D0x068000 card=3D0x50031458 c=
 hip=3D0x710110b9 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ALI M7101 Power Management Con=
 troller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 none1@pci0:0:4:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x040100 card=3D0xae011458 c=
 hip=3D0x545510b9 rev=3D0x20
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'AC'97 Audio Controller (M1563M=
  Southbridge)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D multimedia
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D audio
 atapci0@pci0:0:14:0: =C2=A0 =C2=A0class=3D0x0101fa card=3D0x50021458 chip=
 =3D0x522910b9 rev=3D0xc7
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'EIDE Controller (M5229 Southbr=
 idge)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D mass storage
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ATA
 atapci1@pci0:0:14:1: =C2=A0 =C2=A0class=3D0x01018f card=3D0xb0031458 chip=
 =3D0x528910b9 rev=3D0x10
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'M5289 SATA/Raid controller (UL=
 I M1567/M1689 )'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D mass storage
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ATA
 ohci0@pci0:0:15:0: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 ohci1@pci0:0:15:1: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 ohci2@pci0:0:15:2: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 ehci0@pci0:0:15:3: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0320 card=3D0x50041458 c=
 hip=3D0x523910b9 rev=3D0x01
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'USB EHCI2.0 Controller (527210=
 B9)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 hostb1@pci0:0:24:0: =C2=A0 =C2=A0 class=3D0x060000 card=3D0x00000000 chip=
 =3D0x11001022 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Advanced Micro Devices (AMD)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Athlon64/Opteron/Sempron (K8 F=
 amily) HyperTransport Technology
 Configuration'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 hostb2@pci0:0:24:1: =C2=A0 =C2=A0 class=3D0x060000 card=3D0x00000000 chip=
 =3D0x11011022 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Advanced Micro Devices (AMD)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Athlon64/Opteron/Sempron (K8 F=
 amily) Address Map'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 hostb3@pci0:0:24:2: =C2=A0 =C2=A0 class=3D0x060000 card=3D0x00000000 chip=
 =3D0x11021022 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Advanced Micro Devices (AMD)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Athlon64/Opteron/Sempron (K8 F=
 amily) DRAM Controller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 hostb4@pci0:0:24:3: =C2=A0 =C2=A0 class=3D0x060000 card=3D0x00000000 chip=
 =3D0x11031022 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Advanced Micro Devices (AMD)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Athlon64/Opteron/Sempron (K8 F=
 amily) Miscellaneous Control'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 vgapci0@pci0:1:0:0: =C2=A0 =C2=A0 class=3D0x030000 card=3D0x00000000 chip=
 =3D0x011010de rev=3D0xa1
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Nvidia Corp'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'GeForce2 MX / MX 400 (NV11)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D display
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D VGA
 em0@pci0:2:6:0: class=3D0x020000 card=3D0x13768086 chip=3D0x107c8086 rev=3D=
 0x05 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Intel Corporation'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Gigabit Ethernet Controller (C=
 opper) rev 5 (82541PI)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D network
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ethernet
 hptrr0@pci0:2:8:0: =C2=A0 =C2=A0 =C2=A0class=3D0x010000 card=3D0x11ab11ab c=
 hip=3D0x608111ab rev=3D0x09
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Marvell Semiconductor (Was: Ga=
 lileo Technology Ltd)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'MV88SX6081 8-port SATA II PCI-=
 X Controller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D mass storage
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D SCSI
 rl0@pci0:2:10:0: =C2=A0 =C2=A0 =C2=A0 =C2=A0class=3D0x020000 card=3D0xe0001=
 458 chip=3D0x813910ec rev=3D0x10
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Realtek Semiconductor'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Realtek RTL8139 Family PCI Fas=
 t Ethernet NIC
 (RTL-8139/8139C/8139C)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D network
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ethernet
 
 
 =C2=A0
 Thanks,
 Ryan
 =C2=A0
 
 ------=_Part_46482_1005083949.1274900197056--

From: Alexander Motin <mav@FreeBSD.org>
To: "ryan@ryanholt.net" <ryan@ryanholt.net>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 22:10:41 +0300

 ryan@ryanholt.net wrote:
 > Will the MVS driver allow for any type of hot swap? It appears that when
 > I pull the drive out of any slot on the Supermicro card the kernel will
 > panic and system crash. Same thing with the on-board controller.
 
 mvs(4) provides almost the same set of features that ahci(4), just for
 different hardware. Hot swap should work fine.
 
 -- 
 Alexander Motin

From: "ryan@ryanholt.net" <ryan@ryanholt.net>
To: Alexander Motin <mav@FreeBSD.org>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 14:59:16 -0400 (EDT)

 ------=_Part_46572_388073361.1274900356733
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 I'm assuming that the ULi doesn't have AHCI support as there's no option in=
  the
 BIOS for AHCI, only IDE and RAID.
 =C2=A0
 Will the MVS driver allow for any type of hot swap? It appears that when I =
 pull
 the drive out of any slot on the Supermicro card the kernel will panic and
 system crash. Same thing with the on-board controller.
 =C2=A0
 Thanks,
 Ryan
 =C2=A0
 
 ------=_Part_46572_388073361.1274900356733--

From: "ryan@ryanholt.net" <ryan@ryanholt.net>
To: Alexander Motin <mav@FreeBSD.org>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 15:19:11 -0400 (EDT)

 ------=_Part_47294_804650099.1274901551988
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 OK Great. Should I re-compile my kernel with mvs as a device option?
 =C2=A0
 Thanks,
 Ryan
 =C2=A0
 
 ------=_Part_47294_804650099.1274901551988--

From: Alexander Motin <mav@FreeBSD.org>
To: "ryan@ryanholt.net" <ryan@ryanholt.net>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 22:20:57 +0300

 ryan@ryanholt.net wrote:
 > OK Great. Should I re-compile my kernel with mvs as a device option?
 
 As you wish. Module should also be fine.
 
 -- 
 Alexander Motin

From: "ryan@ryanholt.net" <ryan@ryanholt.net>
To: Alexander Motin <mav@FreeBSD.org>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Thu, 27 May 2010 09:55:56 -0400 (EDT)

 ------=_Part_64910_1088933982.1274968556941
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 OK I got mvs compiled and the drives are using it now. Tested hot swap; rem=
 oved
 and replaced drives while writing data to the ZFS pool sitting atop. One is=
 sue I
 noticed is that the glabels don't seem to be read once I insert the disk ba=
 ck
 into the server. Seems like I need to re-label the drive and then replace i=
 t
 back into the zpool using zpool replace. Would this be an issue with ZFS an=
 d not
 the mvs driver?
 =C2=A0
 Additionally, this might be a cabling issue or an issue with my drive cage,=
  but
 when I place a disk in slot 0 (port 0 on AOC-SAT2-MV8) I get mvsch0 timeout
 errors and the whole box locks up requiring a hard reboot. Placing the driv=
 e in
 slot 4 and utilizing slots 2-5 instead of 1-4 allows the server to boot up =
 fine
 / run fine.
 =C2=A0
 Also, the drive pool seems a bit slow. Using the command...
 =C2=A0
 dd if=3D/dev/urandom (and /dev/zero) of=3D/tank/test.file bs=3D1024 count=
 =3D102400=C2=A0
 =C2=A0
 Seems to indicate that I get somwhere between 15MB/sec (urandom) and 30 mb/=
 sec
 (zero). This card is on a PCI bus and therefore will be somewhat restricted=
 , but
 should it be reasonable to expect better performance than this out of a 4 d=
 isk
 Hitachi 1TB 7200 RPM 32mb cache raidz1 pool? Are there any other recommende=
 d
 tests to benchmark performance?
 =C2=A0
 Thanks again for all your help!
 Ryan
 =C2=A0
 
 On May 26, 2010 at 7:20 PM Alexander Motin <mav@FreeBSD.org> wrote:
 
 > ryan@ryanholt.net wrote:
 > > OK Great. Should I re-compile my kernel with mvs as a device option?
 >
 > As you wish. Module should also be fine.
 >
 > --
 > Alexander Motin
 ------=_Part_64910_1088933982.1274968556941
 MIME-Version: 1.0
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
     <title></title>
   </head>
 
   <body>
     <p style="margin: 0px;">OK I got mvs compiled and the drives are using it now. Tested hot swap; removed and replaced drives while writing data to the ZFS pool sitting atop. One issue I noticed is that the glabels don&#39;t seem to be read once I insert the disk back into the server. Seems like I need to re-label the drive and then replace it back into the zpool using zpool replace. Would this be an issue with ZFS and not the mvs driver?<span></span></p>
 
     <p style="margin: 0px;">&#160;</p>
 
     <p style="margin: 0px;">Additionally, this might be a cabling issue or an issue with my drive cage, but when I place a disk in slot 0 (port 0 on AOC-SAT2-MV8) I get mvsch0 timeout errors and the whole box locks up requiring a hard reboot. Placing the drive in slot 4 and utilizing slots 2-5 instead of 1-4 allows the server to boot up fine / run fine.</p>
 
     <p style="margin: 0px;">&#160;</p>
 
     <p style="margin: 0px;">Also, the drive pool seems a bit slow. Using the command...</p>
 
     <p style="margin: 0px;">&#160;</p>
 
     <p style="margin: 0px;">dd if=/dev/urandom (and /dev/zero) of=/tank/test.file bs=1024 count=102400&#160;</p>
 
     <p style="margin: 0px;">&#160;</p>
 
     <p style="margin: 0px;">Seems to indicate that I get somwhere between 15MB/sec (urandom) and 30 mb/sec (zero). This card is on a PCI bus and therefore will be somewhat restricted, but should it be reasonable to expect better performance than this out of a 4 disk Hitachi 1TB 7200 RPM 32mb cache raidz1 pool? Are there any other recommended tests to benchmark performance?</p>
 
     <p style="margin: 0px;">&#160;</p>
 
     <p style="margin: 0px;">Thanks again for all your help!</p>
 
     <p style="margin: 0px;">Ryan</p>
 
     <p>&#160;</p>
 
     <div style="margin: 5px 0px 5px 0px; font-family: monospace;">
       On May 26, 2010 at 7:20 PM Alexander Motin &lt;mav@FreeBSD.org&gt; wrote:<br />
       <br />
       &gt; ryan@ryanholt.net wrote:<br />
       &gt; &gt; OK Great. Should I re-compile my kernel with mvs as a device option?<br />
       &gt;<br />
       &gt; As you wish. Module should also be fine.<br />
       &gt;<br />
       &gt; --<br />
       &gt; Alexander Motin<br />
     </div>
   </body>
 </html>
 
 ------=_Part_64910_1088933982.1274968556941--

From: Alexander Motin <mav@FreeBSD.org>
To: "ryan@ryanholt.net" <ryan@ryanholt.net>
Cc: bug-followup@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Thu, 27 May 2010 22:35:37 +0300

 ryan@ryanholt.net wrote:
 > OK I got mvs compiled and the drives are using it now. Tested hot swap;
 > removed and replaced drives while writing data to the ZFS pool sitting
 > atop. One issue I noticed is that the glabels don't seem to be read once
 > I insert the disk back into the server. Seems like I need to re-label
 > the drive and then replace it back into the zpool using zpool replace.
 > Would this be an issue with ZFS and not the mvs driver?
 
 I don't think it is driver related.
 
 > Additionally, this might be a cabling issue or an issue with my drive
 > cage, but when I place a disk in slot 0 (port 0 on AOC-SAT2-MV8) I get
 > mvsch0 timeout errors and the whole box locks up requiring a hard
 > reboot. Placing the drive in slot 4 and utilizing slots 2-5 instead of
 > 1-4 allows the server to boot up fine / run fine.
 
 I need more info to say something. Boot with verbose messages and send
 be complete log from boot messages up to the error.
 
 > Also, the drive pool seems a bit slow. Using the command...
 > 
 > dd if=/dev/urandom (and /dev/zero) of=/tank/test.file bs=1024 count=102400 
 > 
 > Seems to indicate that I get somwhere between 15MB/sec (urandom) and 30
 > mb/sec (zero). This card is on a PCI bus and therefore will be somewhat
 > restricted, but should it be reasonable to expect better performance
 > than this out of a 4 disk Hitachi 1TB 7200 RPM 32mb cache raidz1 pool?
 > Are there any other recommended tests to benchmark performance?
 
 If your card placed into regular PCI slot - absolute maximum you can get
 from it is 133MB/s, but usually practical limit is lower. When you are
 writing to redundant array, like raidz, same data written to several
 devices same time. It also divides effective bandwidth by several times,
 proportionally to redundancy. So even if 30MB/s a bit small, it is
 possible in such configuration.
 
 Also it is a bit strange to test linear bandwidth, using 1K blocks.
 System I/O overhead may also affect result. Try it with at least 64K
 block to be sure.
 
 /dev/urandom may also affect performance. On my machine I can read only
 about 60MB/s from it, so it is not a good test.
 
 Also, depending on your typical workload you may be interested in random
 I/O performance. 4 disks with NCQ supported by mvs(4) should handle
 random parallel load quite fine.
 
 -- 
 Alexander Motin
State-Changed-From-To: open->closed 
State-Changed-By: mav 
State-Changed-When: Thu Apr 28 19:03:04 UTC 2011 
State-Changed-Why:  
Original problem solved, secondary - no response. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=147086 
>Unformatted:
