mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [2.4] lockup on boot with 2.4.26
Date: Mon, 05 Jul 2004 06:10:50 +0200	[thread overview]
Message-ID: <1089000649.9568.15.camel@nosferatu.lan> (raw)
In-Reply-To: <20040705002845.GB20847@logos.cnet>

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

On Mon, 2004-07-05 at 02:28, Marcelo Tosatti wrote:
> On Mon, Jul 05, 2004 at 12:15:52AM +0200, Martin Schlemmer wrote:
> > Hi
> > 
> > I have tried to update my gateway's kernel to 2.4.26 (Been running
> > happily on 2.4.17, but a bit _old_, so finally decided this weekend
> > to try and update it).   At boot though it only gets to:
> > 
> > --
> > Uncompressing kernel... booting linux...
> > --
> > 
> > and then locks hard (the capslock and scroll lock leds lids)
> > 
> > Its an old P3 450 on an Asus P2B (BX440 chipset).  .config is pretty
> > much the same as for the 2.4.17 kernel.
> > 
> > I did have grsecurity initially applied, but I tried on an vanilla
> > kernel as well (besides some netfiler POM patches, but they are all
> > modules).  I also tried to disable acpi.
> > 
> > Any suggestions would be appreciated.  .config attached.
> 
> Hi Martin, 
> 
> I do not know the answer for your problem but I'll try to help.
> 
> Can you do a binary search and find out which v2.4 kernel stops working? 
> 
> You can start with 2.4.21, see if that works, if so, try 2.4.23, etc? 

Sure, will do and let you know, thanks.


-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-05  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-04 22:15 Martin Schlemmer
2004-07-05  0:28 ` Marcelo Tosatti
2004-07-05  4:10   ` Martin Schlemmer [this message]
2004-07-05  9:56 Mikael Pettersson

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=1089000649.9568.15.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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®