[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=W6BttCyg6Pq4hdBHaQ7hYXF0-ACHiqR84X4M4WG2ppVw@mail.gmail.com>
Date: Fri, 1 Jul 2016 10:42:40 -0700
From: Doug Anderson <dianders@...omium.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Amitkumar Karwar <akarwar@...vell.com>,
Nishant Sarmukadam <nishants@...vell.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Brian Norris <computersforpeace@...il.com>,
Stephen Barber <smbarber@...omium.org>,
Kalle Valo <kvalo@...eaurora.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
netdev@...r.kernel.org
Subject: Re: [PATCH] mwifiex: mask PCIe interrupts before removal
Hi,
On Thu, Jun 30, 2016 at 3:21 PM, Brian Norris <briannorris@...omium.org> wrote:
> The PCIe driver didn't mask the host interrupts before trying to tear
> down. This causes lockups at reboot or rmmod when using MSI-X on 8997,
> since the MSI handler gets confused and locks up the system.
>
> Also tested on 8897, which does not support MSI-X (and wasn't
> experiencing this same bug). No regressions seen there.
>
> Signed-off-by: Brian Norris <briannorris@...omium.org>
> ---
> drivers/net/wireless/marvell/mwifiex/pcie.c | 6 ++++++
> 1 file changed, 6 insertions(+)
This looks very sane but isn't my area of expertise at all. However,
if my Reviewed-by is at all useful feel free to add it. I will say
that this fixes the issue of the crash at reboot time, so at least
I'll add:
Tested-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists