From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Stable <stable@vger.kernel.org>
Subject: Re: rtlwifi: rtl8821ae: Fix system lockups on boot
Date: Sat, 3 Oct 2015 06:44:32 +0000 (UTC) [thread overview]
Message-ID: <20151003064432.1B0BD13FA34@smtp.codeaurora.org> (raw)
In-Reply-To: <1443804270-3830-1-git-send-email-Larry.Finger@lwfinger.net>
> In commit 1277fa2ab2f9 ("rtlwifi: Remove the clear interrupt routine from all
> drivers"), the code that cleared all interrupt enable bits before setting them
> was removed for all PCI drivers. This fixed an issue that caused TX to be
> blocked for 3-5 seconds. On some RTL8821AE units, this change causes soft
> lockups to occur on boot. For that reason, the portion of the earlier commit
> that applied to rtl8821ae is reverted. Kernels 4.1 and newer are affected.
>
> See http://marc.info/?l=linux-wireless&m=144373370103285&w=2 and
> https://bugzilla.opensuse.org/show_bug.cgi?id=944978 for two cases where
> this regression affected user systems. Note that this bug does not appear on
> any of the developer's setups. For those users whose systems are affected
> by the TX blockage, but do not lock up on boot, a module parameter is added
> to disable the interrupt clear
>
> Fixes: 1277fa2ab2f9 ("rtlwifi: Remove the clear interrupt routine from all drivers")
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.kernel.org> [V4.1+]
Thanks, applied to wireless-drivers.git.
Kalle Valo
prev parent reply other threads:[~2015-10-03 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 16:44 [PATCH] rtlwifi: rtl8821ae: Fix system lockups on boot Larry Finger
2015-10-03 6:44 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151003064432.1B0BD13FA34@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).