My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
I've been trying to save the panic message with kdump, but am not sure how one can configure kdump to do this, if indeed that is possible.
Hi,
On Fri, Jan 01, 2016 at 11:53:51PM +0100, Timothy Murphy wrote:
My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
AMD Turion64 cpu? Could be related to: https://bugs.centos.org/view.php?id=9860 uptream at https://bugzilla.redhat.com/show_bug.cgi?id=1285235
Cheers
Tru
Tru Huynh wrote:
On Fri, Jan 01, 2016 at 11:53:51PM +0100, Timothy Murphy wrote:
My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
AMD Turion64 cpu? Could be related to: https://bugs.centos.org/view.php?id=9860 uptream at https://bugzilla.redhat.com/show_bug.cgi?id=1285235
Thank you very much. My HP MicroServer does indeed have an AMD Turion64 cpu, and the kernel crash-code listed in the bug you cite is exactly what I see.
Timothy Murphy wrote:
My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
AMD Turion64 cpu? Could be related to: https://bugs.centos.org/view.php?id=9860 uptream at https://bugzilla.redhat.com/show_bug.cgi?id=1285235
Thank you again. I followed a suggestion in this bug report, appending the line GRUB_CMDLINE_LINUX_DEFAULT="initcall_blacklist=clocksource_done_booting" to /etc/default/grub , and running # grub2-mkconfig > /boot/grub2/grub.cfg Now I could re-boot into CentOS-7.2 with kernel 3.10.0-327.3.1.el7.x86_64 .
Sorry to late response i wich you all a very happy and peaceful year think you so much i love you in god God bless you
2016-01-04 11:11 GMT+01:00 Timothy Murphy gayleard@eircom.net:
Timothy Murphy wrote:
My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
AMD Turion64 cpu? Could be related to: https://bugs.centos.org/view.php?id=9860 uptream at https://bugzilla.redhat.com/show_bug.cgi?id=1285235
Thank you again. I followed a suggestion in this bug report, appending the line GRUB_CMDLINE_LINUX_DEFAULT="initcall_blacklist=clocksource_done_booting" to /etc/default/grub , and running # grub2-mkconfig > /boot/grub2/grub.cfg Now I could re-boot into CentOS-7.2 with kernel 3.10.0-327.3.1.el7.x86_64 .
-- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Sorry to late response i wich you all a very happy and peaceful year think you so much i love you in god God bless you
2016-01-01 23:53 GMT+01:00 Timothy Murphy gayleard@eircom.net:
My HP MicroServer crashes with a kernel panic when booted into kernel-3.10.0-327.3.1.el7.x86_64, but runs perfectly under kernel-3.10.0-229.20.1.el7.x86_64 .
I've been trying to save the panic message with kdump, but am not sure how one can configure kdump to do this, if indeed that is possible.
-- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
Latifa Benameur -
Timothy Murphy -
Tru Huynh