Comment 21 for bug 1632573

This just happened to me on OTA-15. rsyslogd was using 100% CPU. dmesg is full of:

[286425.216330] *********wlanP2P_early_suspend************
[286425.216339] *********p2pEarlySuspend************
[286425.216349] ip is not avaliable.
[286425.216355] *********wlanP2P_early_suspend************
[286425.216366] *********p2pEarlySuspend************
[286425.216376] ip is not avaliable.
[286425.216385] *********wlanP2P_early_suspend************
[286425.216394] *********p2pEarlySuspend************
[286425.216401] ip is not avaliable.

/var/log/syslog contains this and a bunch of truncated lines like this:

Apr 13 13:25:37 ubuntu-phablet kernel: [2864
Apr 13 13:25:37 ubuntu-phablet kernel: [28647
Apr 13 13:25:37 ubuntu-phablet kernel: [28647
Apr 13 13:25:37 ubuntu-phablet kernel: [2864
Apr 13 13:25:37 ubuntu-phablet kernel: [28647
Apr 13 13:25:37 ubuntu-phablet kernel: [2864
Apr 13 13:25:37 ubuntu-phablet kernel: [286474
Apr 13 13:25:37 ubuntu-phablet kernel: [28647
Apr 13 13:25:37 ubuntu-phablet kernel: [2864
Apr 13 13:25:37 ubuntu-phablet kernel: [2864
Apr 13 13:25:37 ubuntu-phablet kernel: [28647
Apr 13 13:25:37 ubuntu-phablet kernel: [28647

I had used the hotspot earlier today. I thought I'd turned it off before putting my phone away, but I may have forgotten.

I heard a notification sound. The screen was blank (but on I think - faint background visible) and the power button unresponsive.

I have ssh enabled and managed to get in that way to find the logs as above. I rebooted ("sudo reboot") and saw the notification: "Low on disk space" reporting 0%.

"sudo du -hs /var/log" says 1.5G and /var/log/syslog is 1.5G so I assume the log flooding caused the secondary problem.

I did:

sudo -s
service rsyslog stop
>/var/log/syslog
service rsyslog start

to fix the problem (after the reboot).

A catch here is that with 100% CPU burn users may not notice the problem before the battery dies.