All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Cc: Valdis.Kletnieks@vt.edu, Nick Orlov <bugfixer@list.ru>
Subject: Re: 2.6.5-rc1-mm1 hangs after Uncompressing kernel...
Date: Wed, 17 Mar 2004 11:18:40 +0100	[thread overview]
Message-ID: <200403171118.40360@WOLK> (raw)
In-Reply-To: <200403162226.i2GMQTGp003101@turing-police.cc.vt.edu>

On Tuesday 16 March 2004 23:26, Valdis.Kletnieks@vt.edu wrote:

Hi Valadis, Nick, Andrew,

> > reverting early-x86-cpu-detection-fix solved the problem for me.
> I had issues with that patch as well, except that rather than a hang, I'd
> get 'Uncompressing kernel...' and then the screen would clear and instead
> of a penguin logo and boot messages, there'd be a second or so of silence
> and then the dread 'ka-chunk' of the machine resetting for a reboot,
> and then I'd be looking at the BIOS screen again.
> Reverting that patch fixed it for me as well.

exactly the same for me.


processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.66GHz
stepping        : 9
cpu MHz         : 3201.176
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 6383.20


ciao, Marc


      reply	other threads:[~2004-03-17 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 17:51 2.6.5-rc1-mm1 hangs after Uncompressing kernel Nick Orlov
2004-03-16 22:26 ` Valdis.Kletnieks
2004-03-17 10:18   ` Marc-Christian Petersen [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=200403171118.40360@WOLK \
    --to=m.c.p@wolk-project.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=bugfixer@list.ru \
    --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.