Your message dated Sun, 5 Jul 2020 16:43:44 +0200 with message-id <CAGpfsQ1u5LMtQjbm6_5Zdq7jhugxuCs74-tXB92sqyZVPhzJ5A@mail.gmail.com> and subject line has caused the Debian Bug report #922488, regarding linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 922488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation
- From: Ralf Jung <post@ralfj.de>
- Date: Sun, 17 Feb 2019 00:01:26 +0100
- Message-id: <155035808650.26023.3669908555112132003.reportbug@r-thinktop>
Package: linux-image-4.9.0-8-amd64 Version: 4.9.144-3 Severity: critical Justification: breaks the whole system Dear Maintainer, after installing the kernel updates that got released to Debian stable earlier today or yesterday, we saw all the three updated systems fail in the same way: after 3-5h, they stop responding. We managed to grab a picture of the kernel console on one of them, which showed a kernel panic in the IPv6 stack: https://imgur.com/7Teb8BV The topmost stack items are (hoping I got no typos) __pskb_pull_tail ip6_dst_lookup_tail _decode_session6 __xfrm_decode_session icmpv6_route_lookup icmp6_send That system was using the kernel this bug is reported against (linux-image-4.9.0-8-amd64 4.9.144-3). The other two affected systems used a backports kernel instead (linux-image-4.19.0-0.bpo.2-amd65 4.19.16-1~bpo9+1). Unfortunately we have no console access there, all we can do there is a hard reboot from the web interface. These servers are all operating as gateway servers for our Freifunk network, meaning they mostly forward traffic and their network setup is very non-standard. Please let me know if there is any configuration details that would be helpful to track this down. Kind regards, Ralf
--- End Message ---
--- Begin Message ---
- To: 922488-close@bugs.debian.org
- Subject:
- From: Fabio Pedretti <fabio.pedretti@unibs.it>
- Date: Sun, 5 Jul 2020 16:43:44 +0200
- Message-id: <CAGpfsQ1u5LMtQjbm6_5Zdq7jhugxuCs74-tXB92sqyZVPhzJ5A@mail.gmail.com>
Source-Version: 4.9.210-1 Seems fixed by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.9.229&id=f99a93352471791351d67b4f56a7ac891ec1b6aa which was included in 4.9.193: https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.193 and Debian 4.9.210-1 -- ing. Fabio Pedretti Responsabile U.O.C. "Reti, Sistemi e Sicurezza Informatica" https://www.unibs.it/node/4305 Università degli Studi di Brescia Via Valotti, 9 - 25121 Brescia E-mail: fabio.pedretti@unibs.it -- Informativa sulla Privacy: http://www.unibs.it/node/8155 <http://www.unibs.it/node/8155>
--- End Message ---