<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Huge syslog flood on wifi tethering deactivation]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">Thanks for your work on ubPorts. I detected a problem with the WiFi tethering. The /var/log/syslog is flooded with huge amount of this lines :</p>
<pre><code>Feb 20 11:17:02 ubuntu-phablet kernel: [164989.724292]*********wlanP2P_early_suspend************
Feb 20 11:17:02 ubuntu-phablet kernel: [164989.724300]*********p2pEarlySuspend************
Feb 20 11:17:02 ubuntu-phablet kernel: [164989.724307]ip is not avaliable.
</code></pre>
<p dir="auto">The time of first line seems to corresponds to the time of deactivation of tethering. The amount of messages is absolutely crazy (about 50000 ~ 60000 lines a second !) and the storage memory saturate in minutes. I noticed some lines are incomplete.</p>
<p dir="auto">Then saturated the phone become nearly unusable. Particularly it is impossible to open the "console" app to correct this problem however SSH daemon works and "sudo" too and I was able to delete this huge file (after making backup on my PC to read it). Note : after deleting the syslog don't forget to reboot to close the file's inode and free the storage.</p>
<p dir="auto">My phone is a bq Aquarius E4.5 Ubuntu Edition. The network then using tethering was not very good but works. The duration and amount of data exchanged with tethering on this session was very low (~10 minutes and &lt;1 MBytes).</p>
<p dir="auto">Thanks for ubPorts.</p>
]]></description><link>https://forums.ubports.com/topic/3859/huge-syslog-flood-on-wifi-tethering-deactivation</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Apr 2026 03:17:20 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/3859.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 24 Feb 2020 18:17:51 GMT</pubDate><ttl>60</ttl></channel></rss>