Re: port-amd64/52596

[Dominik Bialy <dmb%yenn.ulegend.net@localhost>]

On Tue, Oct 10, 2017 at 08:50:01PM +0000, coypu%sdf.org@localhost wrote:
> The following reply was made to PR port-amd64/52596; it has been noted by GNATS.
> 
> From: coypu%sdf.org@localhost
> To: gnats-bugs%netbsd.org@localhost
> Cc: 
> Subject: Re: port-amd64/52596
> Date: Tue, 10 Oct 2017 20:48:28 +0000
> 
>  Hi,
>  
>  NetBSD should be doing the following thing almost constantly:
>  if (x86_xsave_features != 0) {
>  	xsave()
>  
>  which for your machine can be read as:
>  if (x86_xsave_features != 0) {
>  	panic("complain about xsave")
>  
>  x86_xsave_features is only written to at boot.
>  If it doesn't panic instantly, something is likely corrupting its value.
>  
>  The ACPI functions are unrelated, it's silly about what the last
>  function it prints at a backtrace is (it's after vpanic).
>  
>  With DEBUG/DIAGNOSTIC and some other options you might have a chance of
>  tracking down the cause too
>  
>  can you share a kernel that caused this panic?
>  

https://yenn.ulegend.net/~dmb/crash/

But just now I've noticed in the dmesg:

WARNING: 2 errors while detecting hardware; check system log.

so might be that something is dying in the hardware...

Also, the panic in the dmesg (from today) is unrelated,
as it was after applying the patch from this PR --
the load was increasing for a few hours until like 250,
and then that panic happened.

Hardware problem is possible, but it would be a funny
coincidence, since it started at the time of the upgrade
from NetBSD 6 to NetBSD 8.

I'll bring it down tomorrow and run memtest86+

Dominik