[opensuse] Memory corruption detected in low memory
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, What should I think of this? It is a warning, not an error, apparently. In the BIOS, perhaps. <0.3> 2016-12-11T13:37:26.094997+01:00 Isengard kernel - - - [382640.164069] Corrupted low memory at ffff880000002000 (2000 phys) = 0000f0f6 <0.4> 2016-12-11T13:37:26.095031+01:00 Isengard kernel - - - [382640.164092] ------------[ cut here ]------------ <0.4> 2016-12-11T13:37:26.095034+01:00 Isengard kernel - - - [382640.164111] WARNING: CPU: 1 PID: 7380 at ../arch/x86/kernel/check.c:141 check_for_bios_corruption+0xf9/0x110() <0.3> 2016-12-11T13:37:26.095036+01:00 Isengard kernel - - - [382640.164114] Memory corruption detected in low memory <0.4> 2016-12-11T13:37:26.095037+01:00 Isengard kernel - - - [382640.164116] Modules linked in: rfcomm fuse nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_recent af_packet iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT nf_reject_ipv4 iptable_raw xt_CT iptable_filter bnep ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic xfs libcrc32c intel_rapl intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel jitterentropy_rng nls_iso8859_1 arc4 nls_cp437 vfat fat dm_mod drbg ansi_cprng joydev hid_logitech_hidpp iTCO_wdt iTCO_vendor_support iwlmvm mac80211 msi_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_intel_sst_acpi i915 snd_hda_core aesni_intel snd_intel_sst_core drm_kms_helper btusb iwlwifi drm aes_x86_64 btrtl snd_soc_rt5670 lrw fb_sys_fops btbcm gf128mul snd_soc_sst_mfld_platform hid_logitech_dj pcspkr r8169 btintel snd_hwdep serio_raw snd_soc_rl6231 lpc_ich glue_helper bluetooth mii mfd_core ablk_helper cryptd snd_soc_core i2c_i801 cfg80211 nxp_nci_i2c snd_compress syscopyarea sysfillrect sysimgblt nxp_nci mei_txe i2c_algo_bit shpchp mei snd_pcm nci thermal fan nfc snd_timer regmap_i2c battery snd wmi fjes i2c_designware_platform i2c_designware_core video rfkill_gpio rfkill soundcore 8250_dw pwm_lpss_platform pwm_lpss pinctrl_cherryview button processor sunrpc ext4 crc16 jbd2 mbcache uas usb_storage usbhid sd_mod ahci libahci xhci_pci xhci_hcd usbcore usb_common libata sdhci_pci i2c_hid sdhci_acpi sdhci mmc_core sg scsi_mod efivarfs autofs4 <0.4> 2016-12-11T13:37:26.095040+01:00 Isengard kernel - - - [382640.164309] CPU: 1 PID: 7380 Comm: kworker/1:2 Not tainted 4.4.27-2-default #1 <0.4> 2016-12-11T13:37:26.095042+01:00 Isengard kernel - - - [382640.164313] Hardware name: Micro-Star International Co., Ltd. MS-B120/MS-B120, BIOS EB120IMS.820 03/03/2016 <0.4> 2016-12-11T13:37:26.095043+01:00 Isengard kernel - - - [382640.164321] Workqueue: events check_corruption <0.4> 2016-12-11T13:37:26.095044+01:00 Isengard kernel - - - [382640.164323] 0000000000000000 ffffffff81327657 ffff880063aa7d98 ffffffff81a4c986 <0.4> 2016-12-11T13:37:26.095046+01:00 Isengard kernel - - - [382640.164329] ffffffff8107e821 0000000000000000 ffff880063aa7de8 ffffffff821edff0 <0.4> 2016-12-11T13:37:26.095047+01:00 Isengard kernel - - - [382640.164334] 0000000000000001 ffff880000000000 ffffffff8107e89c ffffffff81a43dc0 <0.4> 2016-12-11T13:37:26.095048+01:00 Isengard kernel - - - [382640.164340] Call Trace: <0.4> 2016-12-11T13:37:26.095049+01:00 Isengard kernel - - - [382640.164358] [<ffffffff81019e69>] dump_trace+0x59/0x320 <0.4> 2016-12-11T13:37:26.095051+01:00 Isengard kernel - - - [382640.164368] [<ffffffff8101a22a>] show_stack_log_lvl+0xfa/0x180 <0.4> 2016-12-11T13:37:26.095052+01:00 Isengard kernel - - - [382640.164372] [<ffffffff8101afd1>] show_stack+0x21/0x40 <0.4> 2016-12-11T13:37:26.095053+01:00 Isengard kernel - - - [382640.164380] [<ffffffff81327657>] dump_stack+0x5c/0x85 <0.4> 2016-12-11T13:37:26.095054+01:00 Isengard kernel - - - [382640.164387] [<ffffffff8107e821>] warn_slowpath_common+0x81/0xb0 <0.4> 2016-12-11T13:37:26.095056+01:00 Isengard kernel - - - [382640.164395] [<ffffffff8107e89c>] warn_slowpath_fmt+0x4c/0x50 <0.4> 2016-12-11T13:37:26.095057+01:00 Isengard kernel - - - [382640.164400] [<ffffffff81060da9>] check_for_bios_corruption+0xf9/0x110 <0.4> 2016-12-11T13:37:26.095058+01:00 Isengard kernel - - - [382640.164408] [<ffffffff81060dca>] check_corruption+0xa/0x40 <0.4> 2016-12-11T13:37:26.095059+01:00 Isengard kernel - - - [382640.164413] [<ffffffff81097205>] process_one_work+0x155/0x440 <0.4> 2016-12-11T13:37:26.095060+01:00 Isengard kernel - - - [382640.164418] [<ffffffff81097d46>] worker_thread+0x116/0x4b0 <0.4> 2016-12-11T13:37:26.095062+01:00 Isengard kernel - - - [382640.164425] [<ffffffff8109d328>] kthread+0xc8/0xe0 <0.4> 2016-12-11T13:37:26.095063+01:00 Isengard kernel - - - [382640.164433] [<ffffffff8160978f>] ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095064+01:00 Isengard kernel - - - [382640.167228] DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095065+01:00 Isengard kernel - - - [382640.167231] <0.4> 2016-12-11T13:37:26.095067+01:00 Isengard kernel - - - [382640.167232] Leftover inexact backtrace: <0.4> 2016-12-11T13:37:26.095068+01:00 Isengard kernel - - - [382640.167232] <0.4> 2016-12-11T13:37:26.095069+01:00 Isengard kernel - - - [382640.167242] [<ffffffff8109d260>] ? kthread_park+0x50/0x50 <0.4> 2016-12-11T13:37:26.095070+01:00 Isengard kernel - - - [382640.167246] ---[ end trace 3ac627478cecce4d ]--- Machine is running Leap 42.2. Memtest passed with no errors. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhOGPwACgkQja8UbcUWM1xB/QD+JiVm8KxuWPXm9fttxKprFwet krWdsThsByUE4z/4eaAA/0g9R8zr4TWNZFRKLb0zLzdx3k7AApHj+i4Zbk2bRyc7 =d7FR -----END PGP SIGNATURE----- N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�: �{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz��
12.12.2016 06:26, Carlos E. R. пишет:
Hi,
What should I think of this?
Some BIOSes are known to corrupt low memory under some condition (like resuming from suspend). Kernel contains check that tries to detect this condition and avoid using this area. See memory_corruption_check and memory_corruption_check_size kernel parameters. So there is little you can do except attempt to find BIOS update or report it to your BIOS/motherboard vendor.
It is a warning, not an error, apparently. In the BIOS, perhaps.
<0.3> 2016-12-11T13:37:26.094997+01:00 Isengard kernel - - - [382640.164069] Corrupted low memory at ffff880000002000 (2000 phys) = 0000f0f6 <0.4> 2016-12-11T13:37:26.095031+01:00 Isengard kernel - - - [382640.164092] ------------[ cut here ]------------ <0.4> 2016-12-11T13:37:26.095034+01:00 Isengard kernel - - - [382640.164111] WARNING: CPU: 1 PID: 7380 at ../arch/x86/kernel/check.c:141 check_for_bios_corruption+0xf9/0x110() <0.3> 2016-12-11T13:37:26.095036+01:00 Isengard kernel - - - [382640.164114] Memory corruption detected in low memory <0.4> 2016-12-11T13:37:26.095037+01:00 Isengard kernel - - - [382640.164116] Modules linked in: rfcomm fuse nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_recent af_packet iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT nf_reject_ipv4 iptable_raw xt_CT iptable_filter bnep ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic xfs libcrc32c intel_rapl intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel jitterentropy_rng nls_iso8859_1 arc4 nls_cp437 vfat fat dm_mod drbg ansi_cprng joydev hid_logitech_hidpp iTCO_wdt iTCO_vendor_support iwlmvm mac80211 msi_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_intel_sst_acpi i915 snd_hda_core aesni_intel snd_intel_sst_core drm_kms_helper btusb iwlwifi drm aes_x86_64 btrtl snd_soc_rt5670 lrw fb_sys_fops btbcm gf128mul snd_soc_sst_mfld_platform hid_logitech_dj pcspkr r8169 btintel snd_hwdep serio_raw snd_soc_rl6231 lpc_ich glue_helper bluetooth mii mfd_core ablk_helper cryptd snd_soc_core i2c_i801 cfg80211 nxp_nci_i2c snd_compress syscopyarea sysfillrect sysimgblt nxp_nci mei_txe i2c_algo_bit shpchp mei snd_pcm nci thermal fan nfc snd_timer regmap_i2c battery snd wmi fjes i2c_designware_platform i2c_designware_core video rfkill_gpio rfkill soundcore 8250_dw pwm_lpss_platform pwm_lpss pinctrl_cherryview button processor sunrpc ext4 crc16 jbd2 mbcache uas usb_storage usbhid sd_mod ahci libahci xhci_pci xhci_hcd usbcore usb_common libata sdhci_pci i2c_hid sdhci_acpi sdhci mmc_core sg scsi_mod efivarfs autofs4 <0.4> 2016-12-11T13:37:26.095040+01:00 Isengard kernel - - - [382640.164309] CPU: 1 PID: 7380 Comm: kworker/1:2 Not tainted 4.4.27-2-default #1 <0.4> 2016-12-11T13:37:26.095042+01:00 Isengard kernel - - - [382640.164313] Hardware name: Micro-Star International Co., Ltd. MS-B120/MS-B120, BIOS EB120IMS.820 03/03/2016 <0.4> 2016-12-11T13:37:26.095043+01:00 Isengard kernel - - - [382640.164321] Workqueue: events check_corruption <0.4> 2016-12-11T13:37:26.095044+01:00 Isengard kernel - - - [382640.164323] 0000000000000000 ffffffff81327657 ffff880063aa7d98 ffffffff81a4c986 <0.4> 2016-12-11T13:37:26.095046+01:00 Isengard kernel - - - [382640.164329] ffffffff8107e821 0000000000000000 ffff880063aa7de8 ffffffff821edff0 <0.4> 2016-12-11T13:37:26.095047+01:00 Isengard kernel - - - [382640.164334] 0000000000000001 ffff880000000000 ffffffff8107e89c ffffffff81a43dc0 <0.4> 2016-12-11T13:37:26.095048+01:00 Isengard kernel - - - [382640.164340] Call Trace: <0.4> 2016-12-11T13:37:26.095049+01:00 Isengard kernel - - - [382640.164358] [<ffffffff81019e69>] dump_trace+0x59/0x320 <0.4> 2016-12-11T13:37:26.095051+01:00 Isengard kernel - - - [382640.164368] [<ffffffff8101a22a>] show_stack_log_lvl+0xfa/0x180 <0.4> 2016-12-11T13:37:26.095052+01:00 Isengard kernel - - - [382640.164372] [<ffffffff8101afd1>] show_stack+0x21/0x40 <0.4> 2016-12-11T13:37:26.095053+01:00 Isengard kernel - - - [382640.164380] [<ffffffff81327657>] dump_stack+0x5c/0x85 <0.4> 2016-12-11T13:37:26.095054+01:00 Isengard kernel - - - [382640.164387] [<ffffffff8107e821>] warn_slowpath_common+0x81/0xb0 <0.4> 2016-12-11T13:37:26.095056+01:00 Isengard kernel - - - [382640.164395] [<ffffffff8107e89c>] warn_slowpath_fmt+0x4c/0x50 <0.4> 2016-12-11T13:37:26.095057+01:00 Isengard kernel - - - [382640.164400] [<ffffffff81060da9>] check_for_bios_corruption+0xf9/0x110 <0.4> 2016-12-11T13:37:26.095058+01:00 Isengard kernel - - - [382640.164408] [<ffffffff81060dca>] check_corruption+0xa/0x40 <0.4> 2016-12-11T13:37:26.095059+01:00 Isengard kernel - - - [382640.164413] [<ffffffff81097205>] process_one_work+0x155/0x440 <0.4> 2016-12-11T13:37:26.095060+01:00 Isengard kernel - - - [382640.164418] [<ffffffff81097d46>] worker_thread+0x116/0x4b0 <0.4> 2016-12-11T13:37:26.095062+01:00 Isengard kernel - - - [382640.164425] [<ffffffff8109d328>] kthread+0xc8/0xe0 <0.4> 2016-12-11T13:37:26.095063+01:00 Isengard kernel - - - [382640.164433] [<ffffffff8160978f>] ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095064+01:00 Isengard kernel - - - [382640.167228] DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095065+01:00 Isengard kernel - - - [382640.167231] <0.4> 2016-12-11T13:37:26.095067+01:00 Isengard kernel - - - [382640.167232] Leftover inexact backtrace: <0.4> 2016-12-11T13:37:26.095068+01:00 Isengard kernel - - - [382640.167232] <0.4> 2016-12-11T13:37:26.095069+01:00 Isengard kernel - - - [382640.167242] [<ffffffff8109d260>] ? kthread_park+0x50/0x50 <0.4> 2016-12-11T13:37:26.095070+01:00 Isengard kernel - - - [382640.167246] ---[ end trace 3ac627478cecce4d ]---
Machine is running Leap 42.2. Memtest passed with no errors.
N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�: �{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz�
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-12 04:42, Andrei Borzenkov wrote:
12.12.2016 06:26, Carlos E. R. пишет:
Hi,
What should I think of this?
Some BIOSes are known to corrupt low memory under some condition (like resuming from suspend). Kernel contains check that tries to detect this condition and avoid using this area. See memory_corruption_check and memory_corruption_check_size kernel parameters.
Thanks, I'll do some reading. Yes, I think I saw messages after hibernation, but this time there wasn't any hibernation. It happened 5 days after boot. So the kernel finds the affected areas and try to not use them. Then maybe I can ignore the issue, mostly.
So there is little you can do except attempt to find BIOS update or report it to your BIOS/motherboard vendor.
I'll try to find updates, yes. The vendor I think will ignore reports coming from Linux users. Thanks! - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhOH84ACgkQja8UbcUWM1z+uQD/UabKiU0FnvA8lKtqnbRqAeFC yxfPNsXpSCxq+Brmg1IA/A38qZN4aB0Y3AzZLImgBj3WzAVkh1E9R7VpCZtJpz87 =qGo7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
12.12.2016 06:55, Carlos E. R. пишет:
On 2016-12-12 04:42, Andrei Borzenkov wrote:
12.12.2016 06:26, Carlos E. R. пишет:
Hi,
What should I think of this?
Some BIOSes are known to corrupt low memory under some condition (like resuming from suspend). Kernel contains check that tries to detect this condition and avoid using this area. See memory_corruption_check and memory_corruption_check_size kernel parameters.
Thanks, I'll do some reading. Yes, I think I saw messages after hibernation, but this time there wasn't any hibernation. It happened 5 days after boot.
So the kernel finds the affected areas and try to not use them. Then maybe I can ignore the issue, mostly.
So there is little you can do except attempt to find BIOS update or report it to your BIOS/motherboard vendor.
I'll try to find updates, yes. The vendor I think will ignore reports coming from Linux users.
There is some chance that it is false positive so you may consider opening bug report to verify.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-12 04:59, Andrei Borzenkov wrote:
12.12.2016 06:55, Carlos E. R. пишет:
On 2016-12-12 04:42, Andrei Borzenkov wrote:
12.12.2016 06:26, Carlos E. R. пишет:
So there is little you can do except attempt to find BIOS update or report it to your BIOS/motherboard vendor.
I'll try to find updates, yes. The vendor I think will ignore reports coming from Linux users.
There is some chance that it is false positive so you may consider opening bug report to verify.
Oh. Ok. Anyway, I don't have local access to the machine at the moment, so perhaps I'll wait till I do. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhOfV0ACgkQja8UbcUWM1yxRQD/dJ0hCplPQo95gU1P7ewbLcgP NRr5U4ZDQilujsEShg0A/jH0IaKMjfbyv52+RZuZYpGe4Q6d4sjaNA9TVWC8VEbN =ej9K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alpine.LSU.2.20.1612161320500.9802@zvanf-gvevgu.inyvabe> El 2016-12-12 a las 06:42 +0300, Andrei Borzenkov escribió:
12.12.2016 06:26, Carlos E. R. пишет:
Hi,
What should I think of this?
Some BIOSes are known to corrupt low memory under some condition (like resuming from suspend). Kernel contains check that tries to detect this condition and avoid using this area. See memory_corruption_check and memory_corruption_check_size kernel parameters.
So there is little you can do except attempt to find BIOS update or report it to your BIOS/motherboard vendor.
It is a warning, not an error, apparently. In the BIOS, perhaps.
<0.3> 2016-12-11T13:37:26.094997+01:00 Isengard kernel - - - [382640.164069] Corrupted low memory at ffff880000002000 (2000 phys) = 0000f0f6 <0.4> 2016-12-11T13:37:26.095031+01:00 Isengard kernel - - - [382640.164092] ------------[ cut here ]------------ <0.4> 2016-12-11T13:37:26.095034+01:00 Isengard kernel - - - [382640.164111] WARNING: CPU: 1 PID: 7380 at ../arch/x86/kernel/check.c:141 check_for_bios_corruption+0xf9/0x110() <0.3> 2016-12-11T13:37:26.095036+01:00 Isengard kernel - - - [382640.164114] Memory corruption detected in low memory
I found some insteresting links, courtesy of another poster off-list. http://unix.stackexchange.com/questions/111923/memory-corruption-detected-in... https://bbs.archlinux.org/viewtopic.php?id=189483 Mostly posts #1 and #18 from second link. I'll quote some bits: +++............................ (#1 2014-11-06 10:43:08 - KRTac) ... In case someone else comes across that type of error: The problem is a poorly designed BIOS that uses parts of RAM that it shouldn't. The kernel checks for those BIOSes and reports the "Corrupted low memory" message. The kernel then ignores that part of the memory and proceeds with system startup. The system will start and work just fine. If you want to get rid of that annoying message, you can explicitly tell the kernel to ignore the first 64KB of memory (which is the part the BIOS might use) with the memmap boot option. Then the kernel no longer needs to check for memory corruption since it won't use that part of the memory anymore. You do that with the memory_corruption_check option. For details see mich41's post. (#18 2014-11-06 16:29:59 - ewaller (admin)) KRTac wrote:
So the memory corruption error indicates that the BIOS is using that part of the memory? So the memory corruption doesn't happen/doesn't affect what goes on in the kernel?
The point is, the BIOS is not supposed to be using that memory without letting other things know. A popular OS from the US Pacific Northwest does not use that memory, so lazy BIOS developers use that space without bothering to do it the right way. Other operating systems, like Linux, might try to use that space and the invisible hand of the BIOS reaches out and corrupts what is in that space. The linux developers are aware of these quirks and have to work around them, This message means that they caught the brain dead BIOS changing that memory red-handed, As there is nothing they can do about it, they set a flag that tells them to ignore that corruptible memory, and it posts a message to the owner of the machine in the hopes they will write a strongly worded letter to the chuckleheads that market buggy hardware. If Linux were to universally ignore that space, they would ignore perfectly good memory on machines that were properly designed and tested. ............................++- So, for practical purposes I can, for the moment, safely ignore that message, and later, map out the first 64KB. Then, search for a bios update for that machine (if found, disable the map out for testing it). About the "strongly worded letter" they would have to say that in the error message with a link to a template. How would I know what to write? And finally, I could also write a bugzilla, just in case. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhT36IACgkQja8UbcUWM1zTFAD9GF+AWH4gC/53e+SUB348+vwQ 2YyJ/gx42vPZYT2BxysA/iT6D8tCPc24hjyMFyWfeUIri2M7080o8xbsWtwJNPn2 =BYMJ -----END PGP SIGNATURE-----
participants (2)
-
Andrei Borzenkov -
Carlos E. R.