Steffen Nurpmeso wrote in <20181231182229.t_LWK%steffen_at_sdaoden.eu>:
|Steffen Nurpmeso wrote in <20181228140158.FsqDX%steffen_at_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
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
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
Jan 12 00:15:00 crond: 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.
|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)
Received on Sat Jan 12 2019 - 00:32:44 UTC