Server hung, is this a stack trace?

Hi everyone,

Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:

RIP: 0010:[<ffffffff8006b981>]  [<ffffffff8006b981>] mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40  EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000010
RBP: 134d6ef57a8e3fe8 R08: 0000000000000033 R09: 0000000000000033
R10: ffff810001005710 R11: ffffffff8014c2c9 R12: 0000000000000000
R13: ffff810c20075800 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff80425000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00000000f7fb6980 CR3: 0000000c016ba000 CR4: 00000000000006e0
Process swapper (pid: 0, threadinfo ffffffff80456000, task ffffffff80310b60)
Stack:  ffffffff801a1337 0000000000000000 000000000000039c 0000000000000000
 000000000000039c 0000000000000000 ffffffff801a11e1 0000000000090000
 0000000000000000 0000000000000000 ffffffff800492fd 0000000000200800
Call Trace:
 [<ffffffff801a1337>] acpi_processor_idle_simple+0x156/0x316
 [<ffffffff801a11e1>] acpi_processor_idle_simple+0x0/0x316
 [<ffffffff800492fd>] cpu_idle+0x95/0xb8
 [<ffffffff80461807>] start_kernel+0x220/0x225
 [<ffffffff8046122f>] _sinittext+0x22f/0x236


Code: c3 41 57 41 56 49 89 f6 41 55 49 89 fd 41 54 4c 8d a7 e0 02

I had to reset the server, as I couldnt ping, or get a prompt, and the above is pretty much all we have to go on. I can't find anything meaningful in /var/log/messages or dmesg. Any ideas what the above output is, or what it indicates?

Many thanks.

It is a crash inside the kernel. Kernel errors can't be saved to any log files, because the kernel's help is needed to save files.

I don't see anything useful in the error unfortunately. It looks like it happened while the CPU was idle.

Thanks Corona,

This is the second time this has occured. The first time HP ASR reset the server, we then disabled ASR hoping that next time around we would be able to get some meaningful messages before resetting the server.

I don' think there's much we can do besides a total blind firmware/patch update (which won't happen!).

Or kernel upgrade?

I am experienced the same issue at the moment. Did you resolve this problem? and what was the fix?

We didn't resolve it really. A kernel upgrade didn't help. Red Hat & HP couldn't tell us what was wrong. So we swapped out all the internals with another spare development server we had (kept the internal disks the same) - since then it has functioned ok.

I can only guess that reseating a bit of hardware resolved the issue.

Hello, we have some type of issue for HP server.
Can you said which model do you use?
We have issue with HP DL360p G8. Thank you.