[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1805282206440.1584@nanos.tec.linutronix.de>
Date: Mon, 28 May 2018 22:09:45 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Song Liu <songliubraving@...com>
cc: Song Liu <liu.song.a23@...il.com>,
Tariq Toukan <tariqt@...lanox.com>,
Dmitry Safonov <0x7f454c46@...il.com>,
open list <linux-kernel@...r.kernel.org>,
Maor Gottlieb <maorg@...lanox.com>,
Kernel Team <Kernel-team@...com>
Subject: Re: WARNING and PANIC in irq_matrix_free
On Mon, 28 May 2018, Song Liu wrote:
> This doesn't fix the issue with bnxt. Here is a trace with this patch:
That's just the backtrace which is not really helpful. The real question is
what leads to this scenaria.
What I was asking for is to enable the irq_vector and irq_matrix trace
points along with ftrace_dump_on_oops. The latter dumps the trace buffer
when the problem happens and that should give us a hint what actually
causes that.
Thanks,
tglx
Powered by blists - more mailing lists