Suggestion on this error welcome

OS 13.2 _64

Snip from dmesg

[17641.696028] Corrupted low memory at ffff88000000cae8 (cae8 phys) = 400000000000
[17641.696034] ------------ cut here ]------------
[17641.696041] WARNING: CPU: 0 PID: 3169 at ../arch/x86/kernel/check.c:140 check_for_bios_corruption+0x107/0x110()
[17641.696043] Memory corruption detected in low memory
[17641.696044] Modules linked in: usblp fuse af_packet cfg80211 rfkill snd_hda_codec_hdmi ppdev iTCO_wdt iTCO_vendor_support gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq parport_pc parport snd_seq_device snd_timer coretemp kvm_intel kvm serio_raw snd acpi_cpufreq r8169 mii pcspkr processor i2c_i801 lpc_ich mfd_core soundcore shpchp dm_mod sr_mod cdrom uas usb_storage nvidia_uvm(PO) nvidia(PO) ata_generic ata_piix firewire_ohci firewire_core crc_itu_t pata_it8213 drm button sg
[17641.696088] CPU: 0 PID: 3169 Comm: kworker/0:0 Tainted: P           O  3.16.7-21-desktop #1
[17641.696090] Hardware name: Gigabyte Technology Co., Ltd. EP43-DS3/EP43-DS3, BIOS F9 09/24/2008
[17641.696094] Workqueue: events check_corruption
[17641.696096]  0000000000000009 ffffffff8161c373 ffff8800d2a67d90 ffffffff8105caf7
[17641.696099]  0000000000000000 ffff8800d2a67de0 ffffffff820d38f0 0000000000000001
[17641.696102]  ffff880000000000 ffffffff8105cb5c ffffffff81a19ab8 ffff880200000018
[17641.696106] Call Trace:
[17641.696118]  <ffffffff810051ee>] dump_trace+0x8e/0x350
[17641.696123]  <ffffffff81005556>] show_stack_log_lvl+0xa6/0x190
[17641.696127]  <ffffffff81006c51>] show_stack+0x21/0x50
[17641.696132]  <ffffffff8161c373>] dump_stack+0x49/0x6a
[17641.696137]  <ffffffff8105caf7>] warn_slowpath_common+0x77/0x90
[17641.696142]  <ffffffff8105cb5c>] warn_slowpath_fmt+0x4c/0x50
[17641.696146]  <ffffffff81045077>] check_for_bios_corruption+0x107/0x110
[17641.696150]  <ffffffff8104508a>] check_corruption+0xa/0x40
[17641.696155]  <ffffffff8107711d>] process_one_work+0x16d/0x460
[17641.696160]  <ffffffff81077a05>] worker_thread+0x115/0x510
[17641.696164]  <ffffffff8107dd7d>] kthread+0xbd/0xe0
[17641.696169]  <ffffffff81622fd8>] ret_from_fork+0x58/0x90
[17641.696173] --- end trace 281eba582acc728d ]---

This is after coming out of suspend/hibernate? A regression in the kernel perhaps…


Perhaps I should try running the previous kernel and see if this happens. It’s a new happening for me

Yes, if you can, then would log as a bug.