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


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

Bug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2025-01-13 23:00 +0100
Last post2025-01-16 09:20 +0100
Articles 3 — 2 participants

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#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters Salvatore Bonaccorso <carnil@debian.org> - 2025-01-13 23:00 +0100
    Processed: Re: Bug#1092960: linux-image-6.1.0-29-amd64: Kernel  OOPS when specifying ZRAM block device parameters "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-01-13 23:00 +0100
    Bug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters Salvatore Bonaccorso <carnil@debian.org> - 2025-01-16 09:20 +0100

#85127 — Bug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-01-13 23:00 +0100
SubjectBug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters
Message-ID<K4ADv-8I8o-9@gated-at.bofh.it>
Control: forwarded -1 https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/
Control: tags -1 + upstream

Hi,

On Tue, Jan 14, 2025 at 12:25:06AM +0300, Pavel Frolov wrote:
> Package: src:linux
> Version: 6.1.123-1
> Severity: normal
> X-Debbugs-Cc: radjah@yandex.ru
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
>    Command "modprobe zram" create /dev/zram0
>    Command "/sbin/zramctrl -s 1G -f" fail
>    systemd-zram-generator do the same
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    Use previous version of kernel (6.1.0-28)
> 
>    * What was the outcome of this action?
>    Kernel log contains errors and trace. Block device not working. Module "zram" can not be removed without reboot.
>  
>    * What outcome did you expect instead?
>    Successfully creating a 1GB block device

Yes, there is a zram related regression in at least the 6.1.y upstream
stable series, cf. https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/

Regards,
Salvatore

[toc] | [next] | [standalone]


#85128 — Processed: Re: Bug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-01-13 23:00 +0100
SubjectProcessed: Re: Bug#1092960: linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters
Message-ID<K4ADv-8I8o-11@gated-at.bofh.it>
In reply to#85127
Processing control commands:

> forwarded -1 https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/
Bug #1092960 [src:linux] linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters
Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/'.
> tags -1 + upstream
Bug #1092960 [src:linux] linux-image-6.1.0-29-amd64: Kernel OOPS when specifying ZRAM block device parameters
Ignoring request to alter tags of bug #1092960 to the same tags previously set

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

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


#85157

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-01-16 09:20 +0100
Message-ID<K5tgB-9jE4-1@gated-at.bofh.it>
In reply to#85127
Source: linux
Source-Version: 6.1.124-1

Hi,

On Mon, Jan 13, 2025 at 10:46:02PM +0100, Salvatore Bonaccorso wrote:
> Control: forwarded -1 https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/
> Control: tags -1 + upstream
> 
> Hi,
> 
> On Tue, Jan 14, 2025 at 12:25:06AM +0300, Pavel Frolov wrote:
> > Package: src:linux
> > Version: 6.1.123-1
> > Severity: normal
> > X-Debbugs-Cc: radjah@yandex.ru
> > 
> > Dear Maintainer,
> > 
> >    * What led up to the situation?
> >    Command "modprobe zram" create /dev/zram0
> >    Command "/sbin/zramctrl -s 1G -f" fail
> >    systemd-zram-generator do the same
> > 
> >    * What exactly did you do (or not do) that was effective (or
> >      ineffective)?
> >    Use previous version of kernel (6.1.0-28)
> > 
> >    * What was the outcome of this action?
> >    Kernel log contains errors and trace. Block device not working. Module "zram" can not be removed without reboot.
> >  
> >    * What outcome did you expect instead?
> >    Successfully creating a 1GB block device
> 
> Yes, there is a zram related regression in at least the 6.1.y upstream
> stable series, cf. https://lore.kernel.org/regressions/010001944286f97d-fe02c461-e7af-4644-9155-a96995709804-000000@email.amazonses.com/

This is fixed in 6.1.124 upstream and included in 6.1.124-1.

Regards,
Salvatore

[toc] | [prev] | [standalone]


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


csiph-web