From: Arthur Marsh <arthur.marsh@internode.on.net>
To: mawupeng1@huawei.com
Cc: akpm@linux-foundation.org, david@redhat.com,
linmiaohe@huawei.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@suse.com, nao.horiguchi@gmail.com,
osalvador@suse.de
Subject: mm: memory-failure: update ttu flag inside unmap_poisoned_folio
Date: Thu, 20 Mar 2025 03:51:52 +1030 [thread overview]
Message-ID: <20250319172153.4702-1-user@am64> (raw)
In-Reply-To: <20250217014329.3610326-2-mawupeng1@huawei.com>
On recent kernel builds on a system with the following CPU with integrated GPU:
AMD Ryzen 5 5500GT with Radeon Graphics
using the integrated GPU, on the following motherboard:
System manufacturer System Product Name/PRIME B350M-A, BIOS 6232 09/29/2024
I've been getting the error below on the initial loading of chromium after
booting, which I git-bisected back to commit
b81679b1633aa43c0d973adfa816d78c1ed0d032 (which I am replying to now):
:
[ 281.651311] WARNING: CPU: 4 PID: 3525 at mm/util.c:674 __kvmalloc_node_noprof+0xc8/0xe0
[ 281.651322] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device fuse bnep bluetooth rfkill cpufreq_userspace cpufreq_conservative cpufreq_powersave binfmt_misc nf_tables scsi_transport_iscsi nfnetlink sch_fq_codel exfat parport_pc ppdev lp parport rtl2832_sdr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev fc0012 rtl2832 i2c_mux regmap_i2c dvb_usb_rtl28xxu amdgpu dvb_usb_v2 dvb_core mc amdxcp gpu_sched snd_hda_codec_realtek snd_hda_codec_hdmi drm_panel_backlight_quirks cec snd_hda_codec_generic drm_buddy drm_ttm_helper ttm snd_hda_scodec_component snd_hda_intel drm_client_lib drm_exec drm_suballoc_helper snd_intel_dspcfg drm_display_helper snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core drm_kms_helper tpm_crb tpm_tis tpm_tis_core snd_hwdep drm snd_pcm tpm edac_mce_amd sha512_ssse3 sha3_generic jitterentropy_rng hmac drbg libaescfb snd_timer ansi_cprng sha512_generic i2c_algo_bit ecdh_generic snd sha256_ssse3 sha1_ssse3
[ 281.651387] ccp aesni_intel ecc video mfd_core gf128mul crypto_simd cryptd button evdev soundcore wmi pcspkr rng_core k10temp ext4 crc16 mbcache jbd2 hid_generic usbhid sg uas sr_mod hid usb_storage cdrom sd_mod sp5100_tco ahci libahci xhci_pci r8169 xhci_hcd libata realtek mdio_devres serio_raw i2c_piix4 usbcore scsi_mod i2c_smbus libphy scsi_common usb_common
[ 281.651424] CPU: 4 UID: 1000 PID: 3525 Comm: chromium Tainted: G W 6.14.0-rc3+ #6448
[ 281.651429] Tainted: [W]=WARN
[ 281.651430] Hardware name: System manufacturer System Product Name/PRIME B350M-A, BIOS 6232 09/29/2024
[ 281.651433] RIP: 0010:__kvmalloc_node_noprof+0xc8/0xe0
[ 281.651436] Code: 64 24 08 41 89 d8 be 01 00 00 00 48 89 ef 48 01 d1 48 89 44 24 10 48 c7 04 24 00 04 00 00 e8 6f 25 04 00 eb 87 80 e7 20 75 82 <0f> 0b 90 0f 1f 44 00 00 e9 75 ff ff ff 66 66 2e 0f 1f 84 00 00 00
[ 281.651438] RSP: 0018:ffffb1334837fc40 EFLAGS: 00010246
[ 281.651440] RAX: 0000000000000000 RBX: 00000000000000c0 RCX: 0000000000000016
[ 281.651442] RDX: 0000000000000016 RSI: ffffffffbe164ba8 RDI: 0000000000052cc0
[ 281.651443] RBP: 0000000498843b00 R08: ffffb1334837fda8 R09: ffffb1334837fdb8
[ 281.651444] R10: 0000000000000018 R11: 0000000000000000 R12: 00000000ffffffff
[ 281.651445] R13: ffffb1334837fcb8 R14: 0000000000000000 R15: ffff997e75680010
[ 281.651446] FS: 00007fda628ef500(0000) GS:ffff99854e700000(0000) knlGS:0000000000000000
[ 281.651447] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 281.651448] CR2: 00007fda6554b302 CR3: 000000013df40000 CR4: 0000000000750ef0
[ 281.651449] PKRU: 55555558
[ 281.651450] Call Trace:
[ 281.651451] <TASK>
[ 281.651453] ? __kvmalloc_node_noprof+0xc8/0xe0
[ 281.651455] ? __warn.cold+0xad/0x109
[ 281.651459] ? __kvmalloc_node_noprof+0xc8/0xe0
[ 281.651461] ? report_bug+0x102/0x190
[ 281.651470] ? handle_bug+0x59/0xa0
[ 281.651474] ? exc_invalid_op+0x1f/0x90
[ 281.651477] ? asm_exc_invalid_op+0x16/0x20
[ 281.651481] ? __kmalloc_node_noprof+0x278/0x360
[ 281.651487] ? __kvmalloc_node_noprof+0xc8/0xe0
[ 281.651489] ? srso_alias_return_thunk+0x5/0xfbef5
[ 281.651491] ? chrdev_open+0xad/0x220
[ 281.651496] amdgpu_bo_create_list_entry_array+0x47/0x120 [amdgpu]
[ 281.651729] amdgpu_bo_list_ioctl+0x4e/0x330 [amdgpu]
[ 281.651823] ? __pfx_amdgpu_bo_list_ioctl+0x10/0x10 [amdgpu]
[ 281.651914] drm_ioctl_kernel+0xa6/0x100 [drm]
[ 281.651942] drm_ioctl+0x236/0x540 [drm]
[ 281.651954] ? __pfx_amdgpu_bo_list_ioctl+0x10/0x10 [amdgpu]
[ 281.652047] ? srso_alias_return_thunk+0x5/0xfbef5
[ 281.652049] ? preempt_count_add+0x51/0xd0
[ 281.652053] ? srso_alias_return_thunk+0x5/0xfbef5
[ 281.652054] ? migrate_enable+0xc0/0xf0
[ 281.652058] amdgpu_drm_ioctl+0x58/0xa0 [amdgpu]
[ 281.652138] __x64_sys_ioctl+0x55f/0xab0
[ 281.652143] ? srso_alias_return_thunk+0x5/0xfbef5
[ 281.652145] ? do_sys_openat2+0x74/0xb0
[ 281.652148] ? do_user_addr_fault+0x3a0/0x660
[ 281.652153] do_syscall_64+0x47/0x110
[ 281.652155] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 281.652157] RIP: 0033:0x7fda65ad08db
[ 281.652159] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[ 281.652160] RSP: 002b:00007ffc93108640 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 281.652162] RAX: ffffffffffffffda RBX: 00003cfc000ac640 RCX: 00007fda65ad08db
[ 281.652162] RDX: 00007ffc931086f0 RSI: 00000000c0106443 RDI: 0000000000000014
[ 281.652163] RBP: 00007ffc931086f0 R08: 0000000000000000 R09: 0000000000000000
[ 281.652164] R10: 000000000000006c R11: 0000000000000246 R12: 00000000c0106443
[ 281.652165] R13: 0000000000000014 R14: 00007ffc93108760 R15: 00003cfc000ac658
[ 281.652168] </TASK>
[ 281.652168] ---[ end trace 0000000000000000 ]---
chromium still loads and runs fine, but I am left wondering why this message
is appearing.
I can supply full dmesg and .config if required.
Arthur.
next prev parent reply other threads:[~2025-03-19 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 1:43 [PATCH v3 0/3] mm: memory_failure: unmap poisoned filio during migrate properly Wupeng Ma
2025-02-17 1:43 ` [PATCH v3 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio Wupeng Ma
2025-02-19 2:50 ` Miaohe Lin
2025-02-19 3:34 ` mawupeng
2025-02-19 6:06 ` [PATCH v3] " Wupeng Ma
2025-02-19 23:41 ` Andrew Morton
2025-03-19 17:21 ` Arthur Marsh [this message]
2025-03-20 2:40 ` mawupeng
2025-02-17 1:43 ` [PATCH v3 2/3] mm: memory-hotplug: check folio ref count first in do_migrate_range Wupeng Ma
2025-02-17 9:30 ` David Hildenbrand
2025-02-19 3:15 ` Miaohe Lin
2025-02-17 1:43 ` [PATCH v3 3/3] hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Wupeng Ma
2025-02-19 3:17 ` Miaohe Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250319172153.4702-1-user@am64 \
--to=arthur.marsh@internode.on.net \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox