WLAN service/cell network service crashes and demands 100% cpu load after booting

[Rom4nB]

• Device: Nexus 5 (Model LG-D821, FCC ID: ZNFD821)
• Channel: Stable Channel
• Build: Ubuntu 15.04 (r2)

Steps to reproduce

1. Switch on phone: WLAN might be crashed, even also cell phone network (no cell phone network seen), flight mode does not work either -> switch off to reboot
   OR
   swtich on phone after having it charged over night

Expected behavoir

Phone boots normally, incorrect 1970 date (see other known bug for hammerhead) is swiftly swichted to correct date, mobile network and WIFI working, phone not getting warm

Actual behavior

1. Google logo seen for unusal long time
2. Ubports loading screen, App Scope loading, fetching correct date etc. takes all unusal long
3. WIFI not working (service not started)
4. Phone gets warm with 100% cpu load, phone hardly usable, doesn't even shut down properly often (shut down then forced via recovery mode)
5. after about 5 attempts to boot the phone, at one time the phone won't be a hand warmer anymore, cpu is not at 100%, cell phone network and wifi connects normally

Logfiles and additional information

Screenshot 1: cell phone network and wifi crashed during stand by -> cell phone settings not seen neither in top bar nor in settings, flight mode not working

Screenshot 2: top shows 100% cpu load caused by the process 'wlan_event_handle', note that time/date did not automatically switch from wrong '1970' date

[rubencarneiro]

Time and data bug is now fixed.
ubports/android_device_lge_hammerhead#14

[HendriXXX]

I have experienced this bug once in my N5 with ota2. Just like Rom4nB described.

[HendriXXX]

In couple of days I had again few times this hanging CPU 100%- problem. If I try to boot it normally, I have non-opening apps, phone heating, stuttering after couple reboots and sometimes it has to reboot MANY times to get it working again properly.

This workaround works for me, I reboot it first to fastboot mode and then start it from there. Phone works after first boot perfectly..

Next time I try to get some logcat print..

[Rom4nB]

I continue struggling with this bug. :/

On sunday in the morning I didn't notice instantly that phone did not boot properly, got hot, mobile network service did not connect and calls didnt come through.

After several reboots it finally worked but battery was drain to 60% (from fully charged).

At afternoon, I noticed in the pocket that the phone got warm again. I assume roaming could have caused trouble again (I was in France) - reboot and airplane mode safed me to get home with 2% battery in the evening.

Yesterday and today the same as usual that it takes several boot attempts until it works properly.

Unfortunately, the phone is very unreliable

[Rom4nB]

... sorry I accidently hit the close button. ^^

Continue: My phone is very unreliable with Ubuntu. With LineageOS or stock my N5 worked fine, so I do not think the hardware itself is damaged.

I really consider flashing LineageOS again as the phone is not really usable as a daily driver in the current state. :(

Is there a way to help you guys with further information to track this bug? My issue seems to be very similar to what HendriXXX described.

[Rom4nB]

Today, my phoen worked fine until during Podbird-ing the 100% cpu load crash caused by wl_event_handle came in.

Now I'm still trying to boot my phone properly (had several attempts now). It got stuck in the Google boot screen first, as the battery got drained too deeply by the 100%-cpu-load-crash and the Nexus 5 doesn't boot properly on low battery.

Recovery mode permitted to switch off the phone and let it charge a while. Now I can boot the phone again but with about 5 attempts now it keeps booting with crashed wl_event_handle process that consumes 100% cpu load.

I managed creating logs now but I dunno if this can help.

They are attached below.
Logs with bad booting: 100% cpu load by crashed wl_event_handle:
UTDmesg.txt
UTlogcat.txt

EDIT: Now finally my device booted properly, WIFI is working, no 100% cpu load anymore. I also created logs now, maybe the comparison can help also.
Logs with proper booting (no wl_event_handle crash):
UTDmesg.txt
UTlogcat.txt

What I noticed with my knowledge:
In the boot with crashing, wl_event_handle showed an timeout in Dmesg. In normal booting, Dmesg shows that wl_event_handle just gets started and that's it.