From: Dan Lenski <dlenski@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup
Date: Sun, 22 May 2016 23:02:40 +0000 (UTC) [thread overview]
Message-ID: <nhtdqf$te$1@ger.gmane.org> (raw)
In-Reply-To: CAOw_LSH8yGT+OoJU=a23B32mZ+qLkNuronB+vqZ5SaBRAG-fQw@mail.gmail.com
Daniel Lenski wrote:
> - Hypothesis: since the rtl8xxxu driver does not explicitly power off the
> device before attempting to power it on, if it boots up in an unknown
> state, it will remain in this state until explicitly power-cycled.
I am now pretty sure that this is the true cause of fimware not starting.
I found that I can induce "Firmware failed to start" by using kexec --force to restart the kernel without a clean shutdown.
After this incomplete reboot, the firmware always fails to start. I guess the rtl8xxxu hardware must be left in some unknown state:
[ 2.794118] usb 1-1.4: Vendor: Realtek
[ 2.794121] usb 1-1.4: Product: 802.11n WLAN Adapter
[ 2.794124] usb 1-1.4: RTL8723AU rev B (TSMC) 1T1R, TX queues 2, WiFi=1, BT=1, GPS=0, HI PA=0
[ 2.794125] usb 1-1.4: RTL8723AU MAC: 20:16:d8:ce:5e:29
[ 2.794127] usb 1-1.4: rtl8xxxu: Loading firmware rtlwifi/rtl8723aufw_B_NoBT.bin
[ 2.797136] usb 1-1.4: Firmware revision 31.0 (signature 0x2302)
[ 2.878370] usb 1-1.4: Firmware checksum poll completed after 0 loops
[ 4.153567] usb 1-1.4: Firmware failed to start after 5000 loops
After power-off and retry of rtl8xxxu_init_device, it then starts correctly:
[ 4.153569] usb 1-1.4: Failed to init device, will retry 5 more times.
[ 4.746357] usb 1-1.4: Firmware checksum poll completed after 0 loops
[ 4.752456] usb 1-1.4: Firmware started after 23 loops
[ 5.194825] usb 1-1.4: Enabling HT_20_40 on the 2.4GHz band
Should I submit a new patch to retry rtl8xxxu_init_device after power cycling?
Thanks,
Dan
next prev parent reply other threads:[~2016-05-22 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:57 [PATCH] rtl8xxxu: increase polling timeout for firmware startup Dan Lenski
2016-05-18 17:57 ` [PATCH] rtl8xxxu: Increase default " Dan Lenski
2016-05-19 2:08 ` [PATCH] rtl8xxxu: increase " Jes Sorensen
2016-05-20 4:51 ` Daniel Lenski
2016-05-20 14:08 ` Jes Sorensen
2016-05-20 20:50 ` Daniel Lenski
2016-05-20 20:54 ` Daniel Lenski
2016-05-21 3:13 ` Jes Sorensen
2016-05-21 2:40 ` Daniel Lenski
2016-05-22 23:02 ` Dan Lenski [this message]
2016-05-23 19:24 ` Jes Sorensen
2016-05-23 21:47 ` Daniel Lenski
2016-05-31 15:04 ` Jes Sorensen
2016-05-31 17:59 ` Daniel Lenski
2016-05-31 18:24 ` Jes Sorensen
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='nhtdqf$te$1@ger.gmane.org' \
--to=dlenski@gmail.com \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.