Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #86749 > unrolled thread

Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62!

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62! Salvatore Bonaccorso <carnil@debian.org> - 2025-04-06 11:10 +0200
    Processed: Re: Bug#1101944: linux-image-6.1.0-32-amd64: list_del  corruption ... kernel BUG at lib/list_debug.c:62! "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-04-06 11:10 +0200
    Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62! Alexis Huxley <alexishuxley@gmail.com> - 2025-04-08 08:50 +0200
      Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62! Uwe Kleine-König <ukleinek@debian.org> - 2025-04-14 10:30 +0200
        Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62! Alexis Huxley <alexishuxley@gmail.com> - 2025-04-15 08:30 +0200

#86749 — Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62!

Control: tags -1 + moreinfo

Hi Alexis,

On Wed, Apr 02, 2025 at 07:07:34PM +0200, Alexis Huxley wrote:
> Package: src:linux
> Version: 6.1.129-1
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> Not clear. System only runs KVM VMs and LXC containers.
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> System had crashed. Hardware reset required.
> 
> Content from kern.log from first crash-related entry to end below.
> 
> If you need more info, then let me know what you need.

Can you repliably trigger the issue? (if not there is little I guess
we can do). If yes which is the earliest previous kernel not exposing
the problem? 6.1.128-1? 

If you can pin point a last good and first bad revision of the Debian
kernel, and reliably reproduce the issue, I would suggest to bisect
next the upstream changes. But we first need to know if you reproduce
the issue and if you find a last good Debian revision.

Regards,
Salvatore

[toc] | [next] | [standalone]

#86750 — Processed: Re: Bug#1101944: linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62!

Processing control commands:

> tags -1 + moreinfo
Bug #1101944 [src:linux] linux-image-6.1.0-32-amd64: list_del corruption ... kernel BUG at lib/list_debug.c:62!
Added tag(s) moreinfo.

-- 
1101944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#86781

Hi Salvatore,

> Can you repliably trigger the issue? (if not there is little I guess
> we can do). If yes which is the earliest previous kernel not exposing
> the problem? 6.1.128-1? 

I had it twice, but I don't know what triggered it. I had no
crashes with 6.1.0-31, but I realise that - with only two crashes
with 6.1.0-32 and no recipe to trigger crash - that no crashes with
6.1.0-31 doesn't really prove anything. I was kinda hoping that my
crash report could contribute to a body of evidence that would help
someone more knowledgable than me to trace the source of problem.
It's fine by me if, after some time to allow others to chip in, that
you close the report with wont-fix or whatever.

Alexis

[toc] | [prev] | [next] | [standalone]

#86884

[Multipart message — attachments visible in raw view] — view raw

Hello,

On Tue, Apr 08, 2025 at 08:38:57AM +0200, Alexis Huxley wrote:
> > Can you repliably trigger the issue? (if not there is little I guess
> > we can do). If yes which is the earliest previous kernel not exposing
> > the problem? 6.1.128-1? 
> 
> I had it twice, but I don't know what triggered it. I had no
> crashes with 6.1.0-31, but I realise that - with only two crashes
> with 6.1.0-32 and no recipe to trigger crash - that no crashes with
> 6.1.0-31 doesn't really prove anything. I was kinda hoping that my
> crash report could contribute to a body of evidence that would help
> someone more knowledgable than me to trace the source of problem.
> It's fine by me if, after some time to allow others to chip in, that
> you close the report with wont-fix or whatever.

It might be a good idea to do a RAM test just to rule out a hardware
issue. (E.g. install memtest86+ which gives you a boot option to start
the memtest in grub.)

Best regards
Uwe

[toc] | [prev] | [next] | [standalone]

#86895

Hi Uwe,

> It might be a good idea to do a RAM test just to rule out a hardware
> issue. (E.g. install memtest86+ which gives you a boot option to start
> the memtest in grub.)

Overnight I ran one full pass of memtest86+ from grub, which detected no errors.

Regards,

Alexis

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web