What's new

kernel: Slab corruption

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

dahyippur

Occasional Visitor
Recently picked up a second hand ac86u and flashed merlin's latest firmware. Have not made a ton of changes , just restored factory defaults, loaded flexqos, disable 5ghz radio, couple other minor things. I noticed this in the syslog today and couldn't find any posts about it, anyone know what this means?

Mar 24 22:06:18 wlceventd: wlceventd_proc_event(507): eth5: Disassoc 70:F1:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 24 22:30:31 wlceventd: wlceventd_proc_event(526): eth5: Auth 70:F1:xx:xx:xx:xx, status: Successful (0), rssi:0
Mar 24 22:30:31 kernel: Slab corruption (Tainted: P O ): bridge_fdb_cache start=ffffffc0191babc0, len=72
Mar 24 22:30:31 kernel: 040: 00 00 00 00 6b 6b 6b a5 ....kkk.
Mar 24 22:30:31 kernel: Prev obj: start=ffffffc0191bab40, len=72
Mar 24 22:30:31 kernel: 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 24 22:30:31 kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 24 22:30:31 kernel: Next obj: start=ffffffc0191bac40, len=72
Mar 24 22:30:31 kernel: 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 24 22:30:31 kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 24 22:30:31 wlceventd: wlceventd_proc_event(536): eth5: ReAssoc 70:F1:xx:xx:xx:xx, status: Successful (0), rssi:0
Mar 24 22:30:31 dnsmasq-dhcp[17872]: DHCPREQUEST(br0) 192.168.50.5 70:f1:xx:xx:xx:xx
Mar 24 22:30:31 dnsmasq-dhcp[17872]: DHCPACK(br0) 192.168.50.5 70:f1:xx:xx:xx:xx pguru
Mar 24 22:30:31 kernel: 70:F1:xx:xx:xx:xx not mesh client, can't update it's ip
Mar 24 22:30:33 dnsmasq-dhcp[17872]: DHCPREQUEST(br0) 192.168.50.5 70:f1:xx:xx:xx:xx
Mar 24 22:30:33 dnsmasq-dhcp[17872]: DHCPACK(br0) 192.168.50.5 70:f1:xx:xx:xx:xx pguru
Mar 24 22:31:19 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 70:F1:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4), rssi:0
 
Recently picked up a second hand ac86u and flashed merlin's latest firmware. Have not made a ton of changes , just restored factory defaults, loaded flexqos, disable 5ghz radio, couple other minor things. I noticed this in the syslog today and couldn't find any posts about it, anyone know what this means?
too much gravel in the mix
 
Happened again this morning as I woke the desktop pc, very mysterious

Mar 26 03:30:00 FlexQoS: No TC modifications necessary
Mar 26 03:58:09 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Mar 26 03:58:09 kernel: br0: port 4(eth4) entered listening state
Mar 26 03:58:09 kernel: br0: port 4(eth4) entered listening state
Mar 26 03:58:11 kernel: br0: port 4(eth4) entered learning state
Mar 26 03:58:13 kernel: br0: topology change detected, propagating
Mar 26 03:58:13 kernel: br0: port 4(eth4) entered forwarding state
Mar 26 03:58:13 kernel: Slab corruption (Tainted: P O ): bridge_fdb_cache start=ffffffc015b95240, len=72
Mar 26 03:58:13 kernel: 040: 00 00 00 00 6b 6b 6b a5 ....kkk.
Mar 26 03:58:13 kernel: Prev obj: start=ffffffc015b951c0, len=72
Mar 26 03:58:13 kernel: 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 26 03:58:13 kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 26 03:58:13 kernel: Next obj: start=ffffffc015b952c0, len=72
Mar 26 03:58:13 kernel: 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 26 03:58:13 kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Mar 26 03:58:15 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.50.138 bc:ee:xx:xx:xx:xx
 
It's not hard to find out what the linux kernel slab allocator is with a web search.

I don't think the memory used by the slab allocator is swapable so it might be faulty memory hardware, or a bug in the kernel. It might be from a failure to allocate a chunk of memory from the memory reserved for the slab. You have not way of knowing unless you have the source code for the kernel component issuing the messages.
 
Last edited:

Similar threads

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