public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chuck Harding <charding@llnl.gov>
Cc: Linux Kernel Discussion List <linux-kernel@vger.kernel.org>
Subject: Re: Oops when rebooting 2.6.13-rc4-RT-V0.7.52-*
Date: Fri, 5 Aug 2005 10:13:24 +0200	[thread overview]
Message-ID: <20050805081324.GC6409@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.63.0508041430140.14107@ghostwheel.llnl.gov>


* Chuck Harding <charding@llnl.gov> wrote:

> couldn't see the beginning of the oops but at the end was
> Init: no more processes left in this run level
> and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
> and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions
> I have on hand (08,10,13) showed the same symptom.
> 
> This is my desktop system - Dell Optiplex GX-240 2GHz P4 1Gb SDRAM ATI 
> Radeon VE/7000 QY SB Live! Value. Dell FP2000 RHEL 4.0 KDE 3.3
> 
> I don't have serial console debugging capability here at work, so what 
> can I do to debug this? Thanks.

it's the first oops that matters. You could try to 'freeze' the system 
after printing the first stacktrace, via the patch below - but debugging 
boot-time crashes without logging support is a quite tedious process.

(maybe, if the crash happens after the ethernet card is detected, you 
could try netconsole logging.)

	Ingo

Index: linux/arch/i386/kernel/traps.c
===================================================================
--- linux.orig/arch/i386/kernel/traps.c
+++ linux/arch/i386/kernel/traps.c
@@ -170,6 +170,7 @@ void show_trace(struct task_struct *task
 		printk(" =======================\n");
 	}
 	print_traces(task);
+	for (;;) raw_local_irq_disable();
 	show_held_locks(task);
 }
 

  reply	other threads:[~2005-08-05  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 21:37 Oops when rebooting 2.6.13-rc4-RT-V0.7.52-* Chuck Harding
2005-08-05  8:13 ` Ingo Molnar [this message]
2005-08-10 16:35   ` Chuck Harding

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=20050805081324.GC6409@elte.hu \
    --to=mingo@elte.hu \
    --cc=charding@llnl.gov \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox