X-Original-To: alpine-user@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id C377EF85670 for ; Sat, 12 Jan 2019 11:54:28 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 3B9219E1D82; Sat, 12 Jan 2019 11:54:28 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 149649E1C8E; Sat, 12 Jan 2019 11:54:26 +0000 (GMT) Date: Sat, 12 Jan 2019 12:54:21 +0100 From: Natanael Copa To: Steffen Nurpmeso Cc: alpine-user@lists.alpinelinux.org Subject: Re: [alpine-user] Kernel crashes on [edge] (1st VM kill inr 606 days!) Message-ID: <20190112125421.2330ddc9@ncopa-desktop.copa.dup.pw> In-Reply-To: <20190111233244.B2bX-%steffen@sdaoden.eu> References: <20181228140158.FsqDX%steffen@sdaoden.eu> <20181231182229.t_LWK%steffen@sdaoden.eu> <20190111233244.B2bX-%steffen@sdaoden.eu> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 12 Jan 2019 00:32:44 +0100 Steffen Nurpmeso wrote: > Hello. > > Steffen Nurpmeso wrote in <20181231182229.t_LWK%steffen@sdaoden.eu>: > |Steffen Nurpmeso wrote in <20181228140158.FsqDX%steffen@sdaoden.eu>: > ||I am seeing kernel crashes with [edge] and 4.19.12 on my server > ... > |Out of interest after seeing the 4.19.13 announcement on Saturday > ... > |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. > > I have updated to 4.19.14, and the issue still exists on my server > VM: > > crit: > Dec 29 00:15:01 kernel: [23338.689515] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 > Jan 12 00:15:00 kernel: [36690.017115] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 > warn: > Jan 12 00:15:00 kernel: [36690.023028] Oops: 0000 [#1] SMP PTI > Jan 12 00:15:00 kernel: [36690.024368] CPU: 0 PID: 3708 Comm: iptables Not tainted 4.19.14-0-vanilla #1-Alpine > Jan 12 00:15:00 kernel: [36690.025679] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 > Jan 12 00:15:00 kernel: [36690.027056] RIP: 0010:nf_conncount_cache_free+0x26/0p > messages: > Jan 12 00:15:00 crond[2046]: USER root pid 3677 cmd run-parts /etc/periodic/12hourly > Jan 12 00:15:00 kernel: [36690.021645] PGD 0 P4D 0 > > That periodic script outputs sort(1)ed entries from xt_recent, and > shows the state of the firewall. > I have reverted to 4.14.89. I have never done this, but i think > this should be reported to Linux kernel list, then? pffffff... > Ciao and a nice weekend. Please report this upstream. https://bugzilla.kernel.org/ -nc --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---