mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel I. Applebaum" <kernel@danapple.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1[89] boot problem
Date: Tue, 27 Aug 2002 08:08:05 -0500	[thread overview]
Message-ID: <20020827130810.1A04F111F0@wotke.danapple.com> (raw)
In-Reply-To: Your message of "Fri, 23 Aug 2002 01:07:11 CDT." <20020823060716.020F1107D9@wotke.danapple.com>


I've been tracking down my booting problem, and while reviewing old
email, found that in trying to track down (and never succeeding) a VM
problem last fall, I determined that any kernel after 2.4.15-pre2
would not boot on my machine.  So, something changed between
2.4.15-pre2 and 2.4.15-pre3 that means linux will not boot.  The
symptom is that the boot sequence displays "Loading linux-2.4.19..."
but never display "Uncompressing".  I've enclosed the 2.4.15-pre3
Changelog.  Any ideas which of the changes would have affected
booting?

pre3:
 - Al Viro: sanity-check user arguments, zero-terminated strings etc.
 - Urban Widmark: smbfs update (server/client cache coherency etc)
 - Rik van Riel, Marcelo Tosatti: VM updates
 - Cort Dougan: PPC updates
 - Neil Brown: raid1/5 failed drive fixups, NULL ptr checking, md error cleanup
 - Neil Brown: knfsd fix for 64-bit architectures, and filehandle resolveir
 - Ken Brownfield: workaround for menuconfig CPU selection glitch
 - David Miller: sparc64 MM setup fix, arpfilter forward port
 - Keith Owens: Remove obsolete IPv6 provider based addressing
 - Jari Ruusu: block_write error case cleanup fix
 - Jeff Garzik: netdriver update

Thanks!

Dan.

  reply	other threads:[~2002-08-27 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  6:07 kernel
2002-08-27 13:08 ` Daniel I. Applebaum [this message]
2002-08-27 17:13   ` Robert Schwebel

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=20020827130810.1A04F111F0@wotke.danapple.com \
    --to=kernel@danapple.com \
    --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

all inboxes | Powered by JetHome®