AU86U - Merlin 386.1 - System Log errors

  • 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.

HotWheels

New Around Here
I updated my 86U to Merlin 386.1 a few days ago and everything seems to be working fine. I was checking logs and notice this repeating block of errors (log level is set to critical): Any input ?

Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:12 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:18 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:19 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:19 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:28 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:42 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:47 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:48 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:51 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:51 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:51 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:51 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:51 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:51 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:53 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:54 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:54 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:59 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:59 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:59 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:59 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:59 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:59 kernel: jffs2: Error garbage collecting node at 02600000!
 

Treadler

Very Senior Member
I updated my 86U to Merlin 386.1 a few days ago and everything seems to be working fine. I was checking logs and notice this repeating block of errors (log level is set to critical): Any input ?

Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:08 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:12 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:16 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:17 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:18 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:19 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:19 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:28 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:38 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:42 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:47 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:48 kernel: protocol 0800 is buggy, dev eth5
Feb 8 15:20:51 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:51 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:51 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:51 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:51 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:51 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:53 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:54 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:54 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:54 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:55 kernel: protocol 86dd is buggy, dev eth5
Feb 8 15:20:59 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:59 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:59 kernel: jffs2: Error garbage collecting node at 02600000!
Feb 8 15:20:59 kernel: jffs2: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Feb 8 15:20:59 kernel: jffs2: jffs2_reserve_space_gc of 196 bytes for garbage_collect_dnode failed: -28
Feb 8 15:20:59 kernel: jffs2: Error garbage collecting node at 02600000!

Shift your guest network/s from position 1, to position 2.
i.e shift them to the right on the guest network page.
Will fix ‘some’ of your error messages.
 

HotWheels

New Around Here
Shift your guest network/s from position 1, to position 2.
i.e shift them to the right on the guest network page.
Will fix ‘some’ of your error messages.
Moving in over seemed to get rid of some of the error, that is rather strage. I just went ahead and did a hard reset and it has been a long time and several fw updates.
 

eibgrad

Very Senior Member
Moving in over seemed to get rid of some of the error, that is rather strage. I just went ahead and did a hard reset and it has been a long time and several fw updates.

There are numerous known issues w/ Guest #1. IMO, it's just best for everyone to avoid it until the next release.
 

Similar threads

Sign Up For SNBForums Daily Digest

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