From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Brown, Len" <len.brown@intel.com>,
Linux-pm@smtp1.linux-foundation.org,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
mailing list <linux-pm@lists.linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Yong Wang <yong.y.wang@linux.intel.com>
Subject: Re: resume crashes in intel_init_thermal [was: mmotm 2009-11-13-19-59 uploaded]
Date: Sat, 14 Nov 2009 08:15:49 -0800 [thread overview]
Message-ID: <20091114081549.1477fabc.akpm@linux-foundation.org> (raw)
In-Reply-To: <4AFEB060.80007@gmail.com>
On Sat, 14 Nov 2009 14:28:00 +0100 Jiri Slaby <jirislaby@gmail.com> wrote:
> On 11/14/2009 05:03 AM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-11-13-19-59 has been uploaded to
>
> Hi, resume from ram dies in intel_init_thermal in that kernel:
> http://www.fi.muni.cz/~xslaby/sklad/mce_oops.png
lol.
> The code is cc cc cc cc ... KGDB and KPROBES are off, I don't know where
> the pattern may come from.
>
> Does it ring a bell? Any ideas? mmotm 2009-11-01-10-01 was OK.
From: Andrew Morton <akpm@linux-foundation.org>
Revert
: commit ce6b5d768c79b9d5dd6345c033bae781d5ca9b8e
: Author: Yong Wang <yong.y.wang@linux.intel.com>
: AuthorDate: Wed Nov 11 15:51:25 2009 +0800
: Commit: Ingo Molnar <mingo@elte.hu>
: CommitDate: Wed Nov 11 12:33:32 2009 +0100
:
: x86: Mark the thermal init functions __init
because intel_init_thermal() is called from mce_intel_feature_init() at
resume time, and we'd like its text to still be in memory when that
happens.
Reported-by: Jiri Slaby <jirislaby@gmail.com>
Cc: Yong Wang <yong.y.wang@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/kernel/cpu/mcheck/therm_throt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/x86/kernel/cpu/mcheck/therm_throt.c~revert-1 arch/x86/kernel/cpu/mcheck/therm_throt.c
--- a/arch/x86/kernel/cpu/mcheck/therm_throt.c~revert-1
+++ a/arch/x86/kernel/cpu/mcheck/therm_throt.c
@@ -256,7 +256,7 @@ asmlinkage void smp_thermal_interrupt(st
ack_APIC_irq();
}
-void __init mcheck_intel_therm_init(void)
+void mcheck_intel_therm_init(void)
{
/*
* This function is only called on boot CPU. Save the init thermal
@@ -268,7 +268,7 @@ void __init mcheck_intel_therm_init(void
lvtthmr_init = apic_read(APIC_LVTTHMR);
}
-void __init intel_init_thermal(struct cpuinfo_x86 *c)
+void intel_init_thermal(struct cpuinfo_x86 *c)
{
unsigned int cpu = smp_processor_id();
int tm2 = 0;
_
next prev parent reply other threads:[~2009-11-14 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911140403.nAE43CN1016851@imap1.linux-foundation.org>
2009-11-14 13:28 ` resume crashes in intel_init_thermal [was: mmotm 2009-11-13-19-59 uploaded] Jiri Slaby
[not found] ` <4AFEB060.80007@gmail.com>
2009-11-14 16:15 ` Andrew Morton [this message]
2009-11-14 18:44 ` Jiri Slaby
2009-11-15 8:07 ` Ingo Molnar
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=20091114081549.1477fabc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Linux-pm@smtp1.linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=yong.y.wang@linux.intel.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