Random crashes on Intel Nuc running Docker

Hello,

Not sure if this is the right spot for this. Please redirect me if not.

I am having issues on my Clear Linux installed on Intel Nuc8i5BEH.

I have random crashes, which looks like to be more frequent just after an update of the system.

Can someone help me with that?

Here the output of the error:

Aug 02 17:05:37 myyqo kernel: CPU: 2 PID: 19843 Comm: docker-runc Tainted: G        W         5.2.4-810.native #1
Aug 02 17:05:37 myyqo kernel: Hardware name: Intel(R) Client Systems NUC8i5BEH/NUC8BEB, BIOS BECFL357.86A.0071.2019.0510.1505 05/10/2019
Aug 02 17:05:37 myyqo kernel: RIP: 0010:__list_del_entry_valid+0x59/0xb0
Aug 02 17:05:37 myyqo kernel: Code: 75 4f 48 8b 52 08 48 39 f2 75 5e b8 01 00 00 00 5d 31 d2 89 d6 89 d7 41 89 d0 c3 48 89 fe 48 c7 c7 f8 71 80 a0 e8 b6 28 af ff <0f> 0b 5d 31 c0 31 d2 89 d6 89 d7 41 89 d0 c3 48 89 fe 4c 89 c2 48
Aug 02 17:05:37 myyqo kernel: RSP: 0018:ffffbaf7434b3b78 EFLAGS: 00010096
Aug 02 17:05:37 myyqo kernel: RAX: 0000000000000000 RBX: ffff9b3883afbf40 RCX: 0000000000000000
Aug 02 17:05:37 myyqo kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Aug 02 17:05:37 myyqo kernel: RBP: ffffbaf7434b3b78 R08: 0000000000000000 R09: 0000000000000000
Aug 02 17:05:37 myyqo kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffee030f21b9c0
Aug 02 17:05:37 myyqo kernel: R13: ffff9b3961013400 R14: 0000000000000003 R15: ffffbaf7434b3bc0
Aug 02 17:05:37 myyqo kernel: FS:  0000000000000000(0000) GS:ffff9b3a6da80000(0000) knlGS:0000000000000000
Aug 02 17:05:37 myyqo kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 02 17:05:37 myyqo kernel: CR2: 000056355b3b6989 CR3: 000000031aa0a001 CR4: 00000000003606e0
Aug 02 17:05:37 myyqo kernel: Call Trace:
Aug 02 17:05:37 myyqo kernel:  release_pages+0x19d/0x420
Aug 02 17:05:37 myyqo kernel:  free_pages_and_swap_cache+0xa5/0xc0
Aug 02 17:05:37 myyqo kernel:  tlb_flush_mmu+0xb5/0x170
Aug 02 17:05:37 myyqo kernel:  tlb_finish_mmu+0x3d/0x80
Aug 02 17:05:37 myyqo kernel:  exit_mmap+0xed/0x170
Aug 02 17:05:37 myyqo kernel:  mmput+0x6c/0x130
Aug 02 17:05:37 myyqo kernel:  do_exit+0x2ae/0x790
Aug 02 17:05:37 myyqo kernel:  do_group_exit+0x36/0xa0
Aug 02 17:05:37 myyqo kernel:  get_signal+0x16c/0x840
Aug 02 17:05:37 myyqo kernel:  ? do_futex+0x12b/0x530
Aug 02 17:05:37 myyqo kernel:  do_signal+0x2f/0x270
Aug 02 17:05:37 myyqo kernel:  ? __se_sys_futex+0x12c/0x160
Aug 02 17:05:37 myyqo kernel:  ? __set_current_blocked+0x3d/0x60
Aug 02 17:05:37 myyqo kernel:  exit_to_usermode_loop+0x98/0xc0
Aug 02 17:05:37 myyqo kernel:  do_syscall_64+0x1a7/0x1f0
Aug 02 17:05:37 myyqo kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 02 17:05:37 myyqo kernel: RIP: 0033:0x56355b3b69b3
Aug 02 17:05:37 myyqo kernel: Code: Bad RIP value.
Aug 02 17:05:37 myyqo kernel: RSP: 002b:00007f9417151db8 EFLAGS: 00000286 ORIG_RAX: 00000000000000ca
Aug 02 17:05:37 myyqo kernel: RAX: fffffffffffffe00 RBX: 000000c000064000 RCX: 000056355b3b69b3
Aug 02 17:05:37 myyqo kernel: RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000056355baa0418
Aug 02 17:05:37 myyqo kernel: RBP: 00007f9417151e00 R08: 0000000000000000 R09: 0000000000000000
Aug 02 17:05:37 myyqo kernel: R10: 0000000000000000 R11: 0000000000000286 R12: 000000c000066180
Aug 02 17:05:37 myyqo kernel: R13: 00007ffce0c1feaf R14: 0000000000000000 R15: 00007f9417152700
Aug 02 17:05:37 myyqo kernel: ---[ end trace aeb57fe52a9584be ]---
Aug 02 17:05:37 myyqo kernel: ------------[ cut here ]------------
Aug 02 17:05:37 myyqo kernel: list_del corruption, ffffee030c8201c8->next is LIST_POISON1 (dead000000000100)

Thanks

I had similar problems with my 8th gen NUC. Installing the latest bios/firmware updates fixed it.

3 Likes

Thanks pceiley.

I have tried to upgrade to the last firmware. I already upgraded in May (071), but there was a new one (073).

Let’s see if it fixes it :slight_smile:

Do you know the version you had issue with and the version which fixed it?

This should be the first thing to check out, before trying anything else.

looks like the new bios firmware fix it :slight_smile: thanks

No worries - glad it helped!