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 in my_kmcdump[2aa07980000+f000]". I attached the first block I found
> in the journal after the reboot.
I see "003b" and "0007" as interruption codes. All those are page
faults (and are reported to the user space process via SIGSEGV). Aka
the process tries to access data that is not available in the page
table.
Why s390 decides to always dump them to the kernel log if the
signal is unhandled is currently over me. There is similar code on
other architectures, and also enabled by default, but I frankly have
never seen it.
Right now I have no idea what this could tell.
Bastian
--
Four thousand throats may be cut in one night by a running man.
-- Klingon Soldier, "Day of the Dove", stardate unknown
