From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Peter Oruba" <peter.oruba@amd.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Tigran Aivazian" <tigran@aivazian.fsnet.co.uk>,
"Max Krasnyansky" <maxk@qualcomm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: [2/2 -tip] x86-microcode: generic interface refactoring
Date: Wed, 20 Aug 2008 16:11:00 +0200 [thread overview]
Message-ID: <b647ffbd0808200711j49c6c9a8m9f0af6ade5f4338@mail.gmail.com> (raw)
In-Reply-To: <48AC2340.5010204@amd.com>
2008/8/20 Peter Oruba <peter.oruba@amd.com>:
> With latest tip-microcode I get the following:
>
> Aug 23 13:38:26 gai_nfs ------------[ cut here ]------------
> Aug 23 13:38:26 gai_nfs kernel BUG at arch/x86/kernel/microcode.c:351!
What's your kernel version?
I assume it does not have the following fix, doesn't it?
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commit;h=279ef6bbb8308488398c8f33b04c760148428378
sched, cpu hotplug: fix set_cpus_allowed() use in hotplug callbacks
author Dmitry Adamushko <dmitry.adamushko@gmail.com>
Wed, 30 Jul 2008 10:34:04 +0000 (12:34 +0200)
committer Ingo Molnar <mingo@elte.hu>
Mon, 11 Aug 2008 14:32:41 +0000 (16:32 +0200)
commit 279ef6bbb8308488398c8f33b04c760148428378
> Aug 23 13:38:26 gai_nfs invalid opcode: 0000 [1] SMP
> Aug 23 13:38:26 gai_nfs CPU 0
> Aug 23 13:38:26 gai_nfs Modules linked in: microcode_amd microcode
> Aug 23 13:38:26 gai_nfs Pid: 4258, comm: bash Not tainted 2.6.27-rc1 #10
> Aug 23 13:38:26 gai_nfs RIP: 0010:[<ffffffffa000048e>] [<ffffffffa000048e>]
> microcode_update_cpu+0x1b/0xf1 [microcode]
> Aug 23 13:38:26 gai_nfs RSP: 0018:ffff88003ed41db8 EFLAGS: 00010297
> Aug 23 13:38:26 gai_nfs RAX: 0000000000000000 RBX: 0000000000000001 RCX:
> 00000000c0000100
> Aug 23 13:38:26 gai_nfs RDX: 0000000000000000 RSI: ffff88003f87cbf0 RDI:
> 0000000000000001
> Aug 23 13:38:26 gai_nfs RBP: 0000000000000001 R08: 0000000000000000 R09:
> ffff880001011ae0
> Aug 23 13:38:26 gai_nfs R10: 000000009f3b7578 R11: ffff88003f887de0 R12:
> 0000000000000000
> Aug 23 13:38:26 gai_nfs R13: 0000000000000001 R14: 0000000000000002 R15:
> ffffffff80739d00
> Aug 23 13:38:26 gai_nfs FS: 00007f0e312d26d0(0000)
> GS:ffffffff807b2a80(0000) knlGS:0000000000000000
> Aug 23 13:38:26 gai_nfs CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Aug 23 13:38:26 gai_nfs CR2: 00007f0f13293f20 CR3: 000000003e412000 CR4:
> 00000000000006a0
> Aug 23 13:38:26 gai_nfs DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> Aug 23 13:38:26 gai_nfs DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
> 0000000000000400
> Aug 23 13:38:26 gai_nfs Process bash (pid: 4258, threadinfo
> ffff88003ed40000, task ffff88003f3e5950)
> Aug 23 13:38:26 gai_nfs Stack: ffff88000101c980 0000000000000296
> 0000000000000003 0000000000000001
> Aug 23 13:38:26 gai_nfs 0000000000000001 0000000000000001 0000000000000001
> ffffffffa00005ac
> Aug 23 13:38:26 gai_nfs 0000000000000003 0000000000000001 0000000000000282
> 0000000000000002
> Aug 23 13:38:26 gai_nfs Call Trace:
> Aug 23 13:38:26 gai_nfs [<ffffffffa00005ac>] ? microcode_init_cpu+0x48/0x61
> [microcode]
> Aug 23 13:38:26 gai_nfs [<ffffffffa00006a7>] ? mc_cpu_callback+0x2b/0x76
> [microcode]
> Aug 23 13:38:26 gai_nfs [<ffffffff80242ffd>] ? notifier_call_chain+0x29/0x4c
> Aug 23 13:38:26 gai_nfs [<ffffffff805ca600>] ? cpu_up+0x105/0x16a
> Aug 23 13:38:26 gai_nfs [<ffffffff805a99d7>] ? store_online+0x46/0x6d
> Aug 23 13:38:26 gai_nfs [<ffffffff802c431a>] ? sysfs_write_file+0xd0/0x107
> Aug 23 13:38:26 gai_nfs [<ffffffff80282b8c>] ? vfs_write+0xad/0x136
> Aug 23 13:38:26 gai_nfs [<ffffffff80282cd1>] ? sys_write+0x45/0x6e
> Aug 23 13:38:26 gai_nfs [<ffffffff8020be8b>] ?
> system_call_fastpath+0x16/0x1b
[ ... ]
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2008-08-20 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 22:22 Dmitry Adamushko
2008-08-20 10:19 ` Ingo Molnar
2008-08-20 13:59 ` BUG: " Peter Oruba
2008-08-20 14:11 ` Dmitry Adamushko [this message]
2008-08-20 15:06 ` Peter Oruba
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=b647ffbd0808200711j49c6c9a8m9f0af6ade5f4338@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=peter.oruba@amd.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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
all inboxes | Powered by JetHome®