Re: [PATCH net-next] ibmvnic: Don't handle RX interrupts when not up.

2018-01-10 Thread Nathan Fontenot
On 01/09/2018 02:33 PM, Thomas Falcon wrote: > On 01/08/2018 10:09 AM, Nathan Fontenot wrote: >> Initiating a kdump via the command line can cause a pending interrupt >> to be handled by the ibmvnic driver when initializing the sub-CRQ >> irqs during driver initialization. >> >> NIP [d0ca34

Re: [PATCH net-next] ibmvnic: Don't handle RX interrupts when not up.

2018-01-09 Thread Thomas Falcon
On 01/08/2018 10:09 AM, Nathan Fontenot wrote: > Initiating a kdump via the command line can cause a pending interrupt > to be handled by the ibmvnic driver when initializing the sub-CRQ > irqs during driver initialization. > > NIP [d0ca34f0] ibmvnic_interrupt_rx+0x40/0xd0 [ibmvnic] > LR [c

[PATCH net-next] ibmvnic: Don't handle RX interrupts when not up.

2018-01-08 Thread Nathan Fontenot
Initiating a kdump via the command line can cause a pending interrupt to be handled by the ibmvnic driver when initializing the sub-CRQ irqs during driver initialization. NIP [d0ca34f0] ibmvnic_interrupt_rx+0x40/0xd0 [ibmvnic] LR [c8132ef0] __handle_irq_event_percpu+0xa0/0x2f0 Call