From: Thomas Gleixner <tglx@linutronix.de>
To: Petri Latvala <petri.latvala@intel.com>
Cc: Yu Chen <yu.c.chen@intel.com>, Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Tony Luck <tony.luck@intel.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Alok Kataria <akataria@vmware.com>,
Joerg Roedel <joro@8bytes.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Steven Rostedt <rostedt@goodmis.org>,
Christoph Hellwig <hch@lst.de>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Rui Zhang <rui.zhang@intel.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in linux-next
Date: Mon, 16 Oct 2017 13:04:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710161237260.1973@nanos> (raw)
In-Reply-To: <cd667019-c16e-60db-7c5d-f2f1cf8d7351@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Mon, 16 Oct 2017, Petri Latvala wrote:
Please CC LKML next time when you report a problem. I almost missed this
thread.
> [ 174.561006] kernel BUG at arch/x86/kernel/apic/vector.c:154!
> [ 174.716682] assign_vector_locked+0x9c/0x150
> [ 174.721229] apic_set_affinity+0x47/0x70
> [ 174.725440] ioapic_set_affinity+0x1a/0x60
> [ 174.729838] irq_do_set_affinity+0x18/0x60
> [ 174.734206] irq_migrate_all_off_this_cpu+0x136/0x270
> [ 174.739647] fixup_irqs+0x2f/0x130
> [ 174.743312] cpu_disable_common+0x1c7/0x1e0
> [ 174.747792] native_cpu_disable+0x20/0x30
> [ 174.752073] take_cpu_down+0x3c/0xa0
> [ 174.755869] multi_cpu_stop+0x8e/0xb0
> [ 174.759762] ? cpu_stop_queue_work+0x90/0x90
> [ 174.764360] cpu_stopper_thread+0x8a/0x100
> [ 174.768758] smpboot_thread_fn+0x165/0x230
> [ 174.773168] kthread+0x10c/0x140
Can you please pick up linux-next of today and merge the x86/apic branch
from the tip-tree into it:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
There is a fix which might be related. Though I have no idea yet how the
above can happen.
Please enable tracing in the kernel configuration and enable the vector
tracepoints.
# for D in `ls -d /sys/kernel/debug/tracing/events/irq_vectors/vector_*`; do echo 1 > $D/enable; done
Also please do
# echo 1 > /proc/sys/kernel/ftrace_dump_on_oops
That should dump the trace buffer when the bug hits. I try to reproduce
myself.
Thanks,
tglx
next parent reply other threads:[~2017-10-16 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3f2d5df-2fd9-5e7f-b744-144e0575f61b@intel.com>
[not found] ` <20171013110850.GA5303@yu-chen.sh.intel.com>
[not found] ` <149ec6e8-4189-040c-a53c-12b0a51a855e@intel.com>
[not found] ` <c1f48dee-bf92-4076-eb15-6e306786bf50@intel.com>
[not found] ` <e1689005-7e4e-a3c9-5f81-57d337a57a2f@intel.com>
[not found] ` <cd667019-c16e-60db-7c5d-f2f1cf8d7351@intel.com>
2017-10-16 11:04 ` Thomas Gleixner [this message]
2017-10-16 11:38 ` Regression in linux-next Petri Latvala
2017-10-16 12:34 ` Thomas Gleixner
2017-10-16 12:54 ` Thomas Gleixner
2017-10-16 13:10 ` Petri Latvala
2017-10-16 14:16 ` Thomas Gleixner
2017-10-17 14:49 ` [tip:x86/apic] x86/vector: Use correct per cpu variable in free_moved_vector() tip-bot for Thomas Gleixner
[not found] <SJ1PR11MB6129592BDF5D06949F99816CB95B9@SJ1PR11MB6129.namprd11.prod.outlook.com>
[not found] ` <SJ1PR11MB6129A7F5C08E2C47748F2BA5B97E9@SJ1PR11MB6129.namprd11.prod.outlook.com>
[not found] ` <SJ1PR11MB612980562220A376CA90E105B97E9@SJ1PR11MB6129.namprd11.prod.outlook.com>
2023-07-25 6:42 ` Regression in linux-next Borah, Chaitanya Kumar
2023-07-25 13:15 ` Alistair Popple
2023-07-26 3:53 ` Borah, Chaitanya Kumar
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=alpine.DEB.2.20.1710161237260.1973@nanos \
--to=tglx@linutronix.de \
--cc=akataria@vmware.com \
--cc=arjan@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=petri.latvala@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=tony.luck@intel.com \
--cc=yu.c.chen@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