From: Priit Laes <plaes@plaes.org>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Jack Steiner <steiner@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: [REGRESSION] x86: support for new UV apic
Date: Fri, 25 Apr 2008 07:43:20 +0300 [thread overview]
Message-ID: <1209098600.3707.13.camel@localhost> (raw)
Hey,
I am getting two following warnings (probable one per each CPU core)
using the latest Linus's git:
WARNING: at arch/x86/kernel/genapic_64.c:86 read_apic_id+0x30/0x62()
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.25-03563-gf7288b1 #20
Call Trace:
[<ffffffff8022f1e1>] warn_on_slowpath+0x51/0x63
[<ffffffff80282e48>] sys_ioctl+0x2d/0x5d
[<ffffffff805185ff>] _spin_lock+0xe/0x24
[<ffffffff80227459>] task_rq_lock+0x3d/0x73
[<ffffffff805133c3>] set_cpu_sibling_map+0x336/0x350
[<ffffffff8021c1b8>] read_apic_id+0x30/0x62
[<ffffffff806d921d>] verify_local_APIC+0x90/0x138
[<ffffffff806d84b5>] native_smp_prepare_cpus+0x1f9/0x305
[<ffffffff806ce7b1>] kernel_init+0x59/0x2d9
[<ffffffff80518a26>] _spin_unlock_irq+0x11/0x2b
[<ffffffff8020bf48>] child_rip+0xa/0x12
[<ffffffff806ce758>] kernel_init+0x0/0x2d9
[<ffffffff8020bf3e>] child_rip+0x0/0x12
---[ end trace ca143223eefdc828 ]---
Few hours of bisecting gave me following commit as a suspect
ac23d4ee3f84de33c16ed7e68f9adee2386e74fb is first bad commit
commit ac23d4ee3f84de33c16ed7e68f9adee2386e74fb
Author: Jack Steiner <steiner@sgi.com>
Date: Fri Mar 28 14:12:16 2008 -0500
x86: support for new UV apic
next reply other threads:[~2008-04-25 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 4:43 Priit Laes [this message]
2008-04-25 6:44 ` [REGRESSION] x86: support for new UV apic Ingo Molnar
2008-04-25 9:11 ` Gabriel C
2008-04-25 9:19 ` Priit Laes
2008-04-25 9:45 ` Andi Kleen
2008-04-25 11:21 ` Gabriel C
2008-04-25 11:41 ` Gabriel C
2008-04-25 15:53 ` Priit Laes
2008-04-28 17:41 ` 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=1209098600.3707.13.camel@localhost \
--to=plaes@plaes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.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