From: Thomas Gleixner <tglx@linutronix.de>
To: Tariq Toukan <tariqt@mellanox.com>
Cc: Song Liu <liu.song.a23@gmail.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
Maor Gottlieb <maorg@mellanox.com>,
kernel-team@fb.com
Subject: Re: WARNING and PANIC in irq_matrix_free
Date: Mon, 28 May 2018 16:27:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1805281625260.1584@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1b4ded38-f217-fafa-d920-cddf980a685c@mellanox.com>
On Mon, 28 May 2018, Tariq Toukan wrote:
> On 28/05/2018 1:53 PM, Thomas Gleixner wrote:
> > On Fri, 25 May 2018, Song Liu wrote:
> > > On Wed, May 23, 2018 at 1:49 AM, Thomas Gleixner <tglx@linutronix.de>
> > > wrote:
> > > > On Wed, 23 May 2018, Tariq Toukan wrote:
> > > > > I have your patch merged into my internal branch, it prints the
> > > > > following:
> > > > >
> > > > > [ 4898.226258] Trying to clear prev_vector: 0
> > > > > [ 4898.226439] Trying to clear prev_vector: 0
> > > > >
> > > > > i.e. vector(0) is lower than FIRST_EXTERNAL_VECTOR.
> > > >
> > > > Could you please enable the vector and irq matrix trace points and
> > > > capture
> > > > the trace when this happens?
> >
> > Does the patch below fix it?
> >
> > Thanks,
> >
> > tglx
> >
> > 8<-------------------
> > diff --git a/arch/x86/kernel/apic/vector.c b/arch/x86/kernel/apic/vector.c
> > index bb6f7a2148d7..54af3d4884b1 100644
> > --- a/arch/x86/kernel/apic/vector.c
> > +++ b/arch/x86/kernel/apic/vector.c
> > @@ -148,6 +148,7 @@ static void apic_update_vector(struct irq_data *irqd,
> > unsigned int newvec,
> > * prev_vector for this and the offlined target case.
> > */
> > apicd->prev_vector = 0;
> > + apicd->move_in_progress = false;
> > if (!apicd->vector || apicd->vector == MANAGED_IRQ_SHUTDOWN_VECTOR)
> > goto setnew;
> > /*
> >
>
> I took it into my internal branch. Will let you know.
Note, I'd still like to see a trace w/o the patch which shows which order
of events leads to this. Even if the patch cures it, it might just paper
over it and not fixing the root cause.
Thanks,
tglx
next prev parent reply other threads:[~2018-05-28 14:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 12:07 Tariq Toukan
2018-02-20 18:11 ` Thomas Gleixner
2018-02-20 18:18 ` Thomas Gleixner
2018-02-21 11:27 ` Tariq Toukan
2018-02-22 21:38 ` Thomas Gleixner
2018-02-25 9:50 ` Tariq Toukan
2018-05-18 22:41 ` Dmitry Safonov
2018-05-18 23:43 ` Dmitry Safonov
2018-05-19 11:20 ` Thomas Gleixner
2018-05-23 7:16 ` Tariq Toukan
2018-05-23 8:49 ` Thomas Gleixner
2018-05-25 20:10 ` Song Liu
2018-05-25 21:29 ` Song Liu
2018-05-28 10:53 ` Thomas Gleixner
2018-05-28 11:17 ` Tariq Toukan
2018-05-28 14:27 ` Thomas Gleixner [this message]
2018-05-28 18:36 ` Song Liu
2018-05-28 18:34 ` Song Liu
2018-05-28 20:09 ` Thomas Gleixner
[not found] ` <3F47F523-64C5-422B-B9B0-73B8D105CF71@fb.com>
2018-05-29 8:35 ` Thomas Gleixner
2018-05-29 16:54 ` Song Liu
2018-05-30 21:56 ` Thomas Gleixner
2018-06-04 7:56 ` Dou Liyang
2018-06-04 11:17 ` Thomas Gleixner
2018-06-04 11:59 ` Dou Liyang
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.21.1805281625260.1584@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=0x7f454c46@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liu.song.a23@gmail.com \
--cc=maorg@mellanox.com \
--cc=tariqt@mellanox.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
all inboxes | Powered by JetHome®