mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1-mm1  - immediate system reset at boot
Date: Thu, 17 Nov 2005 20:27:51 -0800	[thread overview]
Message-ID: <20051117202751.2a6c2fc3.akpm@osdl.org> (raw)
In-Reply-To: <200511180423.jAI4NiT5003598@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
>
> On Thu, 17 Nov 2005 17:23:30 EST, Valdis.Kletnieks@vt.edu said:
> 
> > Am chasing another issue - once I got past that, it wouldn't boot at all.
> > Grub would act like it was loading, then 2 seconds or so later, grub would
> > start up again.  My first guess was CONFIG_DEBUG_RODATA=y, but I ruled that
> > out.  More detail once I've done some more binary searching and ruled out
> > self-inflicted idiocy....
> 
> Rebuilt from a completely new and clean tree, 2.6.14-mm1 is fine, 2.6.15-rc1
> will start booting OK, -rc1-mm1 chokes up almost instantly.  It doesn't live
> long enough for either/both earlyprintk=vga or initcall_debug to output
> anything - grub says "loading", clears the screen, and 2 seconds later the
> laptop gives the 'ka-chunk' noise it does on a system reset, and I'm looking at
> the BIOS splash screen.
> 
> Any obvious places to look, or time to play bisection on the 600 patches
> in -mm?

Can't think of anything, sorry.  The obvious area to probe is around the
x86 and mm patch subserieses.


  reply	other threads:[~2005-11-18  4:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 19:18 2.6.15-rc1-mm1 Andrew Morton
2005-11-17 21:30 ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-17 22:14 ` 2.6.15-rc1-mm1 David Howells
2005-11-17 22:23   ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-18  4:23     ` 2.6.15-rc1-mm1 - immediate system reset at boot Valdis.Kletnieks
2005-11-18  4:27       ` Andrew Morton [this message]
2005-11-18  1:41 ` [-mm patch] kernel/signal.c: fix compile warning Adrian Bunk
2005-11-18  3:59   ` George Anzinger
2005-11-18  1:44 ` 2.6.15-rc1-mm1 Richard Knutsson
2005-11-18  1:53   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:20 ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18  7:42   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:56     ` 2.6.15-rc1-mm1 Sander
2005-11-18 20:58     ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18 21:19       ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 12:43 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 20:37   ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 21:14     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-18 23:16       ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:03         ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 23:35         ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:51           ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:24             ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-19  1:26               ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:49                 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  3:24                 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-21  0:00                   ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-21  0:26                   ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 20:47                     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-22 20:55                       ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 22:05                         ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  1:40               ` 2.6.15-rc1-mm1 Ian McDonald

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=20051117202751.2a6c2fc3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --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

Powered by JetHome