From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
jeremy@goop.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: git-x86 oopses in acpi_ps_peek_opcode
Date: Mon, 28 Jan 2008 19:11:13 +0100 [thread overview]
Message-ID: <20080128181113.GA5375@elte.hu> (raw)
In-Reply-To: <20080128183204.GA25724@one.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> > do you still see that crash?
>
> New the second oops in
> allocate_threshold_blocks->sysfs_add_file->kobject_uevent_env happens
> (see other mail)
that's a Linus -git problem, the upstream kobject changes - try Greg's
and Yinghai Lu's patch below, does it help?
Ingo
Index: linux-x86.q/arch/x86/kernel/cpu/mcheck/mce_amd_64.c
===================================================================
--- linux-x86.q.orig/arch/x86/kernel/cpu/mcheck/mce_amd_64.c
+++ linux-x86.q/arch/x86/kernel/cpu/mcheck/mce_amd_64.c
@@ -450,7 +450,8 @@ recurse:
if (err)
goto out_free;
- kobject_uevent(&b->kobj, KOBJ_ADD);
+ if (b)
+ kobject_uevent(&b->kobj, KOBJ_ADD);
return err;
@@ -553,8 +554,9 @@ static __cpuinit int threshold_create_de
unsigned int bank;
int err = 0;
+ printk(KERN_DEBUG "threshold_create_device: cpu %d, bank_map=%02x\n", cpu, per_cpu(bank_map,cpu));
for (bank = 0; bank < NR_BANKS; ++bank) {
- if (!(per_cpu(bank_map, cpu) & 1 << bank))
+ if (!(per_cpu(bank_map, cpu) & (1 << bank)))
continue;
err = threshold_create_bank(cpu, bank);
if (err)
@@ -637,7 +639,7 @@ static void threshold_remove_device(unsi
unsigned int bank;
for (bank = 0; bank < NR_BANKS; ++bank) {
- if (!(per_cpu(bank_map, cpu) & 1 << bank))
+ if (!(per_cpu(bank_map, cpu) & (1 << bank)))
continue;
threshold_remove_bank(cpu, bank);
}
next prev parent reply other threads:[~2008-01-28 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 17:19 git-x86 oopses in acpi_ps_peek_opcode Andi Kleen
2008-01-28 17:34 ` Ingo Molnar
2008-01-28 18:32 ` Andi Kleen
2008-01-28 18:11 ` Ingo Molnar [this message]
2008-01-28 18:58 ` Andi Kleen
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=20080128181113.GA5375@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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