This is weird.
I have a brand spanking new mobo: 890GPA-UD3H Gigabyte Rev3.1
The MOBO has the capability of presenting an IDE or AHCI interface for SATA.
I had the MOBO on IDE and suddenly, during a heavy session of data migration I started getting an error about AHCI on some port timing out.
When I went to shutdown, I got the dreaded "ps axl advised" message.
My guess is that the AHCI driver got stuck in some sort of loop and it would not terminate.
Now, the weird thing is that, as I pointed out above, the MOBO was in IDE, not AHCI.
I guess this is yet another poor implementation in nanobsd....
I have a brand spanking new mobo: 890GPA-UD3H Gigabyte Rev3.1
The MOBO has the capability of presenting an IDE or AHCI interface for SATA.
I had the MOBO on IDE and suddenly, during a heavy session of data migration I started getting an error about AHCI on some port timing out.
When I went to shutdown, I got the dreaded "ps axl advised" message.
My guess is that the AHCI driver got stuck in some sort of loop and it would not terminate.
Now, the weird thing is that, as I pointed out above, the MOBO was in IDE, not AHCI.
I guess this is yet another poor implementation in nanobsd....
