Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Source: linux
Source-Version: 6.1.15-1
Hi Eriberto,
On Mon, Mar 27, 2023 at 09:58:31PM -0300, Eriberto wrote:
> Hi Salvatore,
>
> Sorry for my delay.
>
> Em dom., 26 de mar. de 2023 às 15:44, Salvatore Bonaccorso
> escreveu:
> >
> > Hi,
> >
> > On Thu, Mar 23, 2023 at 10:36:21PM +0100, Salvatore Bonaccorso wrote:
> > > Hi Eriberto,
> > >
> > > On Sat, Nov 19, 2022 at 11:53:59AM -0300, Eriberto wrote:
> > > > Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
> > > > escreveu:
> > > > >
> > > > > Hi
> > > > >
> > > > > On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho
> > > > > wrote:
> > > > > > Package: src:linux
> > > > > > Version: 5.19.11-1~bpo11+1
> > > > > > Severity: important
> > > > > >
> > > > > > Dear maintainer,
> > > > > >
> > > > > > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2
> > > > > > SSD). The
> > > > > > current kernel on BPO creates an infinite loop when shutting down
> > > > > > the system. I
> > > > > > can see several messages like:
> > > > > >
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > md: md2 stopped.
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > md: md2 stopped.
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > md: md2 stopped.
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > [...]
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > block device autoloading is deprecated and will be removed
> > > > > > [...]
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > md: md2 stopped.
> > > > > > [...]
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > md: md2 stopped.
> > > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > > md: md2 stopped.
> > > > > > [...]
> > > > > >
> > > > > > There is a solution from Arch Linux[1]:
> > > > > >
> > > > > > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke
> > > > > > mdraid".
> > > > > >
> > > > > > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> > > > > >
> > > > > > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD,
> > > > > > enabled by
> > > > > > default in current kernel on Debian:
> > > > > >
> > > > > > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep
> > > > > > BLOCK_LEGACY_AUTOLOAD
> > > > > > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> > > > > >
> > > > > > Thanks in advance.
> > > > >
> > > > > I'm not sure, can we can do that (yet)? Some context about this is in
> > > > > https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> > > > > . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> > > > > for block device autoloading and with 451f0b6f4c44 ("block: default
> > > > > BLOCK_LEGACY_AUTOLOAD to y")[1].
> > > > >
> > > > > Initially it was planned to make it for 5.19, see fbdee71bb5d8
> > > > > ("block: deprecate autoloading based on dev_t")[2].
> > > > >
> > > > > [1]:
> > > > > https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> > > > > [2]:
> > > > > https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
> > > > >
> > > > > Regards,
> > > > > Salvatore
> > > >
> > > > Thanks for the clarification Salvatore. Currently, this is a nightmare
> > > > for me because I am being compelled to power off my computer via the
> > > > energy switch.
> > >
> > > I noticed in mainline landed 6c0f5898836c ("md: select
> > > BLOCK_LEGACY_AUTOLOAD") in 6.3-rc3, which was as well backported to
> > > 6.1.21.
> > >
> > > https://git.kernel.org/linus/6c0f5898836c05c6d850a750ed7940ba29e4e6c5
> > >
> > > So I guess we can/need to close this bug or mark it wontfix at
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Hi Salvatore,
Sorry for my delay.
Em dom., 26 de mar. de 2023 às 15:44, Salvatore Bonaccorso
escreveu:
>
> Hi,
>
> On Thu, Mar 23, 2023 at 10:36:21PM +0100, Salvatore Bonaccorso wrote:
> > Hi Eriberto,
> >
> > On Sat, Nov 19, 2022 at 11:53:59AM -0300, Eriberto wrote:
> > > Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
> > > escreveu:
> > > >
> > > > Hi
> > > >
> > > > On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho
> > > > wrote:
> > > > > Package: src:linux
> > > > > Version: 5.19.11-1~bpo11+1
> > > > > Severity: important
> > > > >
> > > > > Dear maintainer,
> > > > >
> > > > > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD).
> > > > > The
> > > > > current kernel on BPO creates an infinite loop when shutting down the
> > > > > system. I
> > > > > can see several messages like:
> > > > >
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > [...]
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > block device autoloading is deprecated and will be removed
> > > > > [...]
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > md: md2 stopped.
> > > > > [...]
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > > systemd-shutdown[1]: Stopping MD devices.
> > > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > > md: md2 stopped.
> > > > > [...]
> > > > >
> > > > > There is a solution from Arch Linux[1]:
> > > > >
> > > > > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> > > > >
> > > > > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> > > > >
> > > > > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD,
> > > > > enabled by
> > > > > default in current kernel on Debian:
> > > > >
> > > > > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > > > > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> > > > >
> > > > > Thanks in advance.
> > > >
> > > > I'm not sure, can we can do that (yet)? Some context about this is in
> > > > https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> > > > . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> > > > for block device autoloading and with 451f0b6f4c44 ("block: default
> > > > BLOCK_LEGACY_AUTOLOAD to y")[1].
> > > >
> > > > Initially it was planned to make it for 5.19, see fbdee71bb5d8
> > > > ("block: deprecate autoloading based on dev_t")[2].
> > > >
> > > > [1]:
> > > > https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> > > > [2]:
> > > > https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
> > > >
> > > > Regards,
> > > > Salvatore
> > >
> > > Thanks for the clarification Salvatore. Currently, this is a nightmare
> > > for me because I am being compelled to power off my computer via the
> > > energy switch.
> >
> > I noticed in mainline landed 6c0f5898836c ("md: select
> > BLOCK_LEGACY_AUTOLOAD") in 6.3-rc3, which was as well backported to
> > 6.1.21.
> >
> > https://git.kernel.org/linus/6c0f5898836c05c6d850a750ed7940ba29e4e6c5
> >
> > So I guess we can/need to close this bug or mark it wontfix at least
> > for the time beeing.
> >
> > Thoughts?
>
> Well scratch that about closing the bug. The bug still exists, it's
> just that we won't disable BLOCK_LEGACY_AUTOLOAD.
>
> I assume you are still able to reproduce the problem with the most
> current kernel available?
I am using the testing release since Feb 12. I no longer noticed the issue.
Regards,
Eriberto
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Hi,
On Thu, Mar 23, 2023 at 10:36:21PM +0100, Salvatore Bonaccorso wrote:
> Hi Eriberto,
>
> On Sat, Nov 19, 2022 at 11:53:59AM -0300, Eriberto wrote:
> > Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
> > escreveu:
> > >
> > > Hi
> > >
> > > On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho wrote:
> > > > Package: src:linux
> > > > Version: 5.19.11-1~bpo11+1
> > > > Severity: important
> > > >
> > > > Dear maintainer,
> > > >
> > > > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
> > > > current kernel on BPO creates an infinite loop when shutting down the
> > > > system. I
> > > > can see several messages like:
> > > >
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > md: md2 stopped.
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > md: md2 stopped.
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > md: md2 stopped.
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > [...]
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > block device autoloading is deprecated and will be removed
> > > > [...]
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > md: md2 stopped.
> > > > [...]
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > md: md2 stopped.
> > > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > > systemd-shutdown[1]: Stopping MD devices.
> > > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > > md: md2 stopped.
> > > > [...]
> > > >
> > > > There is a solution from Arch Linux[1]:
> > > >
> > > > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> > > >
> > > > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> > > >
> > > > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD,
> > > > enabled by
> > > > default in current kernel on Debian:
> > > >
> > > > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > > > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> > > >
> > > > Thanks in advance.
> > >
> > > I'm not sure, can we can do that (yet)? Some context about this is in
> > > https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> > > . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> > > for block device autoloading and with 451f0b6f4c44 ("block: default
> > > BLOCK_LEGACY_AUTOLOAD to y")[1].
> > >
> > > Initially it was planned to make it for 5.19, see fbdee71bb5d8
> > > ("block: deprecate autoloading based on dev_t")[2].
> > >
> > > [1]:
> > > https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> > > [2]:
> > > https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
> > >
> > > Regards,
> > > Salvatore
> >
> > Thanks for the clarification Salvatore. Currently, this is a nightmare
> > for me because I am being compelled to power off my computer via the
> > energy switch.
>
> I noticed in mainline landed 6c0f5898836c ("md: select
> BLOCK_LEGACY_AUTOLOAD") in 6.3-rc3, which was as well backported to
> 6.1.21.
>
> https://git.kernel.org/linus/6c0f5898836c05c6d850a750ed7940ba29e4e6c5
>
> So I guess we can/need to close this bug or mark it wontfix at least
> for the time beeing.
>
> Thoughts?
Well scratch that about closing the bug. The bug still exists, it's
just that we won't disable BLOCK_LEGACY_AUTOLOAD.
I assume you are still able to reproduce the problem with the most
current kernel available?
Regards,
Salvatore
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Hi Eriberto,
On Sat, Nov 19, 2022 at 11:53:59AM -0300, Eriberto wrote:
> Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
> escreveu:
> >
> > Hi
> >
> > On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho wrote:
> > > Package: src:linux
> > > Version: 5.19.11-1~bpo11+1
> > > Severity: important
> > >
> > > Dear maintainer,
> > >
> > > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
> > > current kernel on BPO creates an infinite loop when shutting down the
> > > system. I
> > > can see several messages like:
> > >
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > md: md2 stopped.
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > md: md2 stopped.
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > md: md2 stopped.
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > [...]
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > block device autoloading is deprecated and will be removed
> > > [...]
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > md: md2 stopped.
> > > [...]
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > md: md2 stopped.
> > > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > > systemd-shutdown[1]: Stopping MD devices.
> > > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > > md: md2 stopped.
> > > [...]
> > >
> > > There is a solution from Arch Linux[1]:
> > >
> > > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> > >
> > > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> > >
> > > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled
> > > by
> > > default in current kernel on Debian:
> > >
> > > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> > >
> > > Thanks in advance.
> >
> > I'm not sure, can we can do that (yet)? Some context about this is in
> > https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> > . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> > for block device autoloading and with 451f0b6f4c44 ("block: default
> > BLOCK_LEGACY_AUTOLOAD to y")[1].
> >
> > Initially it was planned to make it for 5.19, see fbdee71bb5d8
> > ("block: deprecate autoloading based on dev_t")[2].
> >
> > [1]: https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> > [2]: https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
> >
> > Regards,
> > Salvatore
>
> Thanks for the clarification Salvatore. Currently, this is a nightmare
> for me because I am being compelled to power off my computer via the
> energy switch.
I noticed in mainline landed 6c0f5898836c ("md: select
BLOCK_LEGACY_AUTOLOAD") in 6.3-rc3, which was as well backported to
6.1.21.
https://git.kernel.org/linus/6c0f5898836c05c6d850a750ed7940ba29e4e6c5
So I guess we can/need to close this bug or mark it wontfix at least
for the time beeing.
Thoughts?
Regards,
Salvatore
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Em sáb., 19 de nov. de 2022 às 11:36, Salvatore Bonaccorso
escreveu:
>
> Hi
>
> On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho wrote:
> > Package: src:linux
> > Version: 5.19.11-1~bpo11+1
> > Severity: important
> >
> > Dear maintainer,
> >
> > I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
> > current kernel on BPO creates an infinite loop when shutting down the
> > system. I
> > can see several messages like:
> >
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > [...]
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > block device autoloading is deprecated and will be removed
> > [...]
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > md: md2 stopped.
> > [...]
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> > systemd-shutdown[1]: Stopping MD devices.
> > systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> > md: md2 stopped.
> > [...]
> >
> > There is a solution from Arch Linux[1]:
> >
> > "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
> >
> > [1] https://bbs.archlinux.org/viewtopic.php?id=279383
> >
> > Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled by
> > default in current kernel on Debian:
> >
> > $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> > CONFIG_BLOCK_LEGACY_AUTOLOAD=y
> >
> > Thanks in advance.
>
> I'm not sure, can we can do that (yet)? Some context about this is in
> https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
> . In fact back for 5.18-rc1 upstream has weakened the removal schedule
> for block device autoloading and with 451f0b6f4c44 ("block: default
> BLOCK_LEGACY_AUTOLOAD to y")[1].
>
> Initially it was planned to make it for 5.19, see fbdee71bb5d8
> ("block: deprecate autoloading based on dev_t")[2].
>
> [1]: https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
> [2]: https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
>
> Regards,
> Salvatore
Thanks for the clarification Salvatore. Currently, this is a nightmare
for me because I am being compelled to power off my computer via the
energy switch.
Regards,
Eriberto
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Hi
On Fri, Nov 11, 2022 at 06:33:23PM -0300, Joao Eriberto Mota Filho wrote:
> Package: src:linux
> Version: 5.19.11-1~bpo11+1
> Severity: important
>
> Dear maintainer,
>
> I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
> current kernel on BPO creates an infinite loop when shutting down the system.
> I
> can see several messages like:
>
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> md: md2 stopped.
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> md: md2 stopped.
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> md: md2 stopped.
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> [...]
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> block device autoloading is deprecated and will be removed
> [...]
> md: md2 stopped.
> md: md2 stopped.
> md: md2 stopped.
> md: md2 stopped.
> md: md2 stopped.
> md: md2 stopped.
> md: md2 stopped.
> [...]
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> md: md2 stopped.
> systemd-shutdown[1]: Not all MD devices stopped. 1 left.
> systemd-shutdown[1]: Stopping MD devices.
> systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
> md: md2 stopped.
> [...]
>
> There is a solution from Arch Linux[1]:
>
> "Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
>
> [1] https://bbs.archlinux.org/viewtopic.php?id=279383
>
> Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled by
> default in current kernel on Debian:
>
> $ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
> CONFIG_BLOCK_LEGACY_AUTOLOAD=y
>
> Thanks in advance.
I'm not sure, can we can do that (yet)? Some context about this is in
https://lore.kernel.org/all/yhe%2fc0k0fn9j8...@bombadil.infradead.org/
. In fact back for 5.18-rc1 upstream has weakened the removal schedule
for block device autoloading and with 451f0b6f4c44 ("block: default
BLOCK_LEGACY_AUTOLOAD to y")[1].
Initially it was planned to make it for 5.19, see fbdee71bb5d8
("block: deprecate autoloading based on dev_t")[2].
[1]: https://git.kernel.org/linus/451f0b6f4c44d7b649ae609157b114b71f6d7875
[2]: https://git.kernel.org/linus/fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
Regards,
Salvatore
Bug#1023876: linux-image-5.19.0-0.deb11.2-amd64: infinite loop whit RAID1 when shutting down
Package: src:linux
Version: 5.19.11-1~bpo11+1
Severity: important
Dear maintainer,
I have a desktop with 3 polls over RAID1 (2 SSD, 2 HDD, plus 2 SSD). The
current kernel on BPO creates an infinite loop when shutting down the system. I
can see several messages like:
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
[...]
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
block device autoloading is deprecated and will be removed
[...]
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
md: md2 stopped.
[...]
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
systemd-shutdown[1]: Not all MD devices stopped. 1 left.
systemd-shutdown[1]: Stopping MD devices.
systemd-shutdown[1]: Stopping MD /dev/md2 (9:2)
md: md2 stopped.
[...]
There is a solution from Arch Linux[1]:
"Arch disabled BLOCK_LEGACY_AUTOLOAD for 5.18 which broke mdraid".
[1] https://bbs.archlinux.org/viewtopic.php?id=279383
Please, consider disabling the deprecated BLOCK_LEGACY_AUTOLOAD, enabled by
default in current kernel on Debian:
$ cat /boot/config-5.19.0-0.deb11.2-amd64 | grep BLOCK_LEGACY_AUTOLOAD
CONFIG_BLOCK_LEGACY_AUTOLOAD=y
Thanks in advance.
Regards,
Eriberto
-- Package-specific info:
** Version:
Linux version 5.19.0-0.deb11.2-amd64 (debian-ker...@lists.debian.org) (gcc-10
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1
SMP PREEMPT_DYNAMIC Debian 5.19.11-1~bpo11+1 (2022-10-03)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.19.0-0.deb11.2-amd64
root=UUID=daa37e3e-4081-445f-ba72-16c898462277 ro
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1017
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME B560-PLUS
board_version: Rev 1.xx
** Loaded modules:
tls
nfnetlink
bridge
stp
llc
binfmt_misc
intel_rapl_msr
intel_rapl_common
mei_hdcp
nls_ascii
nls_cp437
vfat
fat
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
snd_hda_codec_realtek
snd_hda_codec_generic
kvm
ledtrig_audio
snd_hda_codec_hdmi
snd_usb_audio
snd_hda_intel
irqbypass
snd_intel_dspcfg
snd_intel_sdw_acpi
nvidia_drm(POE)
drm_kms_helper
nvidia_modeset(POE)
rapl
intel_cstate
eeepc_wmi
asus_wmi
platform_profile
battery
efi_pstore
sparse_keymap
rfkill
snd_hda_codec
uvcvideo
snd_usbmidi_lib
snd_hda_core
snd_rawmidi
videobuf2_vmalloc
snd_seq_device
snd_hwdep
videobuf2_memops
videobuf2_v4l2
snd_pcm
joydev
evdev
videobuf2_common
intel_uncore
snd_timer
pcspkr
wmi_bmof
iTCO_wdt
snd
intel_pmc_bxt
mei_me
iTCO_vendor_support
soundcore
mei
watchdog
ee1004
sg
intel_pmc_core
acpi_pad
acpi_tad
button
nvidia(POE)
v4l2loopback(OE)
videodev
mc
dummy
parport_pc
ppdev
lp
parport
loop
dm_crypt
dm_mod
drm
fuse
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_logitech_hidpp
hid_logitech_dj
btrfs
zstd_compress
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
raid0
multipath
linear
hid_generic
usbhid
hid
raid1
md_mod
sd_mod
t10_pi
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
crc64
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ahci
ghash_clmulni_intel
libahci
xhci_pci
libata
xhci_hcd
e1000e
aesni_intel
usbcore
crypto_simd
scsi_mod
cryptd
ptp
intel_lpss_pci
i2c_i801
pps_core
intel_lpss
i2c_smbus
scsi_common
idma64
usb_common
wmi
fan
video
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b43] (rev 05)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Control: I/O- Mem+
