Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Kagura] Wi-Fi out of memory in driver #440

Revertron opened this issue Jul 12, 2019 · 4 comments


Copy link

commented Jul 12, 2019

Platform: Tone
Device: Kagura
Kernel version: 4.9.182-gf79dfb7cd4d3
Android version: 9 Pie

Wi-Fi stops working at all, stuck on searching for networks.

2019-07-09 14:36:06.434 1126-3495/? I/WifiService: startScan uid=1000
2019-07-09 14:36:06.442 1126-1229/? E/WificondScannerImpl: Failed to start scan, freqs=null
2019-07-09 14:36:06.443 1126-1226/? E/WifiScanRequestProxy: Scan failure received. reason: -1,description: Scan failed
2019-07-09 14:36:06.450 7650-7650/? D/WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated
2019-07-09 14:36:06.441 703-703/? E/wificond: NL80211_CMD_TRIGGER_SCAN failed: Out of memory

Wi-Fi does not show any networks, always searching. Only reboot helps.

How to reproduce
Enable Wi-Fi, connect to any network, use as normal. After some time go somewhere far from router, walk for some time (maybe some hour or two) and come back. Wi-Fi can't connect back, can't find any network.


These lines in logcat are repeating on and on.


This comment has been minimized.

Copy link

commented Jul 14, 2019

The same problem in suzu, loire platform.


This comment has been minimized.

Copy link

commented Jul 17, 2019

That's an interesting one. I have something that will probably alleviate/posticipate this issue (because it was made for another issue...) and it's currently under testing.

Anyway, can you please "cat /proc/meminfo" whenever this happens again (in the same boot, of course)? It would be interesting to know what's going on with your RAM :)


This comment has been minimized.

Copy link

commented Jul 24, 2019

I've repeated the bug, here is the meminfo:

kagura:/ $ cat /proc/meminfo
MemTotal:        2700568 kB
MemFree:           43012 kB
MemAvailable:     635916 kB
Buffers:           32252 kB
Cached:           647216 kB
SwapCached:         2796 kB
Active:          1109040 kB
Inactive:         597016 kB
Active(anon):     825408 kB
Inactive(anon):   299600 kB
Active(file):     283632 kB
Inactive(file):   297416 kB
Unevictable:       90448 kB
Mlocked:           90448 kB
SwapTotal:        255996 kB
SwapFree:         191644 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:       1116240 kB
Mapped:           532644 kB
Shmem:              8548 kB
Slab:             191604 kB
SReclaimable:      49880 kB
SUnreclaim:       141724 kB
KernelStack:       32048 kB
PageTables:        44356 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     1606280 kB
Committed_AS:   64396896 kB
VmallocTotal:   263061440 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
CmaTotal:         151552 kB
CmaFree:               0 kB

This comment has been minimized.

Copy link

commented Jul 24, 2019

Oh that's interesting. So the CMA is totally exhausted.
Great to know, we'll think about testing some stuff soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.