From: "Oleg A. Arkhangelsky" <sysoleg@progtech.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Hard lockups on 2.6.22.4-SMP
Date: Wed, 24 Oct 2007 09:49:07 +0400 [thread overview]
Message-ID: <1397016698.20071024094907@progtech.ru> (raw)
In-Reply-To: <1696948867.20071023164555@progtech.ru>
Hello,
Answering to myself.
OAA> We have a problem with spontaneous (there is no relation with CPU
OAA> load, memory load, uptime) hard lockups on linux 2.6.22.4 (no
OAA> additional patches) on SMP system (Intel E7230 ICH7 Montherboard). Num
OAA> Lock (Caps Lock - no matter) on keyboard is not responding. There is
OAA> no debug on console (no oops, no kernel panic, no NMI watchdog info
OAA> [but nmi_watchdog=1 and NMI in /proc/interrupts is OK]). All we see is
OAA> just previous console state (for example - login: prompt). We have the
OAA> same situation on another PC with abosolutely the some hardware and
OAA> software configuration. Could you give us some hints about how to
OAA> debug this situation? If you need some additional information about
OAA> our system, feel free to ask. I can post a lot of output (i.e. lspci,
OAA> dmesg, etc...) but i don't want to post any useless information.
Yesterday we added CONFIG_DEBUG_SPINLOCK and
CONFIG_DEBUG_SPINLOCK_SLEEP to our kernel config.
After six hours of uptime we got the same lockup, but the kernel
became a little verbose:
BUG: spinlock lockup on CPU#1, swapper/0, e9bcb200
Nothing else. No call trace, no cpu registers dump. Just this
line. Any hints?
--
wbr,
Oleg mailto:sysoleg@progtech.ru
prev parent reply other threads:[~2007-10-24 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 12:45 Hard lockups on 2.6.22.4-SMP Oleg A. Arkhangelsky
2007-10-24 5:49 ` Oleg A. Arkhangelsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1397016698.20071024094907@progtech.ru \
--to=sysoleg@progtech.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.