Menu
What's new
By:
Filters Better Search

Scribe Rolling Kernel Error on AX86U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I

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!
 
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...
 
I found out another thread on the same subject, but different router...

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

www.snbforums.com

blog_emit, net_ratelimit

Hello all I find these entries along all my kernel messages. What does it mean? Thanks! May 26 09:52:54 router kernel: net_ratelimit: 18 callbacks suppressed May 26 09:52:54 router kernel: _blog_emit, blogp = 0x560 May 26 09:52:54 router kernel: _blog_emit, blogp = 0x560 May 26 09:52:54 router...
www.snbforums.com www.snbforums.com
 
Not seeing it on my AC86 with 386.1 and Scribe.
 
elorimer said:
Not seeing it on my AC86 with 386.1 and Scribe.
Click to expand...
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
 
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.
 
Citius said:
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.
Click to expand...
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:
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:
clvk07 said:
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
Click to expand...
I noticed this too. If I install scribe, I get those messages. If I use a syslog server, I get those messages as well.
 
You must log in or register to reply here.

Similar threads

B
Scribe A filter to drop kernel dcd tainted errors :
Replies
4
Views
1K
bibikalka
B
J
New install of 386.2_2, off and running with questions and errors?
Replies
4
Views
2K
JT Strickland
J
CaptnDanLKW
Scribe Syslog-ng syslog.d filter help
Replies
4
Views
1K
CaptnDanLKW
CaptnDanLKW
M
USB drive not mounted and read-only error
Replies
3
Views
2K
ColinTaylor
C
JR Godwin
Scribe AX86U - 386.1 - Logging seems to be crashing
Replies
6
Views
2K
L&LD
L&LD
Similar threads
Thread starter Title Forum Replies Date
Tarek Yag Entware RT-AC68U (armv7l Kernel: 2.6.36.4) in need for a newer "ip-full" package Asuswrt-Merlin AddOns 13
John Tetreault amtm Why does amtm install Entware armv7sf-k2.6n builds that are running the 4.1.52 kernel Asuswrt-Merlin AddOns 14
A Tailscale subnet error Asuswrt-Merlin AddOns 7
R Entware Asus-Merlin 388.8 GT-AX11000 Entware v2RayA package error Asuswrt-Merlin AddOns 2
J AdGuardHome There are tons of dnsproxy error messages occuring on syslog. Asuswrt-Merlin AddOns 2
W ntpMerlin Chronyd not starting issue "Fatal error : Could not get user/group ID of nobody" Asuswrt-Merlin AddOns 0
S Unbound fatal error: cannot prefer and disable ip6, pointless Asuswrt-Merlin AddOns 11
U Odd error installing dnscrypt 2.1.5 Asuswrt-Merlin AddOns 0
F Solved Compilation error /opt/bin/ld: cannot find Asuswrt-Merlin AddOns 1

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Staff online

Members online

Total: 867 (members: 30, guests: 837)
Top