Call trace - v6.4

[dadarara]

installed clean server  v6.4.  precleared all the HDs before using

created new VMs and also used some existing vdisk files.

it was running for 2 days now

was in the middle of using Krusader comparing some directories, when was hit by a call trace.

one of the VMs (OSX Sierra) crashed. others are ok.

 

hope someone can look into this. 

thanks

tower-diagnostics-20180130-1458.zip

[dadarara]

anyone ? pls

[dadarara]

pls help me to analyze the diagnostics file

[JorgeB]

Syslog is filled with these:

 

Jan 30 04:31:22 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0.
Jan 30 04:31:22 Tower kernel: Do you have a strange power saving mode enabled?
Jan 30 04:31:22 Tower kernel: Dazed and confused, but trying to continue
Jan 30 04:31:22 Tower kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0.
Jan 30 04:31:22 Tower kernel: Do you have a strange power saving mode enabled?
Jan 30 04:31:22 Tower kernel: Dazed and confused, but trying to continue
Jan 30 04:31:22 Tower kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0.
Jan 30 04:31:22 Tower kernel: Do you have a strange power saving mode enabled?
Jan 30 04:31:22 Tower kernel: Dazed and confused, but trying to continue

These are likely hardware related, possibly a power supply problem.

[dadarara]

thanks Johnnie

I have Platinum rated PSU 1600W . and anything possible 

I wonder if such an error can be a result of SW glitch as well?

 

[wayner]

Nice to see some Led Zep in the unRAID error messages!