Your message dated Wed, 19 Feb 2025 16:11:49 +0100 (CET) with message-id <[email protected]> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #995369, regarding linux-image-5.14.0-1-amd64: "kernel BUG at block/bio.c:52!" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 995369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995369 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-5.14.0-1-amd64 Version: 5.14.6-2 Severity: important Dear Maintainer, after upgrade to kernel 5.14, the computer went unstable, various processes hanging at file access, dubious timeout. In kern.log, the following message appears a number of times: Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228648] ------------[ cut here ]------------ Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228651] kernel BUG at block/bio.c:52! Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228659] invalid opcode: 0000 [#1] SMP PTI Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228662] CPU: 1 PID: 53439 Comm: kworker/u8:13 Tainted: G I 5.14.0-1-amd64 #1 Debian 5.14.6-2 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228664] Hardware name: Dell Inc. PowerEdge T30/07T4MC, BIOS 1.5.0 10/28/2020 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228666] Workqueue: writeback wb_workfn (flush-253:2) Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228672] RIP: 0010:biovec_slab.part.0+0x5/0x10 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228675] Code: d1 65 03 00 48 83 3b 00 74 08 48 89 df e8 e3 fe ff ff 48 c7 03 00 00 00 00 5b c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 83 7f 40 00 75 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228677] RSP: 0018:ffffbcaf47863768 EFLAGS: 00010202 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228679] RAX: 00000000000000bf RBX: ffffbcaf4786379c RCX: 00000000000000c0 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228680] RDX: 0000000000000c00 RSI: ffffbcaf4786379c RDI: ffff9a548a507438 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228682] RBP: 0000000000000c00 R08: ffff9a548a507438 R09: ffff9a541a165480 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228683] R10: 0000000000000004 R11: ffff9a548a0f3ef0 R12: ffff9a548a507438 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228684] R13: 0000000000000c00 R14: 0000000000000c00 R15: ffff9a548a5073f0 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228685] FS: 0000000000000000(0000) GS:ffff9a5955c80000(0000) knlGS:0000000000000000 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228688] CR2: 00007fe046e42258 CR3: 0000000410e10006 CR4: 00000000003706e0 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228689] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228690] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228694] bvec_alloc+0x90/0xc0 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228700] raid1_make_request+0x913/0xc40 [raid1] Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228706] md_handle_request+0x122/0x1b0 [md_mod] Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228719] submit_bio_noacct+0x104/0x430 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228725] ext4_bio_write_page+0x30b/0x5b0 [ext4] Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228782] ext4_writepages+0x89c/0xfc0 [ext4] Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228802] do_writepages+0x34/0xc0 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228809] writeback_sb_inodes+0x200/0x470 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228815] wb_writeback+0x1d8/0x290 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228819] ? check_preempt_curr+0x55/0x70 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228824] process_one_work+0x1ec/0x390 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228828] ? process_one_work+0x390/0x390 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228833] ? set_kthread_struct+0x40/0x40 Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228839] Modules linked in: sctp ip6_udp_tunnel udp_tunnel cfg80211 rfkill 8021q garp mrp tun veth nf_tables nfnetlink bfq cpufreq_powersave cpufreq_conservative cpufreq_ondemand cpufreq_userspace uinput bridge stp llc binfmt_misc nls_ascii quota_v2 quota_tree nls_cp437 vfat fat snd_hda_codec_hdmi uvcvideo snd_hda_codec_realtek videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_usb_audio snd_hda_codec_generic videobuf2_common ledtrig_audio snd_hda_intel snd_usbmidi_lib intel_rapl_msr intel_rapl_common videodev snd_rawmidi snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec x86_pkg_temp_thermal snd_seq_device intel_powerclamp kvm_intel mc snd_hda_core kvm irqbypass snd_hwdep snd_pcm_oss rapl joydev intel_cstate snd_mixer_oss iTCO_wdt mei_hdcp intel_pmc_bxt mei_wdt intel_uncore snd_pcm iTCO_vendor_support dell_wmi snd_timer sparse_keymap snd dell_smbios dcdbas soundcore watchdog serio_raw mei_me pcspkr dell_wmi_descriptor ee1004 sg evdev mei intel_pch_thermal ie31200_edac Sep 29 00:00:36 xxxxxxxxxx kernel: [23519.228959] ---[ end trace ab34d149fe4093c9 ]--- The system's harddisk io is setup as MD-managed RAID 1, on top lvm2 using an ATA connected single SSD disk as read cache. Lacking a 2nd SSD disk, write-through to the disk RAID is configured. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert backup_linux BackupVG -wi-ao---- <2,15t MacBack ClientBackVG -wi-ao---- <2,73t home DataVG Cwi-aoC--- 700,00g [home_cache_cpool] [home_corig] 25,43 1,04 0,00 root DataVG -wi-ao---- 25,00g var_lxc DataVG Cwi-aoC--- 1,17t [var_lxc_cache_cpool] [var_lxc_corig] 99,98 0,24 16,58 var_native DataVG Cwi-aoC--- 15,00g [var_native_cache_cpool] [var_native_corig] 19,67 1,30 0,00 $ sudo /sbin/dmsetup status DataVG-var_native 0 31457280 cache 8 1662/128000 128 161138/819200 229608 4283 2571004 36801 0 9488 0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw - I'm not aware of having any of the misconfiguration issues mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=213181 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.14.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod 29-1 ii linux-base 4.6 Versions of packages linux-image-5.14.0-1-amd64 recommends: ii apparmor 3.0.3-2 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.14.0-1-amd64 suggests: ii debian-kernel-handbook 1.0.19 ii grub-efi-amd64 2.04-20 pn linux-doc-5.14 <none>
--- End Message ---
--- Begin Message ---Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---
