public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: "'Matthew Harrell'" 
	<mharrell-dated-1047753657.4eb01d@bittwiddlers.com>,
	"'Kernel List'" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.64 boot problems
Date: Tue, 11 Mar 2003 07:49:14 +0100	[thread overview]
Message-ID: <00c001c2e79a$5567c8c0$3f00a8c0@witbe> (raw)
In-Reply-To: <20030310184052.GA1623@bittwiddlers.com>

Could you try the same config without APIC and IO APIC for Uniprocessor
?
I've a problem that is directly related to 2.5.64 and these features...

Without them, 2.5.64 just boots fine...

Regards,
Paul

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> Matthew Harrell
> Sent: Monday, March 10, 2003 7:41 PM
> To: Kernel List
> Subject: Re: 2.5.64 boot problems
> 
> 
> > this is the first time i tried to use a 2.5.x kernel. i compiled it 
> > successfully but at boot time it stops at "ok booting kernel"
> 
> I've got the same problem on my HP ZT1195 laptop and it only 
> just started 
> with the 2.5.64 kernels (and all bk snapshots).  2.5.63 
> worked fine.  Config attached below
> 
> -- 
>   Matthew Harrell                          I no longer need 
> to punish, deceive,
>   Bit Twiddlers, Inc.                       or compromise 
> myself, unless I want
>   mharrell@bittwiddlers.com                 to stay employed.
> 


  reply	other threads:[~2003-03-11  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10  9:59 2.5.64 boot problems Daniel Engelschalt
2003-03-10 18:40 ` Matthew Harrell
2003-03-11  6:49   ` Paul Rolland [this message]
2003-03-11 13:53     ` Matthew Harrell
     [not found] <200303101009.h2AA9sSE000765@81-2-122-30.bradfords.org.uk>
2003-03-10 18:01 ` Daniel Engelschalt

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='00c001c2e79a$5567c8c0$3f00a8c0@witbe' \
    --to=rol@as2917.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell-dated-1047753657.4eb01d@bittwiddlers.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