Bug#1034903: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin navi10_mes.bin for module amdgpu

2024-01-18 Thread Diederik de Haas
On Friday, 23 June 2023 18:33:44 CET Alex Deucher wrote:
> On Wed, Jun 21, 2023 at 11:38 AM Ben Hutchings  wrote:
> > On Thu, 27 Apr 2023 15:43:28 +0800 xiao sheng wen(
> >  wrote:
> > > Package: firmware-amd-graphics
> > > Version: 20230310-1~exp1
> > > 
> > >  When I upgrade to kernel 5.10.0-22-arm64, there are following error
> > > 
> > >  infos:
> > > W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin
> > > for module amdgpu W: Possible missing firmware
> > > /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu> 
> > [...]
> 
> Those could be dropped.  They are not really used by the driver.  They
> are for a feature which was not ultimately productized on those parts.

Does this mean that *this* bug can be closed?
Further discussions are about different firmware files, but not the ones
this bug was about.

> > More recently amdgpu added:
> > 
> > MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes.bin");
> > MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes_2.bin");
> > MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes1.bin");
> > 
> > and these are also missing from linux-firmware.git.
> > 
> > Is this firmware intended to be available to the public?
> 
> Yes, those will be available soon.

From current master WHENCE file:
File: amdgpu/gc_11_0_3_me.bin
File: amdgpu/gc_11_0_3_mec.bin
File: amdgpu/gc_11_0_3_mes1.bin
File: amdgpu/gc_11_0_3_mes_2.bin

So 2 out of 3 are now available, but not the `*_mes.bin` file.

signature.asc
Description: This is a digitally signed message part.


Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable

2024-01-18 Thread Arno Lehmann

Hello,

Am 18.01.2024 um 22:12 schrieb Salvatore Bonaccorso:

Hi,

On Sat, Jan 13, 2024 at 04:39:51PM +0100, Arno Lehmann wrote:

Hi Salvatore,

Am 13.01.2024 um 13:47 schrieb Salvatore Bonaccorso:


Just to be clear, can you confirm this is or is not a regression from
a previous running 6.1.y kernel?


On this hardware, the network issues appeared right from the start.

First time I encountered it was with the Debian installation sime time last
year, and that's where my research led me to turn off PCIe power management.

Actually I don't even know which was the first kernel version I had on this
host, but it's been on Bookworm for all its lifetime.


This "feels" like its probably not really a regression, thus the
similarity (though not the identical case as the referenced thread).

What about newer kernels? Do 6.6.11-1 or 6.7-1~exp1 taken from
unstable (resp. experimental) show the same problem?

If yes, then it might be an idea to bring it upstream.


Well, tricky... at this stage, we're guessing what will tell us more -- 
newer kernel or an older one. And then we'll need to wait for while to 
see what happens.


Well, tomorrow morning I'll be on site and can then install another 
kernel and reboot.


Cheers,

Arno


--
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable

2024-01-18 Thread Salvatore Bonaccorso
Hi,

On Sat, Jan 13, 2024 at 04:39:51PM +0100, Arno Lehmann wrote:
> Hi Salvatore,
> 
> Am 13.01.2024 um 13:47 schrieb Salvatore Bonaccorso:
> 
> > Just to be clear, can you confirm this is or is not a regression from
> > a previous running 6.1.y kernel?
> 
> On this hardware, the network issues appeared right from the start.
> 
> First time I encountered it was with the Debian installation sime time last
> year, and that's where my research led me to turn off PCIe power management.
> 
> Actually I don't even know which was the first kernel version I had on this
> host, but it's been on Bookworm for all its lifetime.

This "feels" like its probably not really a regression, thus the
similarity (though not the identical case as the referenced thread).

What about newer kernels? Do 6.6.11-1 or 6.7-1~exp1 taken from
unstable (resp. experimental) show the same problem?

If yes, then it might be an idea to bring it upstream.

Regards,
Salvatore



Fwd: Also observing #988477

2024-01-18 Thread Elliott Mitchell
I should have Cc'd debian-kernel@lists.debian.org, but failed to do so.
As such now forwarding a copy.  At the very least this involves the
Linux MD-RAID1 functionality, but I am unsure whether this is a Linux
kernel bug versus a Xen bug.


Forwarded:

I am also observing #988477 occur.  This machine has a AMD Zen 4
processor.  The first observation was when motherboard/processor was
swapped out, the older motherboard/processor was several generations old.

The pattern which is emerging is Linux MD RAID1 plus recent AMD processor
which has full IOMMU functionality.  The older machine was believed to
have an IOMMU, but the BIOS wasn't creating appropriate ACPI tables
(IVRS) and thus Xen was unable to utilize it.

This seems to be occuring with a small percentage of write operations.
Subsequent read operations appear to be fine.

I am not convinced this is a Xen bug.  I suspect this is instead a bug
in the Linux MD subsystem.  In particular if the DMA interface was
designed assuming only a single device would ever access any page, but
the MD RAID1 driver is reusing the same page for both devices.

IOMMU page release could be handled by marking the page unused in a
device data structure and later removed by sweeping a table.  In such
case if the MD-RAID1 driver was to redirect the page to another device
between these two steps, the entry for a subsequent device could be wiped
out when trying to invalidate an entry for a prior device.


Anyway, I'm also observing bug #988477.  This could also be a kernel bug.
So far no crashes/confirmed data loss have occured, but sweeping the
mirror does turn up small numbers of inconsistencies.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445




Bug#1061117: linux-image-6.1.0-17-arm64: please enable support for lx2160a serdes runtime configuration

2024-01-18 Thread Josua Mayer
Package: src:linux
Version: 6.1.69-1
Severity: important
X-Debbugs-Cc: jo...@solid-run.com

Dear Maintainer,

Please enable support for lx2160a serdes configuration driver in arm64 flavour:
CONFIG_PHY_FSL_LYNX_28G

This driver is essential for supporting the SFP+ connectors on
SolidRun Honeycomb Workstation. Since mainline added references
to SerDes via "phys" properties in v5.18, Debian can not probe
the netdev's, breaking all 10Gbps NICs.

Ideally this will be enabled for current stable release, too.

Sincerely
Josua Mayer

-- Package-specific info:
** Version:
Linux version 6.1.0-17-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 
6.1.69-1 (2023-12-30)

** Command line:
 arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet

** Not tainted

** Kernel log:
[4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) 
(authenc-hmac-md5-cbc-aes-caam-qi2)
[4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) 
(echainiv-authenc-hmac-md5-cbc-aes-caam-qi2)
[4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=525 
comm="apparmor_parser"
[4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 
comm="apparmor_parser"
[4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=526 comm="apparmor_parser"
[4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) 
(echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2)
[4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) 
(authenc-hmac-sha224-cbc-aes-caam-qi2)
[4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) 
(echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2)
[4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) 
(echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2)
[4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) 
(authenc-hmac-sha384-cbc-aes-caam-qi2)
[4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) 
(echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2)
[4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 
comm="apparmor_parser"
[4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=528 
comm="apparmor_parser"
[4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=528 
comm="apparmor_parser"
[4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) 
(echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2)
[4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) 
(authenc-hmac-md5-cbc-des3_ede-caam-qi2)
[4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) 
(echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2)
[4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2)
[4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2)
[4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2)
[4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2)
[4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2)
[4.347693] alg: No test for authenc(hmac(md5),cbc(des)) 
(authenc-hmac-md5-cbc-des-caam-qi2)
[4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) 
(echainiv-authenc-hmac-md5-cbc-des-caam-qi2)
[4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) 
(echainiv-authenc-hmac-sha1-cbc-des-caam-qi2)
[4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) 
(echainiv-authenc-hmac-sha224-cbc-des-caam-qi2)
[4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) 
(echainiv-authenc-hmac-sha256-cbc-des-caam-qi2)
[4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) 
(echainiv-authenc-hmac-sha384-cbc-des-caam-qi2)
[4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) 
(echainiv-authenc-hmac-sha512-cbc-des-caam-qi2)
[4.353008] alg: No test for authenc(hmac(md5),rfc3686(ctr(aes))) 
(authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2)
[4.353112] alg: No test for seqiv(authenc(hmac(md5),rfc3686(ctr(aes 
(seqiv-authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2)
[4.353323] alg: No test for seqiv(authenc(hmac(sha1),rfc3686(ctr(aes 

Bug#1061116: linux-image-6.1.0-17-arm64: please enable support for lx2160a pcie gen4 controller on early silicon

2024-01-18 Thread Josua Mayer
Package: src:linux
Version: 6.1.69-1
Severity: normal
X-Debbugs-Cc: jo...@solid-run.com

Dear Maintainer,

Please enable "PCIE_LAYERSCAPE_GEN4" for arm64 flavour,
in addition to already enabled "PCIE_LAYERSCAPE".

LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
It requires a different driver from newer gen-3 silicon.

This affects the SolidRun Honeycomb Workstation which
is otherwise fully supported in Debian.
Ideally the config option wll be enabled for debian stable, too.

-- Package-specific info:
** Version:
Linux version 6.1.0-17-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 
6.1.69-1 (2023-12-30)

** Command line:
 arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet

** Not tainted

** Kernel log:
[4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) 
(authenc-hmac-md5-cbc-aes-caam-qi2)
[4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) 
(echainiv-authenc-hmac-md5-cbc-aes-caam-qi2)
[4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=525 
comm="apparmor_parser"
[4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 
comm="apparmor_parser"
[4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=526 comm="apparmor_parser"
[4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) 
(echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2)
[4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) 
(authenc-hmac-sha224-cbc-aes-caam-qi2)
[4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) 
(echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2)
[4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) 
(echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2)
[4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) 
(authenc-hmac-sha384-cbc-aes-caam-qi2)
[4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) 
(echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2)
[4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 
comm="apparmor_parser"
[4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=528 
comm="apparmor_parser"
[4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=528 
comm="apparmor_parser"
[4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) 
(echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2)
[4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) 
(authenc-hmac-md5-cbc-des3_ede-caam-qi2)
[4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) 
(echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2)
[4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2)
[4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2)
[4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2)
[4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2)
[4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) 
(echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2)
[4.347693] alg: No test for authenc(hmac(md5),cbc(des)) 
(authenc-hmac-md5-cbc-des-caam-qi2)
[4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) 
(echainiv-authenc-hmac-md5-cbc-des-caam-qi2)
[4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) 
(echainiv-authenc-hmac-sha1-cbc-des-caam-qi2)
[4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) 
(echainiv-authenc-hmac-sha224-cbc-des-caam-qi2)
[4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) 
(echainiv-authenc-hmac-sha256-cbc-des-caam-qi2)
[4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) 
(echainiv-authenc-hmac-sha384-cbc-des-caam-qi2)
[4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) 
(echainiv-authenc-hmac-sha512-cbc-des-caam-qi2)
[4.353008] alg: No test for authenc(hmac(md5),rfc3686(ctr(aes))) 
(authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2)
[4.353112] alg: No test for seqiv(authenc(hmac(md5),rfc3686(ctr(aes 
(seqiv-authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2)
[4.353323] alg: No test for seqiv(authenc(hmac(sha1),rfc3686(ctr(aes 
(seqiv-authenc-hmac-sha1-rfc3686-ctr-aes-caam-qi2)
[4.353425] alg: 

Processed: closing 1036968

2024-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1036968
Bug #1036968 [src:linux] linux: Enable CONFIG_SND_SOC_CS35L41_I2C for Intel 
Alder Lake sound
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1036968: included in 6.6.9-1

2024-01-18 Thread Hans-Christoph Steiner



For the record, the module was included starting in 6.6.9-1:

$ grep -i CS35L41 /boot/config-6.6.9-amd64
CONFIG_SND_HDA_SCODEC_CS35L41=m
CONFIG_SND_HDA_SCODEC_CS35L41_I2C=m
CONFIG_SND_HDA_SCODEC_CS35L41_SPI=m
CONFIG_SND_SOC_CS35L41_LIB=m
CONFIG_SND_SOC_CS35L41=m
CONFIG_SND_SOC_CS35L41_SPI=m
CONFIG_SND_SOC_CS35L41_I2C=m



Processed: fixed

2024-01-18 Thread Debian Bug Tracking System
Processing control commands:

> fixed 1036968 6.6.9-1
Bug #1036968 [src:linux] linux: Enable CONFIG_SND_SOC_CS35L41_I2C for Intel 
Alder Lake sound
Marked as fixed in versions linux/6.6.9-1.
> fixed 1036968 6.6.11-1
Bug #1036968 [src:linux] linux: Enable CONFIG_SND_SOC_CS35L41_I2C for Intel 
Alder Lake sound
Marked as fixed in versions linux/6.6.11-1.

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



Bug#1036968: fixed

2024-01-18 Thread Hans-Christoph Steiner

Control: fixed 1036968 6.6.9-1
Control: fixed 1036968 6.6.11-1

With 6.6.11-1, the headphone jack insert detection is now working when running 
on bookworm.