Bug#1032067: linux-image-5.10.0-19-amd64: recurring btrfs errors and warning related to ibm websphere mq operating files

2023-02-27 Thread IT
Package: src:linux Version: 5.10.149-2 Severity: normal X-Debbugs-Cc: i...@bsi.sm Dear Maintainer, on a server with IBM WebSphere MQ, BTRFS returns these messages: BTRFS warning (device vda2): csum failed root 256 ino 647789 off 9109504 csum 0x2d57cc4b expected csum 0x58676c1e mirror 1 BTRFS

Processed: Apparent s390x kernel bug

2023-02-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1030511 [src:libguestfs] libguestfs: FTBFS on s390x: timeout Added tag(s) pending. > block -1 by 1031753 Bug #1030511 [src:libguestfs] libguestfs: FTBFS on s390x: timeout 1030511 was not blocked by any bugs. 1030511 was not blocking any bugs.

Processed: affects 1031753

2023-02-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1031753 src:qemu Bug #1031753 [src:linux] linux-image-5.10.0-21-s390x: user space process hangs on s390 kernel 5.10.162-1 Added indication that 1031753 affects src:qemu > thanks Stopping processing here. Please contact me if you need

Processed: Re: qemu: qemu-img and qemu-system-s390x hang on s390x

2023-02-27 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1031753 Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x 1030545 was not blocked by any bugs. 1030545 was not blocking any bugs. Added blocking bug(s) of 1030545: 1031753 -- 1030545:

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Daniel Black
Source: linux Version: 5.10.0-21-powerpc64le Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: dan...@mariadb.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Diederik de Haas
On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote: > Source: linux > Version: 5.10.0-21-powerpc64le > Severity: grave > Justification: causes non-serious data loss > X-Debbugs-Cc: dan...@mariadb.org > > >From https://jira.mariadb.org/browse/MDEV-30728 > > MariaDB's mtr tests on a

Bug#1032104: linux: ppc64el iouring corrupted read

2023-02-27 Thread Daniel Black
On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas wrote: > > On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote: > > Source: linux > > Version: 5.10.0-21-powerpc64le > > Severity: grave > > Justification: causes non-serious data loss > > X-Debbugs-Cc: dan...@mariadb.org > > > > >From

Bug#1031839: network devices do not work after kernel upgrade

2023-02-27 Thread Daniel Baumann
On 2/27/23 15:25, Daniel Baumann wrote: > ixgbe.allow_unsupported_sfp=1 I've rebootet the server again just to check and indeed, the above override doesn't work anymore (also tried with ...=1,1 because it's a two slots adapter, but doesn't make any difference). So, seems the reason for your

Plans to support the HSR kernel module

2023-02-27 Thread Yoann Congal
Hi, The HSR module is currently disabled by config : https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/config/config#L7031-7034 For one of our customer, we need this module (Mainly, the PRP IEC-62439-3 implementation) I'd like to know if there are any plans and/or target release

Bug#1031839: network devices do not work after kernel upgrade

2023-02-27 Thread Daniel Baumann
Hi Thorsten, On 2/25/23 11:56, Thorsten Alteholz wrote: > The I225-V are working fine, the other four make trouble. right, but those are copper interfaces. > I am using transceiver modules AXS85-192-M3 from 10Gtek. It looks like they are not flashable (like flexoptix and others), so I presume

Bug#1031839: network devices do not work after kernel upgrade

2023-02-27 Thread Diederik de Haas
On Friday, 24 February 2023 00:28:33 CET Thorsten Alteholz wrote: > upgrading from kernel 5.18.5-1 to 6.1.8-1 (and 6.1.12-1) network devices > using driver module ixgbe stop working. The devices are recognized and can > be configured but "ip a" shows "no-carrier" for them. > With kernel 5.18.5-1