From: Alexis Huxley <alexishuxley@gmail.com>
To: "Uwe Kleine-König" <ukleinek@debian.org>
Cc: Matthew Wilcox <willy@infradead.org>,
1101944@bugs.debian.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: Bug#1101944: list_del corruption ... kernel BUG at lib/list_debug.c:62!
Date: Thu, 1 May 2025 14:52:05 +0200 [thread overview]
Message-ID: <20250501125205.im2r3k7t575g4ztq@sugo.pasta.net> (raw)
In-Reply-To: <pasokojf3peylxcuearrrqjfbpgqm3k37kpxnm7sxfpgxfm5b5@puxeitmfbzoa>
Hi Uwe,
> On Wed, Apr 23, 2025 at 01:19:21PM +0100, Matthew Wilcox wrote:
> > On Wed, Apr 23, 2025 at 10:52:27AM +0200, Uwe Kleine-König wrote:
> >
> > [trimmed all the irrelevant garbage from the start of each line]
>
> As Matthew pointed out the output of the CHECK_DATA_CORRUPTION would be
> interesting. Can you please check if you can find this line still in
> your journal?
I have nightly backups of the machine covering the period when the
crash happened, but I do not find 'corrupt' in a case insensitive
search of uncompressed or compressed files in /var/log of the backup
of the next night or the night after that.
journalctl on the machine itself does not go back that far.
At this point it's fine for me if you want to mark this wonfix or
cantfix or whatever: the bug is recorded and searchable and I'm not
able to further help you to help me; if anybody else encounters the
problem then the logs might be useful reference.
Alexis
prev parent reply other threads:[~2025-05-01 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 8:52 Uwe Kleine-König
2025-04-23 12:19 ` Matthew Wilcox
2025-04-30 19:17 ` Bug#1101944: " Uwe Kleine-König
2025-05-01 12:52 ` Alexis Huxley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250501125205.im2r3k7t575g4ztq@sugo.pasta.net \
--to=alexishuxley@gmail.com \
--cc=1101944@bugs.debian.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=ukleinek@debian.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox