[205975.742039] list_del corruption. next->prev should be ff4bc0233b704c18, but was ff4bc01ac432a1b8 [205975.750965] ---[ cut here ]--- [205975.750966] kernel BUG at lib/list_debug.c:54! [205975.755518] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [205975.760848] CPU: 60 PID...
[570928.662632] list_del corruption, ffff8b3c3b76b048->prev is LIST_POISON2 (dead000000000200) [570928.662739] ---[ cut here ]--- [570928.662740] kernel BUG at lib/list_debug.c:50! [570928.662773] invalid opcode: 0000 [#1] SMP PTI [570928.662790] CPU: 2 PID: 756280 Comm: kworker/2...
WARN(entry->prev->next != entry,"list_del corruption. prev->next should be %p, ""but was %p\n", entry, entry->prev->next);WARN(entry->next->prev != entry,"list_del corruption. next->prev should be %p, ""but was %p\n", entry, entry->next->prev);__list_del(e...
entry, LIST_POISON2)||WARN(prev->next !=entry,"list_del corruption. prev->next should be %p,""but was %p\n", entry, prev->next) ||WARN(next->prev !=entry,"list_del corruption. next->prev should be %p,""but was %p\n", entry, next->prev))return; __list_del(prev, next);...
smc_lgr_cleanup_early() meant to delete the link group from the link group list, but it deleted the list head by mistake. This may cause memory corruption since we didn't remove the real link group from the list and later memseted the link group structure. We got a list corruption ...
dispose_listdispose_list - dispose of the contents of a local list*@head: the head of the list to free* Dispose-list gets a local list with local inodes in it, so it doesn't* need to worry about list corruption and SMP locks. ...
list_del corruption followd by a crash due to a possible data-race around ep->rdllist Raw [11306860.232504] list_del corruption. prev->next should be ffffa01344bb7eb0, but was 0000000000000000 [11306860.233019] ---[ cut here ]--- [11306860.233019] kernel BUG at lib/list_debug.c:53! [...
hrtimer: interrupt took 20589 ns WARNING: at lib/list_debug.c:48 list_del+0x6e/0xa0() (Not tainted) Hardware name: PowerEdge R820 list_del corruption. prev->next should be ffff882035627d90, but was ffff884069541588 [...] Pid: 40267, comm: perl Not tainted 2.6.32-642.3.1.el6.x86_...
[<ffffffffb91a7ed0>] isolate_lru_pages.isra.45+0x130/0x190 [ 2841.809455] WARNING: CPU: 2 PID: 65 at lib/list_debug.c:59 __list_del_entry+0xa1/0xd0 [ 2841.809459] list_del corruption. prev->next should be ffffefb4ac703420, but was (null) [ 2841.811177] kernel BUG at mm/...
The possible root cause for such memory corruption can be eitherfaulty hardware,3rd-party kernel modules, or akernel bug. Diagnostic Steps The panic string shows the kernel panic due to ageneral protection fault. Raw crash> sys | grep PANIC ...