Date: Thu, 01 Jan 2015 19:28:40 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-stable@freebsd.org Subject: Re: Creating a bootable ZFS disk? Message-ID: <54A59FE8.2070008@multiplay.co.uk> In-Reply-To: <18C4C5D1-04D8-46B3-9E6F-FDAEB49BED1A@tao.org.uk> References: <54a048f2.45c1c20a.6ffd.ffffe6d7SMTPIN_ADDED_BROKEN@mx.google.com> <54A062FE.6020500@multiplay.co.uk> <54A067D0.4050606@multiplay.co.uk> <349F0A87-5F85-4367-9A5C-E77DBFA16588@karthauser.co.uk> <7E1DA790-822F-4253-A3F6-1E5F5EFFEE04@karthauser.co.uk> <54A1129F.3040004@multiplay.co.uk> <C0A39010-8EBD-46C6-8AA5-B7970DF5280B@tao.org.uk> <54A18986.4000002@multiplay.co.uk> <5AFFE5CE-ABC7-4D9C-B8E7-0AC9C3327D6B@tao.org.uk> <54A2D3FA.6000404@multiplay.co.uk> <18C4C5D1-04D8-46B3-9E6F-FDAEB49BED1A@tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/01/2015 17:18, Dr Josef Karthauser wrote:
> On 30 Dec 2014, at 16:34, Steven Hartland <killing@multiplay.co.uk> wrote:
>> This is strengthened by the fact that ATI's previous generation HW (SB600) had MSI disabled by r245875 due to a very similar issue.
>>
>> So given all the evidence so far ahci.0.msi=1 may well be the fix.
>>
> Is there any benefit to also trying with mdi > 1 < 8?
Nope as the ahci(4) details there's only 3 settings:
0 = MSI disabled
1 = Single MSI vector used, if supported
2 = Multiple MSI vectors used, if supported (default)
If setting it to 1 does fix it, I've got a patch which provides a quirk
we can use to make that the default for this HW.
Regards
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54A59FE8.2070008>