Scribe Rolling Kernel Error on AX86U

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

isr25

Regular Contributor
Hi, I know it's still an alpha, but I installed Scribe on 386.1 Alpha 4 for AX86U and I am getting a rolling kernel error lines multiple times as below.

kernel: _blog_emit, blogp = 0x6
kernel: _blog_emit, blogp = 0x4
kernel: _blog_emit, blogp = 0x2240
kernel: _blog_emit, blogp = 0x1a68
kernel: _blog_emit, blogp = 0x2

The kernel error message will only disappear after removing scribe. Any thoughts on what I should do? Or should I just wait until the final release of 386.1 - I'm ok to wait, just wanted to put it out here. Thanks!
 

Rassal

Occasional Visitor
I am also using an AX86U and on 386.1 final release, with Scribe also, and i am seeing the same thing on my side...

Feb 5 09:13:04 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Feb 5 09:13:04 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Feb 5 09:14:04 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:04 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:04 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:04 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:04 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:10 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:11 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:14:12 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:15:16 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:15:38 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:27 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:27 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2360
Feb 5 09:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:44 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:44 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:44 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:44 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4
Feb 5 09:16:47 RT-AX86U kernel: _blog_emit, blogp = 0x4

And that's over a 2min period... but, also, i don't see any impact on the overall functionality of the Router...

If someone has a clue...
 

Rassal

Occasional Visitor
I found out another thread on the same subject, but different router...

Dunno if it applies directly to the AX86U... see for yourself...

 

elorimer

Very Senior Member
Not seeing it on my AC86 with 386.1 and Scribe.
 

isr25

Regular Contributor
Not seeing it on my AC86 with 386.1 and Scribe.
So far, only afflicting the AX86U with scribe installed - never had this come up on my old AC86U. From what I'm reading, it's just debugging output from Broadcom code, and harmless, although it's totally spamming the log
 

Citius

Occasional Visitor
I installed Scribe and the scribe WebUI today. And it was not showing the "kernel: _blog_emit, blogp" in all day. Then the kids cane home with their ipads, iPhones, and laptops. And the wifi dropped on My Google Home and Chromecast. And i started having problems with the wifi om both 2.4ghz and 5ghz. I noticed the 5ghz was not complying to the channel and bandwith settings and was interferring with 2.4ghz. so i started the wifi radar logging to see what was wrong. I did sonen changes but Still hade issues with the 5ghz so i changed it to auto to see if it would change ro some better channel and bandwith and began to look att the channel statistics again. It got better and i Saw it going ro 80 MHz and bo moore unstability but then i hade intermittent freeze in the wifi. So i looked att the system logs and found the kernel: _blog_emit, blogp just going on over and over again.
It seems this is specifik to the RT-AX86U. I Will remove Scribe lager and see what happens.
 

Argo

New Around Here
I installed Scribe and the scribe WebUI today. And it was not showing the "kernel: _blog_emit, blogp" in all day. Then the kids cane home with their ipads, iPhones, and laptops. And the wifi dropped on My Google Home and Chromecast. And i started having problems with the wifi om both 2.4ghz and 5ghz. I noticed the 5ghz was not complying to the channel and bandwith settings and was interferring with 2.4ghz. so i started the wifi radar logging to see what was wrong. I did sonen changes but Still hade issues with the 5ghz so i changed it to auto to see if it would change ro some better channel and bandwith and began to look att the channel statistics again. It got better and i Saw it going ro 80 MHz and bo moore unstability but then i hade intermittent freeze in the wifi. So i looked att the system logs and found the kernel: _blog_emit, blogp just going on over and over again.
It seems this is specifik to the RT-AX86U. I Will remove Scribe lager and see what happens.
It's also happening on my RT-AX56U connected to 2 AiMesh Nodes (AC66U_B1). Been having a lot of connectivity issues that only seem to last a 2-3 minutes, but happens often throughout the day. I am however, not using Scribe. Is it possible Scribe is not the issue in your cases?
 
Last edited:

clvk07

Senior Member
getting these messages using papertrail. I see these messages in the papert dashboard


Feb 14 15:20:03 kernel _blog_emit, blogp = 0x2

Feb 14 15:20:37 kernel _blog_emit, blogp = 0x2

Feb 14 15:23:37 kernel _blog_emit, blogp = 0x2

Feb 14 15:30:46 kernel _blog_emit, blogp = 0x2


But the Asus log doesnt show them at the same time.

Feb 14 15:31:43 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d2:f6:98:00:17:10:95:6e:16:08:00 SRC=103.145.13.58 DST=1XX.2XX.23.164 LEN=40 TOS=0x08 PREC=0x20 TTL=241 ID=3648 PROTO=TCP SPT=53015 DPT=50802 SEQ=190177174 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Feb 14 15:31:57 kernel: [BLOCKED - INBOUND]


asus log settings both to notice. 386.1 AX86u
 
Last edited:

isr25

Regular Contributor
getting these messages using papertrail. I see these messages in the papert dashboard


Feb 14 15:20:03 kernel _blog_emit, blogp = 0x2

Feb 14 15:20:37 kernel _blog_emit, blogp = 0x2

Feb 14 15:23:37 kernel _blog_emit, blogp = 0x2

Feb 14 15:30:46 kernel _blog_emit, blogp = 0x2


But the Asus log doesnt show them at the same time.

Feb 14 15:31:43 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d2:f6:98:00:17:10:95:6e:16:08:00 SRC=103.145.13.58 DST=1XX.2XX.23.164 LEN=40 TOS=0x08 PREC=0x20 TTL=241 ID=3648 PROTO=TCP SPT=53015 DPT=50802 SEQ=190177174 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Feb 14 15:31:57 kernel: [BLOCKED - INBOUND]


asus log settings both to notice. 386.1 AX86u
I noticed this too. If I install scribe, I get those messages. If I use a syslog server, I get those messages as well.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top