Created attachment 288579
attachment-30359-0.html
As of 6-DEC-2019, NXP has acquired Marvell’s Wireless business unit. You
can now reach me at ganapathi.b...@nxp.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Created attachment 286651
attachment-16293-0.html
As of 6-DEC-2019, NXP has acquired Marvell’s Wireless business unit. You
can now reach me at ganapathi.b...@nxp.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Created attachment 286459
attachment-14890-0.html
As of 6-DEC-2019, NXP has acquired Marvell’s Wireless business unit. You
can now reach me at ganapathi.b...@nxp.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Hi Verdre,
I am yet to try on my side, the reason for why change in comment#105
don't cause the issue;
Please let know your inputs on the change shared in comment#105; We will
improve the change considering different observations(comment#106, #108)
Regards,
Ganapathi
--
You received this bug n
Hi Andy,
>PCI core *does* the same (*) for you already.
OK; I see, with this change, command timeout is not recreated; without
this change, just after second iteration I see the issue(as given in
comment#103);
>Does it mean we have some race there?
I need to understand more on this; I was just t
Created attachment 285537
0001-mwifiex-set-PCIE-to-PCI_D0-power-state-on-resume
Hi Tsuchiya/Verdre,
Could please give a try with attached change;
Regards,
Ganapathi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Hi verdre,
>> went back to a clean kernel and tried disabling L1.2 to fix the command
>> timeout. While that indeed fixed the command timeout issue, the "Firmware
>> wakeup
failed" issue wasn't fixed.
could you share your changes, with which command timeout is not seen;
Regards,
Ganapathi
--
>> 1. Command timeout after second suspend could be recreated in my Surface 4;
more specific observation on this(you could cross check, if possible):
1. timeout happens after a resume, if we see below message in dmesg:
"mwifiex_pci :02:00.0: Refused to change power state, currently in D0"
2
Hi Tsuchiya/Verdre,
>- "cmd_timeout"
> This issue will occur after a second suspend like the dmesg log on
> >Comment#91 regardless of 2.4GHz/5GHz AP or power_save on/off
1. Command timeout after second suspend could be recreated in my Surface 4;
2. Logs were similar to the one in #91 &
>2. could you kindly try the same use case by disabling power_save
I mean, your use case(not #1)
Regards,
Ganapathi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi do
Hi Verdre,
Thanks for above log;
1. Could you confirm above issue is seen only in connected state:
[a] say, you keep scanning for AP but do not connect to any AP;
[b] along with #[a], you do suspend and resume;
[c] after a specific time(you could try different duration, based on how fast
you us
Hi Verdre,
Could you kindly share the dmesg logs, when the issue is recreated; You
could use below method to collect the log:
1. dmesg -c
2. echo 0x > /sys/kernel/debug/mwifiex/mlan0/debug_mask
3. while true; do dmesg -c >> dmesg.txt; done &
4. run your use case
5. share dmesg.txt once yo
Hi Verdre,
>I'm making progress with figuring out potential workarounds for this issue
>right now, seems like the "Firmware wakeup failed" error on resume indeed is
>caused by another issue (that might still be related to PCI connection/ASPM
>issues) than the command timeout
OK; Thanks for this; I
Hi Verdre,
>Or you could try out Fedora 31 beta, which should have a 5.3 kernel
Thanks for this, it worked for me;
Now, I try to recreate like below(power save enabled):
1. connect to a known AP
2. ping to AP for few seconds
3. suspend(use rtcwake) and resume
4. goto #1
I do not see the error in
Hi Verdre,
Could you give inputs on how did you get Fedora 30 installed on Surface
4; I created the image using 'dd' and tried to boot from it;It would get
to grub, after I was getting the _ cursor forever;
Regards,
Ganapathi
--
You received this bug notification because you are a member of Ker
Hi Andy/Verdre,
Last time I started working on this, I failed to fix due to different
reasons; From past few days I see still the issue is same as given in
comment#74;
>Using the CONFIG_PCIEASPM_DEBUG config option of the kernel I was able to
>track the issue down to the PCI ASPM L1.2 power savin
Hi Chatty,
Do you mean you see the error in #Comment74? (after suspending)?
Regards,
Ganapathi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in
17 matches
Mail list logo
