X-Original-To: alpine-user@lists.alpinelinux.org Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) by lists.alpinelinux.org (Postfix) with ESMTP id 9A8CAF856EA for ; Mon, 31 Dec 2018 18:22:15 +0000 (UTC) Received: by sdaoden.eu (Postfix, from userid 1000) id 730C21604A; Mon, 31 Dec 2018 19:22:15 +0100 (CET) Date: Mon, 31 Dec 2018 19:22:29 +0100 From: Steffen Nurpmeso To: alpine-user@lists.alpinelinux.org Subject: Re: [alpine-user] Kernel crashes on [edge] (1st VM kill inr 606 days!) Message-ID: <20181231182229.t_LWK%steffen@sdaoden.eu> In-Reply-To: <20181228140158.FsqDX%steffen@sdaoden.eu> References: <20181228140158.FsqDX%steffen@sdaoden.eu> Mail-Followup-To: alpine-user@lists.alpinelinux.org User-Agent: s-nail v14.9.11-123-g49d1a5c2 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Steffen Nurpmeso wrote in <20181228140158.FsqDX%steffen@sdaoden.eu>: |I am seeing kernel crashes with [edge] and 4.19.12 on my server ... |and we do have a _lot_ of messages like | | Dec 28 12:31:00 kernel: [34719.914043] list_add corruption. prev->next \ | should be next (ffff9273faffe2c0), but was ffff9273faffea40. (prev=ffff9\ | 273f75a52c0). | Dec 28 12:31:00 kernel: [34719.919121] WARNING: CPU: 1 PID: 0 at \ | lib/list_debug.c:28 __list_add_valid+0x3c/0x67 | Dec 28 12:31:00 kernel: [34719.921763] Modules linked in: sch_sfq \ | sch_htb nf_log_ipv4 nf_log_common xt_LOG xt_limit ipt_REJECT nf_reject_i\ | pv4 xt_tcpudp xt_recent xt_conn> ... | Dec 28 12:15:00 kernel: [33760.775634] Oops: 0000 [#1] SMP PTI | Dec 28 12:15:00 kernel: [33760.776726] CPU: 0 PID: 3934 Comm: iptables \ | Not tainted 4.19.12-0-vanilla #1-Alpine | Dec 28 12:15:00 kernel: [33760.777864] Hardware name: QEMU Standard \ | PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 | Dec 28 12:15:00 kernel: [33760.779111] RIP: 0010:nf_conncount_cache_free\ | +0x26/0x2f [nf_conncount] ... Out of interest after seeing the 4.19.13 announcement on Saturday i think i looked into that, and after that did not seem to mention anything regarding xt_conntrack, into the git of iptables. Indeed there have been some commits (on master branch) that could fit to list corruption about two weeks ago. Maybe it comes with 4.19.14, what do you think? I have reverted the machine in the meantime (luckily i always have c. urrent and o. ld kernels and modules, so that is easy), 4.14.89 works absolutely neatless. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---