Your message dated Wed, 22 Mar 2023 09:11:44 +0100
with message-id <7d56278c22162f42dacb800156c3602c4310f81c.ca...@debian.org>
and subject line Closing after further investigation
has caused the Debian Bug report #1027444,
regarding linux-signed-amd64: system crash after loading radeon module
to be
Thanks Cyril.
Another important detail ... I only get that behavior in qemu in
graphical mode.
On LPARs there is no issue. I didn't try on baremetal so far.
F.
On Tue, 21 Mar 2023 17:44:49 +0100 Cyril Brulebois wrote:
> Frédéric Bonnard (2023-03-17):
> > > It would be helpful to confirm which e
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 19 Mar 2023 15:46:34 +0100
Source: linux-signed-arm64
Architecture: source
Version: 6.1.20+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By:
Package: initramfs-tools-core
Version: 0.142
Severity: normal
Tags: patch
With a root filesystem on ZFS then mkinitramfs builds an initrd that
lacks fsck.zfs:
testaroli# mkinitramfs -o /boot/initrd.img-$(uname -r)
W: Couldn't identify type of root file system for fsck hook
Source: linux
Version: 6.1.20-1
Severity: important
Tags: upstream patch
On 32-bit architectures, many symbol versions (CRCs) are recorded in
Module.symvers as 0x7fff.
This is a regression, and I have bisected it to the upstream change:
commit f292d875d0dc700b3af0bef04c5abc1dc7b3b62c
Author:
Processing commands for cont...@bugs.debian.org:
> forwarded 1033329
> https://lore.kernel.org/linux-kbuild/zbte4xlqcxjfe...@decadent.org.uk/T/
Bug #1033329 [src:linux] Bad symbol versions on 32-bit architectures
Set Bug forwarded-to-address to
'https://lore.kernel.org/linux-kbuild/zbte4xlqcxjfe
Processing commands for cont...@bugs.debian.org:
> # Bug was introduced in 5.19-rc1
> found 1033329 5.19~rc4-1~exp1
Bug #1033329 [src:linux] Bad symbol versions on 32-bit architectures
Marked as found in versions linux/5.19~rc4-1~exp1.
> thanks
Stopping processing here.
Please contact me if you n
Ciao Giuseppe,
> Hello,
> I finally found the source of this problem: it was a hardware problem on
> the video card. In fact, after replacing the board the system started
> working correctly. Sorry to bother you.
Thanks for reporting back!
Regards,
Salvatore
Hi Frédéric,
Frédéric Bonnard (2023-03-22):
> Another important detail ... I only get that behavior in qemu in
> graphical mode. On LPARs there is no issue. I didn't try on baremetal
> so far.
Could you please guide me into reproducing this issue in QEMU? #987368
had hints, but at least the open
9 matches
Mail list logo
