Latest update -> kernel panic

[BloodyIron]

Hi,

I recently updated two nodes in my cluster to the latest (as of a day or two ago?) kernel and other packages. One of the nodes is just fine, the other panics regularly when I start putting load on it.

I'm not sure how to get the panic records to you, as I am scrambling to get my environment back up and running, but I'll do what I can with some instruction.

Each of my nodes runs on a FX-8320 CPU, and M5A78L-M/USB3 motherboards. I recently added more RAM to each node, however I have ran memtest against the problematic node for 10hrs and saw no problems.

If anyone can advise on this that would be great, but I don't plan to use this second node until I see the next kernel in the update stream.

 

[e100]

Passing memtest only means that memtest did not detect an issue.
So don't assume the RAM is good just because memtest failed to detect an issue.

You need to get the kernel messages that are causing the panic, that will guide you in the right direction.
The easiest way is to setup a serial console on the problem server then setup a serial logger on another server and connect them with a serial cable.
When the panic occurs you will capture all of the output from the kernel as to what went wrong.
Post that here and hopefully someone can help you decipher it.

 

[danielmash]

I Agree. I've seen so many issues just because of wrong type memory.

Simply swapping memory between two hosts solved problem for me.

Or in some cases buying brand new memory sticks of different brand/suplier.

Please post dump here. Might be there is something interesting.