From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Yinghai Lu <yinghai@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
hpa@zytor.com, mingo@elte.hu, a.p.zijlstra@chello.nl,
jaswinder@kernel.org, stable@kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Boot hangs after "Freeing initrd memory" with 2.6.31.11
Date: Sun, 17 Jan 2010 10:43:12 +0200 [thread overview]
Message-ID: <4B52CDA0.7050909@pardus.org.tr> (raw)
In-Reply-To: <201001162312.34189.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Saturday 16 January 2010, Ozan Çağlayan wrote:
>>>
>>> I think that the commit should be reverted or a fix should be released for linux-2.6 tree,
>>> as well as .31 and .32 stable trees.
>>
>> Linux 2.6.31 is released on Sep 9th. So people having an Athlon XP processor + a kernel newer than 4 months
>> which enables CONFIG_X86_CPU_DEBUG can't even boot into a linux kernel. I was *at least* expecting a comment from the relevant
>> people but nope for 2 days.
>>
>> It seems to be a serious regression which doesn't get caught. I'm also CC'ing Rafael, maybe he can inject this
>> in one of his regression threads.
>
> Well, the problem is I'm not listing regressions from 2.6.31 any more.
Yes you're right.
>
> Also, I don't have hardware to reproduce the problem on.
>
> Is there a bug entry for this in the kernel Bugzilla?
Nope not for now, I'll do that.
next prev parent reply other threads:[~2010-01-17 8:43 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
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 [this message]
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=4B52CDA0.7050909@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--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.