Call Trace errors after installing registration key?

[Chezro]

I was instructed by "Fix Common Problems" that I should upload my diag report and ask for help. Any idea what's the culprit here? Didn't get this error until upgrading my registration and updating some plugins.

tower-diagnostics-20170129-1331.zip

[John_M]

When you installed your paid-for Plus registration key the old Trial key remained on your USB stick because it wasn't automatically removed. It isn't really a problem but if you want to fix it simply delete the /boot/config/Trial.key file (which is the Trial.key file in the config folder on your USB stick).

 

The call traces look like a firmware problem. Maybe a BIOS update is needed.

 

Your CPU is overheating and throttling. You should check the fan is working and blow out any dust in the heatsink fins.

[Chezro]

Well, the cpu is new with a stock fan so I may just need to add an aftermarket solution  but that thing is dust free. It's just a tight squeeze for everything I have in a small antec 900 case in my closet.

 

Deleted the extra key(actually just backed it up and moved it).

 

Bios was recently upgraded on my mobo. I doubt there's an upgrade. Only thing I can think is I usually have a mouse and keyboard attached to the server and I removed them with the array powered on and a vm uses it. I'll have to test when I get back in.

 

 

On a side note.....how could you tell all that? I can read logs but I'm not sure where that specific info you got is located or how it's presented.

[John_M]

Ok, for the duplicate key issue, look at the system/folders.txt file in your diagnostics:

 

/boot/config

total 304

-rwxrwxrwx  1 root root  256 Jan 29 13:17 Plus.key

-rwxrwxrwx  1 root root  256 Jan 10 03:20 Trial.key

-rwxrwxrwx  1 root root 11963 Jan 29 13:24 disk.cfg

 

For the call traces, see logs/syslog.txt and search for "trace"

 

Jan 28 22:05:37 Tower kernel: DMAR: [Firmware Bug]: RMRR entry for device 04:00.0 is broken - applying workaround

Jan 28 22:05:37 Tower kernel: DMAR: No ATSR found

Jan 28 22:05:37 Tower kernel: DMAR: dmar0: Using Queued invalidation

Jan 28 22:05:37 Tower kernel: ------------[ cut here ]------------

Jan 28 22:05:37 Tower kernel: WARNING: CPU: 1 PID: 1 at mm/page_alloc.c:3011 __alloc_pages_nodemask+0x1a4/0x8ca()

Jan 28 22:05:37 Tower kernel: Modules linked in:

Jan 28 22:05:37 Tower kernel: CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.30-unRAID #2

Jan 28 22:05:37 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME Z270-AR, BIOS 0701 12/27/2016

Jan 28 22:05:37 Tower kernel: 0000000000000000 ffff88085aec7bc0 ffffffff8136f79f 0000000000000000

Jan 28 22:05:37 Tower kernel: 0000000000000bc3 ffff88085aec7bf8 ffffffff8104a4ab ffffffff810bfe7c

Jan 28 22:05:37 Tower kernel: 00000000024000c0 00000000024080c0 000000000000000e 000000000000000e

Jan 28 22:05:37 Tower kernel: Call Trace:

Jan 28 22:05:37 Tower kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e

 

Are you passing 04:00.0 through to a VM?

 

From system/lspci.txt:

 

04:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:2142]

Subsystem: ASUSTeK Computer Inc. Device [1043:8732]

Kernel driver in use: xhci_hcd

 

USB 3 adapter?

 

For the hot CPU, syslog.txt again:

 

Jan 28 23:10:53 Tower kernel: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)

Jan 28 23:10:53 Tower kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)

Jan 28 23:10:53 Tower kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)

Jan 28 23:10:53 Tower kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)

Jan 28 23:10:53 Tower kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)

Jan 28 23:10:53 Tower kernel: mce: [Hardware Error]: Machine check events logged

 

I missed the fact that the hardware is brand new and unlikely to be dusty  but the fan may be stalled or the heatsink not making good thermal contact.

 

[John_M]

I see the BIOS is recent and there isn't a newer one available yet (I've checked with Asus) but I trust there will be soon as this one has a lot of bugs.