Messages in this thread | | | Date | Tue, 29 May 2018 10:35:30 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: WARNING and PANIC in irq_matrix_free |
| |
On Mon, 28 May 2018, Song Liu wrote: > > On May 28, 2018, at 1:09 PM, Thomas Gleixner <tglx@linutronix.de> wrote: > > > > 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. > > Attached is the dump I got. It seems pretty noisy, with many message lost. > > Maybe we cannot enable all trace points under irq_vectors/ and irq_matrix.
Right. Sorry, I forgot to say that we only need the irq_vectors ones which are related to vector allocation, i.e.: irq_vectors/vector_*
Thanks,
tglx
| |