>>
>> The call gic_handle_irq() sounds like a hardware IRQ func/context.
>>
>> The flush_backlog() call is due to the device is being unregistered.
>>
Yes, this is the ARM interrupt controller. It appeared as if wifi was
getting torn down around this.
>> I'm surprised to see kfree_skb() being cal
On Thu, 2015-11-19 at 11:42 +0100, Jesper Dangaard Brouer wrote:
> On Thu, 19 Nov 2015 02:37:54 - subas...@codeaurora.org wrote:
>
> > We are seeing a WARN due to local_bh_disable called with interrupts
> > disabled with CONFIG_IRQSOFF_TRACER / CONFIG_PREEMPT_TRACER.
&g
On Thu, 19 Nov 2015 02:37:54 - subas...@codeaurora.org wrote:
> We are seeing a WARN due to local_bh_disable called with interrupts
> disabled with CONFIG_IRQSOFF_TRACER / CONFIG_PREEMPT_TRACER.
AFAIK this WARN happens due to a being called from hardware interrupt
c
