Bug#1061430: firmware-realtek: Realtek 10ec:8136 wrongly identified as Fast Ethernet instead of Gigabit

[Răzvan Sandu]

Package: firmware-realtek
Version: 20230210-5
Severity: normal

Dear Maintainer,

I use stock Debian 12.x with non-free firmware installed, fully updated 
online.


I've noted that two Realtek-based Ethernet cards (hardware ID 
[10ec:8136], chipset RTL8111C) in my system operate as Fast Ethernet,
despite having Gigabit capability. They were advertised as "PCI-E&USB 
Network Adapter" with support for Windows, Mac and GNU/Linux 
(10/100/1000 Mbps).


In order to help, I've entered full hardware data for this ID at 
https://h-node.org/ethernetcards/view/en/2358/Realtek-Semiconductor-Co---Ltd--RTL810xE-PCI-Express-Fast-Ethernet-controller--rev-05-


Please include correct identification data for this RTL8111C Ethernet 
controller, so it can use its full hardware capabilities.



-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-17-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.142

-- no debconf information


Thank you!  :)

Răzvan

Bug#1061439: initramfs-tools-core: since zstd raid mapper not implemented in initramfs

[Christian Kiss]

Package: initramfs-tools-core
Version: 0.142
Severity: important
X-Debbugs-Cc: christianpeterk...@yahoo.com

Dear Maintainer,

since change of compression of kernel initramfs 5.9 to zstd

#keypoint update-initramfs does not seem to include the correct raid mappers

any boot drops to a shell early on which lists
a dos ptuuid
sda as part of a raid
sdb as part of a raid
but

#keypoint not the mapper withe raid

not boot not root
this is a bug

i suspected itis

#keypoint because of change of bullseye to bookworm
but it doesnot seem to get fixed

cc i use a backedup initramfs of a former kernel but since bullseye there is no
upgraded bookworm or bullseye kernel bootable since


all the best

Christian KISS
*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldstable-security'), (500, 'stable'), (500, 
'oldstable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-23-rt-686-pae (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools-core depends on:
ii  coreutils9.1-1
ii  cpio 2.13+dfsg-7.1
ii  e2fsprogs1.47.0-2
ii  klibc-utils  2.0.12-1
ii  kmod 30+20221128-1
ii  logsave  1.47.0-2
ii  udev 252.19-1~deb12u1

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.35.0-4+b3
ii  zstd 1.5.4+dfsg2-5

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.11-6

-- no debconf information

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

[Arno Lehmann]

Some news, but unfortunately not helping me to understand what we see :-)

Network link was lost during the day.

dmesg shows this:
[Tue Jan 23 06:54:24 2024] igc :0a:00.0 eno1: NIC Link is Up 1000 
Mbps Full Duplex, Flow Control: RX
[Tue Jan 23 16:24:13 2024] [drm:retrieve_link_cap [amdgpu]] *ERROR* 
retrieve_link_cap: Read receiver caps dpcd data failed.

[Tue Jan 23 23:09:16 2024] igc :0a:00.0 eno1: NIC Link is Down
[Tue Jan 23 23:09:19 2024] igc :0a:00.0 eno1: NIC Link is Up 1000 
Mbps Full Duplex, Flow Control: RX

[Wed Jan 24 12:00:23 2024] systemd-journald[750]:
[Wed Jan 24 14:46:17 2024] nfs: server  not responding, timed out
[Wed Jan 24 14:46:17 2024] nfs: server  not responding, timed out
[Wed Jan 24 17:00:09 2024] nfs: server  not responding, timed out

Here, I rmmod'ed the igc module and modprobe'd it immediately.

[Wed Jan 24 17:00:36 2024] igc :0a:00.0 eno1: PHC removed
[Wed Jan 24 17:00:42 2024] Intel(R) 2.5G Ethernet Linux Driver
[Wed Jan 24 17:00:42 2024] Copyright(c) 2018 Intel Corporation.
[Wed Jan 24 17:00:42 2024] igc :0a:00.0: PCIe PTM not supported by 
PCIe bus/controller

[Wed Jan 24 17:00:42 2024] pps pps0: new PPS source ptp0
[Wed Jan 24 17:00:42 2024] igc :0a:00.0 (unnamed net_device) 
(uninitialized): PHC added
[Wed Jan 24 17:00:42 2024] igc :0a:00.0: 4.000 Gb/s available PCIe 
bandwidth (5.0 GT/s PCIe x1 link)

[Wed Jan 24 17:00:42 2024] igc :0a:00.0 eth0: MAC: c8:7f:54:67:6d:cc
[Wed Jan 24 17:00:42 2024] igc :0a:00.0 eno1: renamed from eth0
[Wed Jan 24 17:00:45 2024] igc :0a:00.0 eno1: NIC Link is Up 1000 
Mbps Full Duplex, Flow Control: RX
[Wed Jan 24 17:00:45 2024] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link 
becomes ready



So, we have a case of the NIC becoming unresponsive for some reason, but 
I can not see or even guess the reason. I'll leave the system as it is 
for a few more days, I think, and then try a much newer kernel.


Or -- any better suggestions?

Cheers,

Arno

--
Arno Lehmann

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

Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

[Paul Menzel]

Package: linux-image-6.7-cloud-amd64
Version: 6.6.13-1
Severity: normal


Dear Debian folks,


Trying to quickly start a VM, it’d be great to not use an initrd image, 
and also use the Virtio features, for example with the command below:


qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 
-device virtio-rng-pci -net nic,model=virtio-net-pci -net 
user,hostfwd=tcp::5-:22 -drive 
if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic


Currently, that is not possible, as the driver is only available as 
module `virtio_blk.ko` (`CONFIG_VIRTIO_BLK=m`). It’d be great, if it 
could be built into the Linux kernel cloud image.



Kind regards,

Paul

Bug#1015287: Most other distributions support this ...

[Thomas Kuhlmann]

A solution would be really great, because ...

... crypted root and vlan (in combination) are not uncommon.

... all other (large) distributions (Ubuntu, RedHat, SuSe) already 
supports this.


With many thanks in advance,
Thomas

Upcoming stable point release (12.5)

[Adam D. Barratt]

Hi,

The next point release for "bookworm" (12.5) is scheduled for Saturday,
February 10th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.

Regards,

Adam

Upcoming oldstable point release (11.9)

[Adam D. Barratt]

Hi,

The next point release for "bullseye" (11.9) is scheduled for Saturday,
February 10th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.

Regards,

Adam

Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Patrice Duroux]

Package: src:linux
Version: 6.7.1-1~exp1
Severity: normal

Dear Maintainer,

Giving a try to 6.7, here is a message extracted from dmesg:

[4.177226] [ cut here ]
[4.177227] WARNING: CPU: 6 PID: 248 at
drivers/gpu/drm/amd/amdgpu/../display/dc/link/link_factory.c:387
construct_phy+0xb26/0xd60 [amdgpu]
[4.177658] Modules linked in: amdgpu(+) i915(+) sd_mod drm_exec amdxcp
gpu_sched drm_buddy nvme i2c_algo_bit drm_suballoc_helper drm_display_helper
ahci nvme_core hid_generic crc32_pclmul libahci crc32c_intel t10_pi cec libata
crc64_rocksoft_generic ghash_clmulni_intel rc_core drm_ttm_helper
crc64_rocksoft sha512_ssse3 i2c_hid_acpi ttm rtsx_pci_sdmmc i2c_hid xhci_pci
crc_t10dif sha512_generic mmc_core scsi_mod xhci_hcd drm_kms_helper video hid
crct10dif_generic intel_lpss_pci crct10dif_pclmul i2c_i801 sha256_ssse3
intel_lpss crc64 thunderbolt drm e1000e usbcore sha1_ssse3 rtsx_pci i2c_smbus
scsi_common crct10dif_common idma64 usb_common battery wmi button aesni_intel
crypto_simd cryptd
[4.177689] CPU: 6 PID: 248 Comm: (udev-worker) Not tainted 6.7-amd64 #1
Debian 6.7.1-1~exp1
[4.177691] Hardware name: Dell Inc. Precision 7540/0T2FXT, BIOS 1.29.0
11/03/2023
[4.177692] RIP: 0010:construct_phy+0xb26/0xd60 [amdgpu]
[4.178050] Code: b9 01 00 00 00 83 fe 01 74 40 48 8b 82 f8 03 00 00 89 f2
48 c7 c6 00 35 a7 c1 48 8b 40 10 48 8b 00 48 8b 78 08 e8 ba b7 5b fb <0f> 0b 49
8b 87 d0 01 00 00 b9 0f 00 00 00 48 8b 80 e8 04 00 00 48
[4.178052] RSP: 0018:aad300857408 EFLAGS: 00010246
[4.178053] RAX:  RBX: 96df636a1700 RCX:
c000efff
[4.178054] RDX:  RSI: efff RDI:
0001
[4.178055] RBP: 96df4d379c00 R08:  R09:
aad3008571d0
[4.178056] R10: 0003 R11: bded2428 R12:
aad300857474
[4.178057] R13: c1933140 R14: aad3008577d0 R15:
96df43e82000
[4.178058] FS:  7fcd5d9648c0() GS:96e2cc38()
knlGS:
[4.178060] CS:  0010 DS:  ES:  CR0: 80050033
[4.178061] CR2: 7fcd5d932a6d CR3: 000103e9a004 CR4:
003706f0
[4.178062] DR0:  DR1:  DR2:

[4.178063] DR3:  DR6: fffe0ff0 DR7:
0400
[4.178063] Call Trace:
[4.178066]  
[4.178067]  ? construct_phy+0xb26/0xd60 [amdgpu]
[4.178422]  ? __warn+0x81/0x130
[4.178426]  ? construct_phy+0xb26/0xd60 [amdgpu]
[4.178784]  ? report_bug+0x171/0x1a0
[4.178787]  ? handle_bug+0x3c/0x80
[4.178789]  ? exc_invalid_op+0x17/0x70
[4.178790]  ? asm_exc_invalid_op+0x1a/0x20
[4.178793]  ? construct_phy+0xb26/0xd60 [amdgpu]
[4.179149]  ? construct_phy+0xb26/0xd60 [amdgpu]
[4.179507]  link_create+0x1b2/0x200 [amdgpu]
[4.179865]  create_links+0x135/0x420 [amdgpu]
[4.180196]  dc_create+0x321/0x640 [amdgpu]
[4.180529]  amdgpu_dm_init.isra.0+0x2a0/0x1ed0 [amdgpu]
[4.180881]  ? sysvec_apic_timer_interrupt+0xe/0x90
[4.180883]  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
[4.180885]  ? delay_tsc+0x37/0xa0
[4.180889]  dm_hw_init+0x12/0x30 [amdgpu]
[4.181240]  amdgpu_device_init+0x1e42/0x24a0 [amdgpu]
[4.181517]  amdgpu_driver_load_kms+0x19/0x190 [amdgpu]
[4.181793]  amdgpu_pci_probe+0x165/0x4c0 [amdgpu]
[4.182067]  local_pci_probe+0x42/0xa0
[4.182070]  pci_device_probe+0xc7/0x240
[4.182072]  really_probe+0x19b/0x3e0
[4.182075]  ? __pfx___driver_attach+0x10/0x10
[4.182076]  __driver_probe_device+0x78/0x160
[4.182078]  driver_probe_device+0x1f/0x90
[4.182079]  __driver_attach+0xd2/0x1c0
[4.182081]  bus_for_each_dev+0x85/0xd0
[4.182083]  bus_add_driver+0x116/0x220
[4.182085]  driver_register+0x59/0x100
[4.182087]  ? __pfx_amdgpu_init+0x10/0x10 [amdgpu]
[4.182356]  do_one_initcall+0x58/0x320
[4.182359]  do_init_module+0x60/0x240
[4.182361]  init_module_from_file+0x89/0xe0
[4.182364]  idempotent_init_module+0x120/0x2b0
[4.182366]  __x64_sys_finit_module+0x5e/0xb0
[4.182367]  do_syscall_64+0x61/0x120
[4.182370]  ? do_syscall_64+0x70/0x120
[4.182372]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[4.182375] RIP: 0033:0x7fcd5e130f19
[4.182376] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d cf 1e 0d 00 f7 d8 64 89 01 48
[4.182378] RSP: 002b:7ffd314afa38 EFLAGS: 0246 ORIG_RAX:
0139
[4.182379] RAX: ffda RBX: 5611ee7f84d0 RCX:
7fcd5e130f19
[4.182380] RDX:  RSI: 7fcd5e2644f5 RDI:
0024
[4.182381] RBP:  R08: 0040 R09:
5611ee7d3140
[4.182382] R10: 0038 R11: 0246 R12:
7fcd5e2644f5
[4.182383] R13: 0002 R14: 5611ee7f0670 R15:
0

Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Patrice Duroux]

Yes, the message is from the version 6.7.1-1~exp1, sorry for the doubt.
It is just because, package name is «simply»: linux-image-6.7-amd64
and so I wrote 6.7, expecting the exact version from reportbug.
I will give it a try then and be back.


Le mer. 24 janv. 2024 à 20:02, Diederik de Haas
 a écrit :
>
> Control: tag -1 moreinfo
>
> On Wednesday, 24 January 2024 19:38:16 CET Patrice Duroux wrote:
> > Package: src:linux
> > Version: 6.7.1-1~exp1
> > Severity: normal
> >
> > Giving a try to 6.7, here is a message extracted from dmesg:
>
> Is that dmesg output from 6.7(.0) or 6.7.1?
> If from 6.7.1, does the error NOT occur with 6.7.0?
> If that's the case, can you test the attached patch with the `test-patches`
> script? See the following link for instructions:
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4

Processed: Re: Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1061449 [src:linux] linux-image-6.7-amd64: a boot message from amdgpu
Added tag(s) moreinfo.

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

Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Diederik de Haas]

Control: tag -1 moreinfo

On Wednesday, 24 January 2024 19:38:16 CET Patrice Duroux wrote:
> Package: src:linux
> Version: 6.7.1-1~exp1
> Severity: normal
> 
> Giving a try to 6.7, here is a message extracted from dmesg:

Is that dmesg output from 6.7(.0) or 6.7.1?
If from 6.7.1, does the error NOT occur with 6.7.0?
If that's the case, can you test the attached patch with the `test-patches`
script? See the following link for instructions:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4>From 48e0efa8ff3b5f97cd2b12040b676dad09dbcefd Mon Sep 17 00:00:00 2001
From: Diederik de Haas 
Date: Wed, 24 Jan 2024 19:59:35 +0100
Subject: [PATCH] Revert "drm/amd/display: Pass pwrseq inst for backlight and
 ABM"

This reverts commit f90fb3a482d1d4705603ab6c320de0ccd611055c.
---
 .../drm/amd/display/dc/bios/bios_parser2.c|  4 +-
 .../drm/amd/display/dc/bios/command_table2.c  | 12 ++--
 .../drm/amd/display/dc/bios/command_table2.h  |  2 +-
 .../gpu/drm/amd/display/dc/dc_bios_types.h|  2 +-
 drivers/gpu/drm/amd/display/dc/dce/dmub_abm.c |  8 +--
 .../gpu/drm/amd/display/dc/dce/dmub_abm_lcd.c |  7 +--
 .../gpu/drm/amd/display/dc/dce/dmub_abm_lcd.h |  2 +-
 .../amd/display/dc/dcn31/dcn31_panel_cntl.c   |  5 +-
 .../amd/display/dc/hwss/dce110/dce110_hwseq.c | 16 ++---
 .../amd/display/dc/hwss/dcn21/dcn21_hwseq.c   | 36 +++
 drivers/gpu/drm/amd/display/dc/inc/hw/abm.h   |  3 +-
 .../drm/amd/display/dc/inc/hw/panel_cntl.h|  2 -
 .../drm/amd/display/dc/link/link_factory.c| 59 ++-
 .../gpu/drm/amd/display/dmub/inc/dmub_cmd.h   | 14 +
 14 files changed, 53 insertions(+), 119 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c b/drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c
index b5b29451d2db..2d1f5efa9091 100644
--- a/drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c
+++ b/drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c
@@ -1698,7 +1698,7 @@ static enum bp_result bios_parser_enable_disp_power_gating(
 static enum bp_result bios_parser_enable_lvtma_control(
 	struct dc_bios *dcb,
 	uint8_t uc_pwr_on,
-	uint8_t pwrseq_instance,
+	uint8_t panel_instance,
 	uint8_t bypass_panel_control_wait)
 {
 	struct bios_parser *bp = BP_FROM_DCB(dcb);
@@ -1706,7 +1706,7 @@ static enum bp_result bios_parser_enable_lvtma_control(
 	if (!bp->cmd_tbl.enable_lvtma_control)
 		return BP_RESULT_FAILURE;
 
-	return bp->cmd_tbl.enable_lvtma_control(bp, uc_pwr_on, pwrseq_instance, bypass_panel_control_wait);
+	return bp->cmd_tbl.enable_lvtma_control(bp, uc_pwr_on, panel_instance, bypass_panel_control_wait);
 }
 
 static bool bios_parser_is_accelerated_mode(
diff --git a/drivers/gpu/drm/amd/display/dc/bios/command_table2.c b/drivers/gpu/drm/amd/display/dc/bios/command_table2.c
index ab0adabf9dd4..90a02d7bd3da 100644
--- a/drivers/gpu/drm/amd/display/dc/bios/command_table2.c
+++ b/drivers/gpu/drm/amd/display/dc/bios/command_table2.c
@@ -976,7 +976,7 @@ static unsigned int get_smu_clock_info_v3_1(struct bios_parser *bp, uint8_t id)
 static enum bp_result enable_lvtma_control(
 	struct bios_parser *bp,
 	uint8_t uc_pwr_on,
-	uint8_t pwrseq_instance,
+	uint8_t panel_instance,
 	uint8_t bypass_panel_control_wait);
 
 static void init_enable_lvtma_control(struct bios_parser *bp)
@@ -989,7 +989,7 @@ static void init_enable_lvtma_control(struct bios_parser *bp)
 static void enable_lvtma_control_dmcub(
 	struct dc_dmub_srv *dmcub,
 	uint8_t uc_pwr_on,
-	uint8_t pwrseq_instance,
+	uint8_t panel_instance,
 	uint8_t bypass_panel_control_wait)
 {
 
@@ -1002,8 +1002,8 @@ static void enable_lvtma_control_dmcub(
 			DMUB_CMD__VBIOS_LVTMA_CONTROL;
 	cmd.lvtma_control.data.uc_pwr_action =
 			uc_pwr_on;
-	cmd.lvtma_control.data.pwrseq_inst =
-			pwrseq_instance;
+	cmd.lvtma_control.data.panel_inst =
+			panel_instance;
 	cmd.lvtma_control.data.bypass_panel_control_wait =
 			bypass_panel_control_wait;
 	dm_execute_dmub_cmd(dmcub->ctx, &cmd, DM_DMUB_WAIT_TYPE_WAIT);
@@ -1012,7 +1012,7 @@ static void enable_lvtma_control_dmcub(
 static enum bp_result enable_lvtma_control(
 	struct bios_parser *bp,
 	uint8_t uc_pwr_on,
-	uint8_t pwrseq_instance,
+	uint8_t panel_instance,
 	uint8_t bypass_panel_control_wait)
 {
 	enum bp_result result = BP_RESULT_FAILURE;
@@ -1021,7 +1021,7 @@ static enum bp_result enable_lvtma_control(
 	bp->base.ctx->dc->debug.dmub_command_table) {
 		enable_lvtma_control_dmcub(bp->base.ctx->dmub_srv,
 uc_pwr_on,
-pwrseq_instance,
+panel_instance,
 bypass_panel_control_wait);
 		return BP_RESULT_OK;
 	}
diff --git a/drivers/gpu/drm/amd/display/dc/bios/command_table2.h b/drivers/gpu/drm/amd/display/dc/bios/command_table2.h
index 41c8c014397f..b6d09bf6cf72 100644
--- a/drivers/gpu/drm/amd/display/dc/bios/command_table2.h
+++ b/drivers/gpu/drm/amd/display/dc/bios/command_table2.h
@@ -96,7 +96,7 @@ struct cmd_tbl {
 			struct bios_parser *bp, uint8_t id);
 	enum bp_result (*enable_lvtma_control)(struct bios_parser *bp,
 			uint8_t u

Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

[Bastian Blank]

Control: tags -1 wontfix

On Wed, Jan 24, 2024 at 06:13:05PM +0100, Paul Menzel wrote:
> Trying to quickly start a VM, it’d be great to not use an initrd image, and
> also use the Virtio features, for example with the command below:

Please use virtiofs in this case.

> qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32
> -device virtio-rng-pci -net nic,model=virtio-net-pci -net
> user,hostfwd=tcp::5-:22 -drive
> if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic

But you don't specify a kernel, so it boots fine using the initramfs
within.  So this already boots quite fine.

I don't see what exactly you mean will be easier.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown

Processed: Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 wontfix
Bug #1061445 [linux-image-6.7-cloud-amd64] linux-image-6.7-cloud-amd64: Built 
CONFIG_VIRTIO_BLK into kernel
Added tag(s) wontfix.

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

Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Patrice Duroux]

Finally, no more complaints!

$ uname -a
Linux kos-moceratops 6.7+unreleased-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.7.1-1~exp1a~test (2024-01-24) x86_64 GNU/Linux

$ sudo dmesg | grep '\(amdgpu\|drm\)'
[1.095216] ACPI: bus type drm_connector registered
[2.085314] i915 :00:02.0: [drm] VT-d active for gfx access
[2.085425] i915 :00:02.0: [drm] Using Transparent Hugepages
[2.087746] i915 :00:02.0: [drm] Finished loading DMC firmware
i915/kbl_dmc_ver1_04.bin (v1.4)
[3.608758] [drm] amdgpu kernel modesetting enabled.
[3.608767] amdgpu: vga_switcheroo: detected switching method
\_SB_.PCI0.GFX0.ATPX handle
[3.608784] amdgpu: ATPX version 1, functions 0x0033
[3.608830] amdgpu: ATPX Hybrid Graphics
[3.610446] amdgpu: Virtual CRAT table created for CPU
[3.610455] amdgpu: Topology: Add CPU node
[3.610550] amdgpu :01:00.0: enabling device ( -> 0003)
[3.610586] [drm] initializing kernel modesetting (POLARIS12
0x1002:0x6981 0x1028:0x0926 0x00).
[3.630941] [drm] register mmio base: 0xB430
[3.630944] [drm] register mmio size: 262144
[3.631086] [drm] add ip block number 0 
[3.631087] [drm] add ip block number 1 
[3.631088] [drm] add ip block number 2 
[3.631089] [drm] add ip block number 3 
[3.631089] [drm] add ip block number 4 
[3.631090] [drm] add ip block number 5 
[3.631091] [drm] add ip block number 6 
[3.631091] [drm] add ip block number 7 
[3.631092] [drm] add ip block number 8 
[3.642892] amdgpu :01:00.0: amdgpu: Fetched VBIOS from ATRM
[3.642895] amdgpu: ATOM BIOS: BR43850.001
[3.642927] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_sdma.bin
[3.642991] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_sdma1.bin
[3.643023] [drm] UVD is enabled in VM mode
[3.643024] [drm] UVD ENC is enabled in VM mode
[3.643026] [drm] VCE enabled in VM mode
[3.643027] amdgpu :01:00.0: amdgpu: Trusted Memory Zone (TMZ)
feature not supported
[3.643036] [drm] GPU posting now...
[3.755975] [drm] vm size is 64 GB, 2 levels, block size is 10-bit,
fragment size is 9-bit
[3.756017] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_k_mc.bin
[3.756122] amdgpu :01:00.0: BAR 2: releasing [mem
0x8000-0x801f 64bit pref]
[3.756124] amdgpu :01:00.0: BAR 0: releasing [mem
0x7000-0x7fff 64bit pref]
[3.756142] amdgpu :01:00.0: BAR 0: assigned [mem
0x41-0x41 64bit pref]
[3.756147] amdgpu :01:00.0: BAR 2: assigned [mem
0x408000-0x40801f 64bit pref]
[3.756162] amdgpu :01:00.0: amdgpu: VRAM: 4096M
0x00F4 - 0x00F4 (4096M used)
[3.756163] amdgpu :01:00.0: amdgpu: GART: 256M
0x00FF - 0x00FF0FFF
[3.756174] [drm] Detected VRAM RAM=4096M, BAR=4096M
[3.756175] [drm] RAM width 128bits GDDR5
[3.756337] [drm] amdgpu: 4096M of VRAM memory ready
[3.756338] [drm] amdgpu: 7879M of GTT memory ready.
[3.756357] [drm] GART: num cpu pages 65536, num gpu pages 65536
[3.756874] [drm] PCIE GART of 256M enabled (table at 0x00F4FFF8).
[3.756946] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_pfp_2.bin
[3.756996] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_me_2.bin
[3.757042] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_ce_2.bin
[3.757063] [drm] Chained IB support enabled!
[3.757072] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_rlc.bin
[3.757146] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_mec_2.bin
[3.757726] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_mec2_2.bin
[3.758564] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[3.758620] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_uvd.bin
[3.759394] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[3.760073] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_vce.bin
[3.760419] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
[3.760798] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris12_k_smc.bin
[4.092386] [drm] Display Core v3.2.259 initialized on DCE 11.2
[4.636780] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon
[4.636791] [drm] Initialized i915 1.6.0 20230929 for :00:02.0 on minor 0
[5.207332] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon
[5.207335] i915 :00:02.0: [drm] *ERROR* LSPCON init failed on port D
[5.607371] fbcon: i915drmfb (fb0) is primary device
[5.629068] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
[6.211671] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon
[6.211682] i915 :00:02.0: [drm] *ERROR* LSPCON init failed on port D
[7.194222] i

Bug#1061460: firmware-nonfree: CVE-2023-4969

[Salvatore Bonaccorso]

Source: firmware-nonfree
Version: 20230625-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for firmware-nonfree.

CVE-2023-4969[0]:
| A GPU kernel can read sensitive data from another GPU kernel (even
| from another user or app) through an optimized GPU memory region
| called _local memory_ on various architectures.

There are though some unclarities about this, so just filling for
keeping track of the issue. [1] mentions that AMD expects to to start
rolling out mitigations beginning of March 2024, so we might see then
more where the mitigations lies and if firmware-nonfree are correct.
They mention there rather "upcoming driver updates".


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-4969
https://www.cve.org/CVERecord?id=CVE-2023-4969
[1] https://www.amd.com/en/resources/product-security/bulletin/amd-sb-6010.html

Regards,
Salvatore

Processed: Re: Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 =upstream
Bug #1061449 [src:linux] linux-image-6.7-amd64: a boot message from amdgpu
Added tag(s) upstream; removed tag(s) moreinfo.

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

Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu

[Diederik de Haas]

Control: tag -1 =upstream

On Wednesday, 24 January 2024 21:41:29 CET Patrice Duroux wrote:
> Finally, no more complaints!
> 
> $ uname -a
> Linux kos-moceratops 6.7+unreleased-amd64 #1 SMP PREEMPT_DYNAMIC
> Debian 6.7.1-1~exp1a~test (2024-01-24) x86_64 GNU/Linux

Excellent, now we know commit b17ef04bf3a4346d66404454d6a646343ddc9749 
introduced the regression.
 
> Does this need further testing from my side?

No, but it should be reported upstream so that an actual fix can be made.
Unfortunately the commit doesn't link to a/the patch discussion (on f.e. 
lore.kernel.org), so I don't know where it should be reported.

Hopefully someone else does ...

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

Bug#1060052: Status?

[Dennis Haney]

Can we please get a new release of a stable kernel?
This keeps crashing our machines, and it is a pain manually updating to the 6.5 
kernel on all of them.

Med venlig hilsen
Dennis Haney d...@voxmeter.dk
Catglobe Direktør Mobil +84 907 42 46 52


Voxmeter A/S   Tlf.: +45 70 20 23 24   Borgergade 6, 4. sal   
DK-1300 København   CVR/VAT: 34217432
Analyser og Interviewarbejde: voxmeter.dk   
Analysesystem: catglobe.com