<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DEBUG Kernel warning on Three 4G Hub E5-250MA router in Broadband</title>
    <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67620#M10777</link>
    <description>&lt;P&gt;Thanks for your reply, it's not good, but reassuring to me, in a way, that others have seen the same on different models and that it was fixed ... eventually. Hopefully I won't have to wait too long for an update !&lt;BR /&gt;&lt;BR /&gt;I guess we're in the minority as most customers never even sign into their device, that alone check the logs, so sadly logging levels is a low priority concern for an ISP.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Mar 2026 12:25:11 GMT</pubDate>
    <dc:creator>X2701</dc:creator>
    <dc:date>2026-03-19T12:25:11Z</dc:date>
    <item>
      <title>DEBUG Kernel warning on Three 4G Hub E5-250MA router</title>
      <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67605#M10774</link>
      <description>&lt;P&gt;Recently renewed &amp;amp; upgraded home broadband with new Three router and on looking at the router logs I'm seeing that it's reporting that the device is running a DEBUG kernel "unsafe for production use", which is concerning ?!&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;**********************************************************&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE&amp;nbsp; &amp;nbsp; &amp;nbsp;**&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;**&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** trace_printk() being used. Allocating extra memory.&amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;**&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** This means that this is a DEBUG kernel and it is&amp;nbsp; &amp;nbsp; &amp;nbsp;**&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** unsafe for production use.&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;**&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;**&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** If you see this message and you are not debugging&amp;nbsp; &amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** the kernel, report this immediately to your vendor!&amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;**&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; **&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE&amp;nbsp; &amp;nbsp; &amp;nbsp;**&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 13:07:35 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67605#M10774</guid>
      <dc:creator>X2701</dc:creator>
      <dc:date>2026-03-18T13:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: DEBUG Kernel warning on Three 4G Hub E5-250MA router</title>
      <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67606#M10775</link>
      <description>&lt;P&gt;We had the same issue on the Greenpacket Y5-210MU external hub,&lt;/P&gt;&lt;P&gt;There was a firmware upgrade for the external hub in January which eliminated that message&amp;nbsp; but also turned the logging level down so much that there are no longer any useful log messages&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":crying_face:"&gt;😢&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We really need something in between to see what the hub is actually doing!&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 13:21:33 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67606#M10775</guid>
      <dc:creator>MymsMan</dc:creator>
      <dc:date>2026-03-18T13:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: DEBUG Kernel warning on Three 4G Hub E5-250MA router</title>
      <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67620#M10777</link>
      <description>&lt;P&gt;Thanks for your reply, it's not good, but reassuring to me, in a way, that others have seen the same on different models and that it was fixed ... eventually. Hopefully I won't have to wait too long for an update !&lt;BR /&gt;&lt;BR /&gt;I guess we're in the minority as most customers never even sign into their device, that alone check the logs, so sadly logging levels is a low priority concern for an ISP.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 12:25:11 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67620#M10777</guid>
      <dc:creator>X2701</dc:creator>
      <dc:date>2026-03-19T12:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: DEBUG Kernel warning on Three 4G Hub E5-250MA router</title>
      <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67623#M10778</link>
      <description>&lt;P&gt;Hi I also discovered this same DEBUG Kernel message in the logs two weeks ago while trying to solve another issue with this new Three E5-250 MA hub (wireless devices on LAN are unable to communicate with each other when connected to this hub). However a firmware update may not be possible with this hub because in the web admin interface, when you click on the "update" button at the top of the screen it directs you to a non-existent menu option that cannot be selected. So good luck with that. I am very disappointed with this hub and still waiting for Three technical support to offer me a solution to my problem.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 14:48:59 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67623#M10778</guid>
      <dc:creator>Timmy1</dc:creator>
      <dc:date>2026-03-19T14:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: DEBUG Kernel warning on Three 4G Hub E5-250MA router</title>
      <link>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67639#M10781</link>
      <description>&lt;P&gt;Three apply updates to the hub remotely using a process known as TR069/CWMP,&amp;nbsp;&lt;/P&gt;&lt;P&gt;AFAIK Three have never made firmware updates available for customers to install.&lt;/P&gt;&lt;P&gt;Problems with the TR069 process have caused frequent rebbots and loss of conection for some outdoor hub users but reports had dropped in frequncy leading to hopes the problem had been fixed but a user has reported the issue today &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 22:18:37 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Broadband/DEBUG-Kernel-warning-on-Three-4G-Hub-E5-250MA-router/m-p/67639#M10781</guid>
      <dc:creator>MymsMan</dc:creator>
      <dc:date>2026-03-19T22:18:37Z</dc:date>
    </item>
  </channel>
</rss>

