From: Ingo Molnar <mingo@elte.hu>
To: Rok Markovic <kernel@kanardia.eu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 2.6.23-rt1 lockup after loading HAL deamon
Date: Fri, 12 Oct 2007 19:58:31 +0200 [thread overview]
Message-ID: <20071012175831.GA27420@elte.hu> (raw)
In-Reply-To: <470FB4F4.60707@kanardia.eu>
* Rok Markovic <kernel@kanardia.eu> wrote:
> I tried to recompile with those options enabled, kernel and linux
> boots and loads fine, but after few minutes (if i try to recompile
> kernel in console) the system locks completely (hard reset) without
> any messages. Is there anything I can do, maybe console on serial
> port? My new config is atached.
yes, serial console (or netconsole) output would be useful, if you can
solve that. Another way would be to boot with nmi_watchdog=2, do the
kernel recompile in a VGA text console, and wait for the lockup to
occur. Either you get some crash message to the text console
immediately, or you should get the NMI watchdog print something within a
minute or so. If neither happens you just get a blank hard lockup then
the wedge is very deep ...
(also make sure that the NMI counter in /proc/interrupts is increasing
on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are
increasing their NMI counters once per second then the NMI watchdog wont
be able to print out a stackdump.)
Ingo
next prev parent reply other threads:[~2007-10-12 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 7:52 2.6.23-rt1 lockup after loading HAL deamon Rok Markovic
2007-10-12 8:35 ` Ingo Molnar
2007-10-12 17:55 ` Rok Markovic
2007-10-12 17:58 ` Ingo Molnar [this message]
2007-10-12 18:13 ` Rok Markovic
2007-10-12 20:30 ` Rok Markovic
2007-10-12 20:32 ` Rok Markovic
2007-10-13 5:59 ` Ingo Molnar
2007-10-13 9:29 ` Rok Markovic
2007-10-13 9:41 ` Ingo Molnar
2007-10-13 12:03 ` Rok Markovic
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=20071012175831.GA27420@elte.hu \
--to=mingo@elte.hu \
--cc=kernel@kanardia.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.