Starting a container causes kernel warnings

Incus
1

Hi, I saw this issue a while ago…I was very busy so I just switched to LTS kernel and the issue went away.

Today I have some time so I decided to replicate and report it.

When I start an existing (or a newly created) container, it produces 75 kernel messages in the journalctl. The messages are part of a kernel trace.

Here are the first few lines

Oct 30 17:29:00 Machine kernel: ------------[ cut here ]------------
Oct 30 17:29:00 Machine kernel: WARNING: CPU: 6 PID: 8626 at net/core/dev.c:12440 __dev_change_net_namespace+0xb89/0xc30
Oct 30 17:29:00 Machine kernel: Modules linked in: veth nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock snd_seq_dummy snd_hrtimer snd_seq vfat fat qrtr_>
Oct 30 17:29:00 Machine kernel:  x_tables amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched drm_suballoc_helper nvme drm_panel_backlight_quirks drm_buddy nvme_core drm_display_helper video nvme_keyring cec nvme_auth wmi
Oct 30 17:29:00 Machine kernel: CPU: 6 UID: 0 PID: 8626 Comm: incusd Tainted: G           OE       6.17.5-arch1-1 #1 PREEMPT(full)  01c39fc421df2af799dd5e9180b572af860b40c1
Oct 30 17:29:00 Machine kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE


❯ uname -r                                                                          
6.17.5-arch1-1

The lts-kernel version is

❯ uname -r                                                                          
6.12.56-1-lts

I wish I had noted when (or which updated caused it).

How can I troubleshoot this…

Also apologies, I feel like I am not providing enough information. Please let me know what would be helpful and I will follow up.

2

It’s not a panic, it’s a kernel warning. That issue was reported upstream a few weeks ago already and a fix was merged I believe, so it will eventually go away.

3

Oh I see, Thank you!…is the fix a kernel fix or incus fix :slight_smile:

4

kernel

5

Thank you. 6.17.6-arch1-1 kernel was just released. After upgrade I no longer see the issue…

I think they were just waiting for me to post my issue here :joy: