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, stable@kernel.org
Subject: Re: Boot hangs after "Freeing initrd memory" with 2.6.31.11
Date: Thu, 14 Jan 2010 15:36:39 +0200 [thread overview]
Message-ID: <4B4F1DE7.307@pardus.org.tr> (raw)
In-Reply-To: <4B4F1764.2040406@pardus.org.tr>
Ozan Çağlayan wrote On 14-01-2010 15:08:
(CC'ing stable)
>>
>> 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.
OK we've verified on 2 separate systems with Athlon XP that reverting the commit fixes the issue.
Here's proc/cpuinfo and relevant dmesg output for reference:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2600+
stepping : 0
cpu MHz : 1920.500
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up
bogomips : 3842.29
clflush size : 32
power management: ts
[ 0.461404] Freeing initrd memory: 5191k freed
[ 0.467844] initcall populate_rootfs+0x0/0x62 returned 0 after 217975 usecs
[ 0.467947] calling i8259A_init_sysfs+0x0/0x1d @ 1
[ 0.468093] initcall i8259A_init_sysfs+0x0/0x1d returned 0 after 41 usecs
[ 0.468190] calling sbf_init+0x0/0xda @ 1
[ 0.468282] initcall sbf_init+0x0/0xda returned 0 after 0 usecs
[ 0.468378] calling i8237A_init_sysfs+0x0/0x1d @ 1
[ 0.468484] initcall i8237A_init_sysfs+0x0/0x1d returned 0 after 12 usecs
[ 0.468582] calling add_rtc_cmos+0x0/0x94 @ 1
[ 0.468679] initcall add_rtc_cmos+0x0/0x94 returned 0 after 4 usecs
[ 0.468780] calling cache_sysfs_init+0x0/0x55 @ 1
[ 0.468940] initcall cache_sysfs_init+0x0/0x55 returned 0 after 64 usecs
[ 0.469041] calling cpu_debug_init+0x0/0x1f @ 1
[ 0.469190] cpu0(1) debug files 5
[ 0.469282] initcall cpu_debug_init+0x0/0x1f returned 0 after 143 usecs <-- That call wasn't returning at all
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.
Thanks,
Ozan Caglayan
next prev parent reply other threads:[~2010-01-14 13:37 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 [this message]
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=4B4F1DE7.307@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=stable@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).