Control: found -1 6.10.6-1~bpo12+1
Control: clone -1 -2
Control: retitle -2 s390x fails with vm.panic_on_oom=1 & kernel.panic=10
Hi,
On 18-07-2024 08:06, Paul Gevers wrote:
However, that doesn't seem to work on our s390x host as it seems to
freeze instead. Is this something known? Something I'm
Hi waldi,
On 24-07-2024 10:57 a.m., Bastian Blank wrote:
On Thu, Jul 18, 2024 at 08:06:46AM +0200, Paul Gevers wrote:
However, that doesn't seem to work on our s390x host as it seems to freeze
instead. Is this something known? Something I'm doing wrong (E.g. these
options behaving differently o
On Thu, Jul 18, 2024 at 08:06:46AM +0200, Paul Gevers wrote:
> However, that doesn't seem to work on our s390x host as it seems to freeze
> instead. Is this something known? Something I'm doing wrong (E.g. these
> options behaving differently on s390x)? Is this a s390x kernel bug?
This now points
Hi
On Sun, Jul 14, 2024 at 09:22:32AM +0200, Paul Gevers wrote:
> Today I restarted the s390x host of ci.d.n because I lost access. I
> inspected the journal and noticed there were a lot kernel messages (several
> tens to hundreds per day) like "User process fault: interruption code 003b
> ilc:3 i
Hi all,
On Sun, 14 Jul 2024 09:22:32 +0200 Paul Gevers wrote:
Today I restarted the s390x host of ci.d.n because I lost access.
I have been fighting with the host for several days now, and I think I
finally found the culprit. Several days ago I configured the host to do:
# panic kernel on O
Package: src:linux
Version: 6.7.12-1~bpo12+1
X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org
Severity: normal
X-Debbugs-Cc: elb...@debian.org
Hi linux maintainers,
Today I restarted the s390x host of ci.d.n because I lost access. I
inspected the journal and noticed there
6 matches
Mail list logo
