Tainted message from kernel, leading to panic/crash

I am seeing this fairly regularly these days. Any idea where I should investigate?

It is an old machine, Q8800 on an old Battle Axe MB. Running syncthing 0.14.37-rc.1. Same problem on earlier versions.

-jem

 WARNING: CPU: 3 PID: 23784 at net/ipv4/tcp.c:1662 tcp_recvmsg+0x4e9/0xa80
Aug 21 11:21:36 ratbert kernel: recvmsg bug: copied 13DEBB69 seq 13DEC111 rcvnxt 1420AB98 fl 0
Aug 21 11:21:36 ratbert kernel: CPU: 3 PID: 23784 Comm: syncthing Tainted: G        W       4.8.17-hardened-r2 #4
Aug 21 11:21:36 ratbert kernel: Hardware name:                  /D975XBX2, BIOS BX97520J.86A.2777.2007.0805.1747 08/05/2007
Aug 21 11:21:36 ratbert kernel:  0000000000000246 b8a20adf4924101e ffffffff813a8da3 ffffffff819c3f5b
Aug 21 11:21:36 ratbert kernel:  b8a20adf4924101e ffff880225b57ca8 0000000000000000 ffffffff8107529f
Aug 21 11:21:36 ratbert kernel:  ffff8801386ff500 ffff880225b57d00 ffff880111311808 0000000000000000
Aug 21 11:21:36 ratbert kernel: Call Trace:
Aug 21 11:21:36 ratbert kernel:  [<ffffffff813a8da3>] ? dump_stack+0x64/0xa1
Aug 21 11:21:36 ratbert kernel:  [<ffffffff8107529f>] ? __warn+0xaf/0xd0
Aug 21 11:21:36 ratbert kernel:  [<ffffffff8107531a>] ? warn_slowpath_fmt+0x5a/0x80
Aug 21 11:21:36 ratbert kernel:  [<ffffffff8166f5c9>] ? tcp_recvmsg+0x4e9/0xa80
Aug 21 11:21:36 ratbert kernel:  [<ffffffff810da3ee>] ? futex_wake+0x8e/0x170
Aug 21 11:21:36 ratbert kernel:  [<ffffffff81697796>] ? inet_recvmsg+0x76/0xa0
Aug 21 11:21:36 ratbert kernel:  [<ffffffff815ecc36>] ? sock_read_iter+0x96/0xf0
Aug 21 11:21:36 ratbert kernel:  [<ffffffff81165ade>] ? __vfs_read+0xde/0x130
Aug 21 11:21:36 ratbert kernel:  [<ffffffff81165bf1>] ? vfs_read+0xc1/0x1b0
Aug 21 11:21:36 ratbert kernel:  [<ffffffff8116613d>] ? sys_read+0x4d/0xc0
Aug 21 11:21:36 ratbert kernel:  [<ffffffff8171681f>] ? entry_SYSCALL_64_fastpath+0x13/0x93
Aug 21 11:21:36 ratbert kernel: ---[ end trace 6faae4a3296b7787 ]---

Kernel bug or hardware issue (bad memory?) is my guess.

Yup. Yanked some RAM, problem seems to have cleared.

-jem

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.