All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jurriaan <thunder7@xs4all.nl>
To: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ?
Date: Fri, 7 Feb 2003 21:19:10 +0100	[thread overview]
Message-ID: <20030207201910.GA4322@middle.of.nowhere> (raw)
In-Reply-To: <20030206123340.GA3305@codemonkey.org.uk>

From: Dave Jones <davej@codemonkey.org.uk>
Date: Thu, Feb 06, 2003 at 12:33:40PM +0000
> On Thu, Feb 06, 2003 at 07:07:42AM +0100, Jurriaan wrote:
>  > Until now, all 2.5.59-based kernels (2.5.59 vanilla, 2.5.59 + vmlinux
>  > patch, 2.5.59-mm[1-8]) hang very early in the boot-process on my system,
>  > right after 'Uncompressing Linux...'
> 
> Two suspects (from freezing boxes Ive had here) are ACPI and PNP. Try
> disabling those first.
> 
I didn't use them. I was busy checking out where between cset-943 and
cset-944 it stopped booting, when I accidentally removed my .config
file. I recreated it from the one I posted earlier to lkml, and suddenly
all 2.5.59 kernels boot. I don't know if I'm glad it's solved or
irritated that I don't know how it was solved.

Anyway, 2.5.59-mm8 boots here just fine.

Thanks everyone!

Jurriaan
-- 
Gore of Borg: I invented the collective!
GNU/Linux 2.5.59 SMP/ReiserFS 2x2318 bogomips load av: 0.05 0.06 0.02

      parent reply	other threads:[~2003-02-07 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06  6:07 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ? Jurriaan
2003-02-06  6:23 ` Andrew Morton
2003-02-06 12:33 ` Dave Jones
2003-02-06 12:51   ` Duncan Sands
2003-02-06 12:50     ` Dave Jones
2003-02-07 20:19   ` Jurriaan [this message]

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=20030207201910.GA4322@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=davej@codemonkey.org.uk \
    --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 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.