All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	hpa@zytor.com, mingo@elte.hu, a.p.zijlstra@chello.nl,
	jaswinder@kernel.org
Subject: Re: Boot hangs after "Freeing initrd memory" with 2.6.31.11
Date: Thu, 14 Jan 2010 15:08:52 +0200	[thread overview]
Message-ID: <4B4F1764.2040406@pardus.org.tr> (raw)
In-Reply-To: <4B4EF35D.3040203@pardus.org.tr>

Ozan Çağlayan wrote On 14-01-2010 12:35:
> Yinghai Lu wrote On 14-01-2010 09:43:
>> On 01/13/2010 10:58 PM, Ozan Çağlayan wrote:
>>> Ozan Çağlayan wrote On 13-01-2010 20:51:
> 
>> can you just deselect CONFIG_X86_CPU_DEBUG in your .config ?
> 
> Yes that fixed the issue. I now reenabled it and reverted the following commit which is 1/2 commits
> modifying cpu_debug code between 2.6.30..2.6.31:
> 
> From 5095f59bda6793a7b8f0856096d6893fe98e0e51 Mon Sep 17 00:00:00 2001
> From: Jaswinder Singh Rajput <jaswinder@kernel.org>
> Date: Fri, 5 Jun 2009 23:27:17 +0530
> Subject: [PATCH] x86: cpu_debug: Remove model information to reduce encoding-decoding

Reverting this commit on top of 2.6.31.11 fixes the boot hangs with AMD Athlon XP processors.
I'll double check with other reporters in a day or two.

  reply	other threads:[~2010-01-14 13:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 18:51 Boot hangs after "Freeing initrd memory" with 2.6.31.11 Ozan Çağlayan
2010-01-14  6:58 ` Ozan Çağlayan
2010-01-14  7:43   ` Yinghai Lu
2010-01-14  7:48     ` Ozan Çağlayan
2010-01-14 10:35     ` Ozan Çağlayan
2010-01-14 13:08       ` Ozan Çağlayan [this message]
2010-01-14 13:36         ` Ozan Çağlayan
2010-01-16 12:28           ` Ozan Çağlayan
2010-01-16 22:12             ` Rafael J. Wysocki
2010-01-17  8:43               ` Ozan Çağlayan
2010-01-17 13:43                 ` Rafael J. Wysocki
2010-01-17  9:22               ` Ozan Çağlayan
2010-01-17 13:44                 ` Rafael J. Wysocki
2010-01-18  1:26                   ` RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapid removal H. Peter Anvin
2010-01-18 21:28                     ` Rafael J. Wysocki
2010-01-23  0:53                     ` Andrew Morton
2010-01-23  1:05                       ` H. Peter Anvin
2010-01-23  1:20                         ` [stable] " Greg KH
2010-01-23  1:51                           ` H. Peter Anvin
2010-01-23  1:59                       ` Linus Torvalds
2010-01-23  5:22                         ` Ingo Molnar
2010-01-18  0:58             ` Boot hangs after "Freeing initrd memory" with 2.6.31.11 H. Peter Anvin

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=4B4F1764.2040406@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hpa@zytor.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@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.