All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Walsh <jwalsh@atl.lmco.com>
To: linux-rt-users@vger.kernel.org
Cc: "Gautam H. Thaker" <gthaker@atl.lmco.com>
Subject: 2.6.20-rc1-rt1 Panic on reboot after fresh kernel compile
Date: Thu, 21 Dec 2006 10:06:28 -0500	[thread overview]
Message-ID: <458AA2F4.4080601@atl.lmco.com> (raw)

I also saw this yesterday in 2.6.19.1-rt15, retried today with the new 
patch and saw the same result.  This error only occurs with the RT 
patches applied, 2.6.20-rc1 (and 2.6.19.1) boots fine with the same 
config.  After a clean compilation and install run, I reboot and receive 
the following console error message before hanging:

...
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
ÿserial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
[a few hundred junk characters]
Creating root deKernel panic - not syncing: Attempted to kill init!
 [<c0118c60>] panic+0x50/0x100
 [<c011bd59>] do_exit+0x6d9/0xa50
 [<c0158fe9>] remove_vma+0x39/0x50
 [<c015a56a>] do_munmap+0x19a/0x1f0
 [<c011c104>] do_group_exit+0x34/0xb0
 [<c015a608>] sys_munmap+0x48/0x60
 [<c010316f>] syscall_call+0x7/0xb
 [<c044007b>] packet_seq_start+0x2b/0x80

This is of course snipped to the last few relevant lines.  This is a 
reproducible message so I can rerun and give the entire console log if 
it would be helpful, or if any other information at all would be useful.

Hopefully this is in some way helpful, and thanks for any advice,

-Jonathan Walsh
Associate Member Engineering Staff
Lockheed Martin Advanced Technology Laboratories

             reply	other threads:[~2006-12-21 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 15:06 Jonathan Walsh [this message]
2006-12-21 15:31 ` 2.6.20-rc1-rt1 Panic on reboot after fresh kernel compile Ingo Molnar
2006-12-22 15:39   ` Jonathan Walsh
2006-12-22 19:06     ` Ingo Molnar
2006-12-22 20:46       ` Jonathan Walsh

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=458AA2F4.4080601@atl.lmco.com \
    --to=jwalsh@atl.lmco.com \
    --cc=gthaker@atl.lmco.com \
    --cc=linux-rt-users@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.