Date: Mon, 7 Sep 2015 20:04:54 -0600 From: Scott Long <scottl@samsco.org> To: "Bradley W. Dutton" <brad-fbsd-stable@duttonbros.com> Cc: freebsd-stable@freebsd.org Subject: Re: ISCI bus_alloc_resource failed Message-ID: <514DD6B2-EBC3-43F7-8C2A-F8A1C77463F0@samsco.org> In-Reply-To: <20150907103435.Horde.z4GgTZD3-chqVxPgZhMklyM@duttonbros.com> References: <20150907103435.Horde.z4GgTZD3-chqVxPgZhMklyM@duttonbros.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is really weird. According to what you=E2=80=99ve posted, it=E2=80=99= s advertising itself as an SMBus controller with no BARs. Maybe = you=E2=80=99re passing through the wrong device, or someone added the = wrong PCI device id data to the driver? Scott > On Sep 7, 2015, at 11:34 AM, Bradley W. Dutton = <brad-fbsd-stable@duttonbros.com> wrote: >=20 > Hi, >=20 > I'm having trouble with the isci driver in both stable and current. I = see the following dmesg in stable: >=20 > isci0: <Intel(R) C600 Series Chipset SAS Controller (SATA mode)> port = 0x5000-0x50ff mem 0xe7afc000-0xe7afffff,0xe7400000-0xe77fffff irq 19 at = device 0.0 on pci11 > isci: 1:000051 ISCI bus_alloc_resource failed >=20 >=20 > I'm running FreeBSD on VMWare ESXi 6 with vt-d passthrough of the isci = devices, here is the relevant pciconf output: >=20 > none2@pci0:3:0:0: class=3D0x0c0500 card=3D0x062815d9 = chip=3D0x1d708086 rev=3D0x06 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'C600/X79 series chipset SMBus Controller 0' > class =3D serial bus > subclass =3D SMBus > cap 10[90] =3D PCI-Express 2 endpoint max data 128(128) link = x32(x32) > speed 5.0(5.0) ASPM disabled(L0s) > cap 01[cc] =3D powerspec 3 supports D0 D3 current D0 > cap 05[d4] =3D MSI supports 1 message > ecap 000e[100] =3D ARI 1 > isci0@pci0:11:0:0: class=3D0x010700 card=3D0x062815d9 = chip=3D0x1d6b8086 rev=3D0x06 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'C602 chipset 4-Port SATA Storage Control Unit' > class =3D mass storage > subclass =3D SAS > cap 01[98] =3D powerspec 3 supports D0 D3 current D0 > cap 10[c4] =3D PCI-Express 2 endpoint max data 128(128) link = x32(x32) > speed 5.0(5.0) ASPM disabled(L0s) > cap 11[a0] =3D MSI-X supports 2 messages > Table in map 0x10[0x2000], PBA in map 0x10[0x3000] > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 1 corrected > ecap 000e[138] =3D ARI 1 > ecap 0017[180] =3D TPH Requester 1 > ecap 0010[140] =3D SRIOV 1 >=20 >=20 > I haven't tried booting on bare metal but running a linux distro = (centos 7) in the same VM works without issue. Is is possible the SRIOV = option is causing trouble? I don't see a BIOS option to disable that = setting on this server like I have on some others. Any other ideas to = get this working? >=20 > Thanks, > Brad >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?514DD6B2-EBC3-43F7-8C2A-F8A1C77463F0>