Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
09-01-2017, 10:30 AM
|
#1
|
LQ Newbie
Registered: May 2017
Posts: 7
Rep:
|
centos error-NMI received for unknown reason 39 on cpu
hi my centos server not booting and showing the error as...
uhhuh. NMI received for unknown reason 39 on cpu 0
do you have a strange power saving mode enable?
dazed and confused but trying to continue
what is this issue and what is the fox for this..
need help in asap..
thanks in advance...
|
|
|
09-01-2017, 11:30 AM
|
#2
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
NMI = Non-maskable interrupt.
This is mainly a hardware message. Did your server reboot (panic) after these messages?
You should look into updating firmware and BIOS for your system unless it is a virtual server.
|
|
|
09-02-2017, 12:27 AM
|
#3
|
LQ Newbie
Registered: May 2017
Posts: 7
Original Poster
Rep:
|
yes , keenel panic its comming.. so what needs to done to fix this.
thanks
Bicky
|
|
|
09-05-2017, 09:30 AM
|
#4
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
As noted this is a hardware issue. You need to look at updating the BIOS and firmware for your hardware.
|
|
|
All times are GMT -5. The time now is 02:58 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|