mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Sat, 13 Oct 2007 07:59:22 +0200	[thread overview]
Message-ID: <20071013055922.GB26370@elte.hu> (raw)
In-Reply-To: <470FD96A.8040505@kanardia.eu>


* Rok Markovic <kernel@kanardia.eu> wrote:

> I enabled netconsole but I am affraid that it won't help. In 
> attachment I am sending complete log over netconsole. While I was 
> trying to make everything, I got a lockup on linux-2.6.23-rc8, but I 
> am not sure into this. But all lockups happend in VGA console mode. 
> Any ideas.

hm:

[  104.224904] oprofile: using NMI interrupt.

could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI 
watchdog?

how does /proc/interrupts look like shortly after bootup? Does a simple 
"intentional lockup" piece of code, which provokes a hard lockup from 
user-space, get properly zapped by the NMI watchdog (within a minute or 
so):

# cat > lockup.c

int main(void)
{
	iopl(3);
	for (;;)
		asm("cli");
}
Ctrl-D
# make lockup
# ./lockup
<hard hang>

the NMI watchdog should produce a console message similar to:

 BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers:
 ...

( if you test ./lockup and get the message properly then i'd suggest a 
  new reboot - i think we inhibit further console output after an NMI 
  printout. )

	Ingo

  parent reply	other threads:[~2007-10-13  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12  7:52 Rok Markovic
2007-10-12  8:35 ` Ingo Molnar
2007-10-12 17:55   ` Rok Markovic
2007-10-12 17:58     ` Ingo Molnar
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 [this message]
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=20071013055922.GB26370@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®