On Wed, Feb 1, 2017 at 6:28 AM, Jonathan Matthew <[email protected]> wrote:
> On Wed, Feb 01, 2017 at 04:16:34AM -0500, Sanka Coffie wrote:
> > Here is the output of dmesg with debugging enabled on ahci, running with
> > -current that I pulled down a few hours ago. The line matches up with the
> > driver which is an improvement.
>
> OK, that looks like the mechanism for determining which NCQ command failed
> is failing, so let's see what happens if we turn NCQ off. Does this diff
> change anything?
>
>
> Index: ahci_pci.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/ahci_pci.c,v
> retrieving revision 1.12
> diff -u -p -u -p -r1.12 ahci_pci.c
> --- ahci_pci.c 14 Jan 2016 04:06:53 -0000 1.12
> +++ ahci_pci.c 1 Feb 2017 11:26:01 -0000
> @@ -281,7 +281,7 @@ ahci_amd_hudson2_attach(struct ahci_soft
> {
> ahci_ati_sb_idetoahci(sc, pa);
>
> - sc->sc_flags |= AHCI_F_IPMS_PROBE;
> + sc->sc_flags |= AHCI_F_IPMS_PROBE | AHCI_F_NO_NCQ;
>
> return (0);
> }
>
>
Yep, just installed with that change and no more kernel panic. I was also
able to reboot, as well as run df and ls on the 2nd drive without issue.
