NMI watchdog: BUG: soft lockup
We have HP DL360 G8 and trying to install CentOS7 and getting this error before it start installing package so installation is never getting complete.. it just going on and on with this error, we have tried to upgrade firmware of HPVSA RAID controller too
[ 175.185716] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 203.189583] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 231.192973] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
Update - CentOS 5/6 working fine, only C7 has issue.
linux drivers raid hp
asked Mar 28 '17 at 15:27
SatishSatish
64611134
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We have HP DL360 G8 and trying to install CentOS7 and getting this error before it start installing package so installation is never getting complete.. it just going on and on with this error, we have tried to upgrade firmware of HPVSA RAID controller too
[ 175.185716] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 203.189583] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 231.192973] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
Update - CentOS 5/6 working fine, only C7 has issue.
linux drivers raid hp
asked Mar 28 '17 at 15:27
SatishSatish
64611134
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We have HP DL360 G8 and trying to install CentOS7 and getting this error before it start installing package so installation is never getting complete.. it just going on and on with this error, we have tried to upgrade firmware of HPVSA RAID controller too
[ 175.185716] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 203.189583] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 231.192973] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
Update - CentOS 5/6 working fine, only C7 has issue.
linux drivers raid hp
asked Mar 28 '17 at 15:27
SatishSatish
64611134
We have HP DL360 G8 and trying to install CentOS7 and getting this error before it start installing package so installation is never getting complete.. it just going on and on with this error, we have tried to upgrade firmware of HPVSA RAID controller too
[ 175.185716] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 203.189583] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
[ 231.192973] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [hpvsa/4:958]
Update - CentOS 5/6 working fine, only C7 has issue.
linux drivers raid hp
linux drivers raid hp
asked Mar 28 '17 at 15:27
SatishSatish
64611134
asked Mar 28 '17 at 15:27
SatishSatish
64611134
edited Mar 28 '17 at 15:56
Satish
asked Mar 28 '17 at 15:27
SatishSatish
64611134
asked Mar 28 '17 at 15:27
SatishSatish
64611134
asked Mar 28 '17 at 15:27
SatishSatish
64611134
64611134
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have seen this on HP DL360 G8 servers which were using multiple fiber channel controllers and multipath to attach several hundred SAN disks to a server.
The problem was that the kernel was booted with a serial console enabled and running at 9600 bps.
When the large number of drives was being discovered, a lot of verbose output was being dumped to the console. The slow serial console could not keep up with the messages and the soft lockup would occur.
Check /etc/default/grub for lines that look like:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=9600"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600"
If you need to maintain a serial console, change 9600 to 115200:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=115200"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
Then reinstall grub with grub2-mkconfig -o /boot/grub2/grub.cfg
If you don't need a serial console, you can remove GRUB_SERIAL_COMMAND and update the other two lines and reinstall grub:
GRUB_TERMINAL="console"
GRUB_CMDLINE_LINUX="console=tty0"
You may have other parameters in GRUB_CMDLINE_LINUX, in which case you want to be careful to make sure that you only change the console so that you aren't making other changes which could negatively impact your system.
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f354368%2fnmi-watchdog-bug-soft-lockup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have seen this on HP DL360 G8 servers which were using multiple fiber channel controllers and multipath to attach several hundred SAN disks to a server.
The problem was that the kernel was booted with a serial console enabled and running at 9600 bps.
When the large number of drives was being discovered, a lot of verbose output was being dumped to the console. The slow serial console could not keep up with the messages and the soft lockup would occur.
Check /etc/default/grub for lines that look like:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=9600"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600"
If you need to maintain a serial console, change 9600 to 115200:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=115200"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
Then reinstall grub with grub2-mkconfig -o /boot/grub2/grub.cfg
If you don't need a serial console, you can remove GRUB_SERIAL_COMMAND and update the other two lines and reinstall grub:
GRUB_TERMINAL="console"
GRUB_CMDLINE_LINUX="console=tty0"
You may have other parameters in GRUB_CMDLINE_LINUX, in which case you want to be careful to make sure that you only change the console so that you aren't making other changes which could negatively impact your system.
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
add a comment |
I have seen this on HP DL360 G8 servers which were using multiple fiber channel controllers and multipath to attach several hundred SAN disks to a server.
The problem was that the kernel was booted with a serial console enabled and running at 9600 bps.
When the large number of drives was being discovered, a lot of verbose output was being dumped to the console. The slow serial console could not keep up with the messages and the soft lockup would occur.
Check /etc/default/grub for lines that look like:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=9600"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600"
If you need to maintain a serial console, change 9600 to 115200:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=115200"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
Then reinstall grub with grub2-mkconfig -o /boot/grub2/grub.cfg
If you don't need a serial console, you can remove GRUB_SERIAL_COMMAND and update the other two lines and reinstall grub:
GRUB_TERMINAL="console"
GRUB_CMDLINE_LINUX="console=tty0"
You may have other parameters in GRUB_CMDLINE_LINUX, in which case you want to be careful to make sure that you only change the console so that you aren't making other changes which could negatively impact your system.
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
add a comment |
I have seen this on HP DL360 G8 servers which were using multiple fiber channel controllers and multipath to attach several hundred SAN disks to a server.
The problem was that the kernel was booted with a serial console enabled and running at 9600 bps.
When the large number of drives was being discovered, a lot of verbose output was being dumped to the console. The slow serial console could not keep up with the messages and the soft lockup would occur.
Check /etc/default/grub for lines that look like:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=9600"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600"
If you need to maintain a serial console, change 9600 to 115200:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=115200"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
Then reinstall grub with grub2-mkconfig -o /boot/grub2/grub.cfg
If you don't need a serial console, you can remove GRUB_SERIAL_COMMAND and update the other two lines and reinstall grub:
GRUB_TERMINAL="console"
GRUB_CMDLINE_LINUX="console=tty0"
You may have other parameters in GRUB_CMDLINE_LINUX, in which case you want to be careful to make sure that you only change the console so that you aren't making other changes which could negatively impact your system.
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
I have seen this on HP DL360 G8 servers which were using multiple fiber channel controllers and multipath to attach several hundred SAN disks to a server.
The problem was that the kernel was booted with a serial console enabled and running at 9600 bps.
When the large number of drives was being discovered, a lot of verbose output was being dumped to the console. The slow serial console could not keep up with the messages and the soft lockup would occur.
Check /etc/default/grub for lines that look like:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=9600"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600"
If you need to maintain a serial console, change 9600 to 115200:
GRUB_TERMINAL="serial console"
GRUB_SERIAL_COMMAND="serial --speed=115200"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"
Then reinstall grub with grub2-mkconfig -o /boot/grub2/grub.cfg
If you don't need a serial console, you can remove GRUB_SERIAL_COMMAND and update the other two lines and reinstall grub:
GRUB_TERMINAL="console"
GRUB_CMDLINE_LINUX="console=tty0"
You may have other parameters in GRUB_CMDLINE_LINUX, in which case you want to be careful to make sure that you only change the console so that you aren't making other changes which could negatively impact your system.
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
answered Mar 31 '17 at 16:19
Rich Alloway - RogueWaveRich Alloway - RogueWave
1114
1114
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f354368%2fnmi-watchdog-bug-soft-lockup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
