On Oct 10, 1:00pm, Michael van Elst wrote:
} pet...@nordu.net (Fredrik Pettai) writes:
}
} >Begin forwarded message:
} >>
} >> http://phoronix.com/scan.php?page=news_item&px=BSD-Linux-Late-2015
}
} >The installation of NetBSD 7.0 didnt work smooth for the author of this
article,
} >and the same happened for another sysadmin I know.
} >Someone should have a look at this to see if this could be fixed.
}
} This here doesn't look like it can be fixed quickly.
}
} The TSC code has issues with the Haswell-EP, maybe harmless.
}
} USB failed completely, maybe interrupt routing or conflicting USB3 that we
} don't see on the screen.
}
} A wd device is found but cannot be accessed, that might even not be
} the system disk. If that's server hardware (and Haswell-EP tells this)
} then it probably has some RAID controller that we don't even
} recognize.
We can't see the whole dmesg, and the author of the phoronix
article doesn't appear to be interested in figuring out the issue,
but the problem appears to be PR/50030, PR/50029, PR/49448, and
probably other related ones.
I thought I had commented on at least one of the PRs, but
maybe I didn't attach my comment to a PR. However, I'm seeing the
WDCTL_RESET issue on my Asus Z97-C (Intel Z97 chipset) motherboard
with Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz processor (Haswell).
This seems to be a generic problem with the ahci_sata driver.
}-- End of excerpt from Michael van Elst
