linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yu Zhao <yuzhao@google.com>
To: kernel test robot <yujie.liu@intel.com>
Cc: lkp@lists.01.org, "kernel test robot" <lkp@intel.com>,
	"Steev Klimaszewski" <steev@kali.org>,
	"Brian Geffon" <bgeffon@google.com>,
	"Jan Alexander Steffens (heftig)" <heftig@archlinux.org>,
	"Oleksandr Natalenko" <oleksandr@natalenko.name>,
	"Steven Barrett" <steven@liquorix.net>,
	"Suleiman Souhlal" <suleiman@google.com>,
	"Daniel Byrne" <djbyrne@mtu.edu>,
	"Donald Carr" <d@chaos-reins.com>,
	"Holger Hoffstätte" <holger@applied-asynchrony.com>,
	"Konstantin Kharlamov" <Hi-Angel@yandex.ru>,
	"Shuang Zhai" <szhai2@cs.rochester.edu>,
	"Sofia Trinh" <sofia.trinh@edi.works>,
	"Vaibhav Jain" <vaibhav@linux.ibm.com>,
	Linux-MM <linux-mm@kvack.org>
Subject: Re: [mm] d88f8edb09: dmesg.Kernel_panic-not_syncing:Fatal_exception
Date: Wed, 24 Aug 2022 22:18:05 -0600	[thread overview]
Message-ID: <CAOUHufYrGRzMPsAygCeV49JvSTY-jr88aLtJdFH+-=vTkwZqsw@mail.gmail.com> (raw)
In-Reply-To: <15cd6083-061c-8d1a-3042-bf40bc1184d4@intel.com>

On Wed, Aug 24, 2022 at 7:55 PM kernel test robot <yujie.liu@intel.com> wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with clang-16):
>
> commit: d88f8edb095214f8c36eeec6b89cebcfcbe3ea62 ("mm: multi-gen LRU: optimize multiple memcgs")
> https://github.com/steev/linux lenovo-x13s-5.19.0
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> [    5.440406][    T1] general protection fault, probably for non-canonical address 0xe686464b00000166: 0000 [#1] KASAN PTI
> [    5.441841][    T1] KASAN: maybe wild-memory-access in range [0x3432525800000b30-0x3432525800000b37]
> [    5.443045][    T1] CPU: 0 PID: 1 Comm: swapper Tainted: G                T 5.19.0-00144-gd88f8edb0952 #1
> [    5.443471][    T1] RIP: 0010:drm_atomic_helper_check_modeset+0x59/0x2c80
> [    5.443471][    T1] Code: 03 48 89 85 20 ff ff ff 42 80 3c 20 00 74 08 4c 89 f7 e8 7a a0 b6 fe 48 89 5d a8 bb 30 08 00 00 49 03 1e 48 89 d8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 b6 2a 00 00 83 3b 00 4c 89 b5 58 ff ff
> [    5.443471][    T1] RSP: 0018:ffffc9000001f580 EFLAGS: 00010206
> [    5.443471][    T1] RAX: 06864a4b00000166 RBX: 3432525800000b30 RCX: ffffc9000001f890
> [    5.443471][    T1] RDX: dffffc0000000000 RSI: ffffc9000001f888 RDI: ffffc9000001f888
> [    5.443471][    T1] RBP: ffffc9000001f6c0 R08: ffff88811d82c800 R09: ffffc9000001f898
> [    5.443471][    T1] R10: ffffc9000001f88c R11: ffffffff82b8a800 R12: dffffc0000000000
> [    5.443471][    T1] R13: 1ffff92000003f13 R14: ffffc9000001f890 R15: 0000000000000014
> [    5.443471][    T1] FS:  0000000000000000(0000) GS:ffffffff880c6000(0000) knlGS:0000000000000000
> [    5.443471][    T1] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    5.443471][    T1] CR2: 00007f6aae86f480 CR3: 0000000008036000 CR4: 00000000000406f0
> [    5.443471][    T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [    5.443471][    T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [    5.443471][    T1] Call Trace:
> [    5.443471][    T1]  <TASK>
> [    5.443471][    T1]  ? validate_chain+0x1379/0x5b80
> [    5.443471][    T1]  drm_atomic_helper_check+0x18/0x100
> [    5.443471][    T1]  drm_get_format_info+0x67/0x180
> [    5.443471][    T1]  drm_internal_framebuffer_create+0x280/0x19c0
> [    5.443471][    T1]  drm_mode_addfb2+0x9b/0x300
> [    5.443471][    T1]  drm_mode_addfb+0x25d/0x580
> [    5.443471][    T1]  drm_client_framebuffer_create+0x412/0x8c0
> [    5.443471][    T1]  drm_fb_helper_generic_probe+0x191/0x980
> [    5.443471][    T1]  ? __kasan_check_write+0x14/0x40
> [    5.443471][    T1]  ? __mutex_unlock_slowpath+0x1d7/0x740
> [    5.443471][    T1]  __drm_fb_helper_initial_config_and_unlock+0x1159/0x1b80
> [    5.443471][    T1]  drm_fbdev_client_hotplug+0x547/0x740
> [    5.443471][    T1]  drm_fbdev_generic_setup+0x13b/0x3c0
> [    5.443471][    T1]  vkms_init+0x4b6/0x640
> [    5.443471][    T1]  ? vgem_init+0x240/0x240
> [    5.443471][    T1]  do_one_initcall+0x16d/0x440
> [    5.443471][    T1]  ? vgem_init+0x240/0x240
> [    5.443471][    T1]  do_initcall_level+0x1a3/0x280
> [    5.443471][    T1]  do_initcalls+0x4b/0x80
> [    5.443471][    T1]  do_basic_setup+0x69/0x80
> [    5.443471][    T1]  kernel_init_freeable+0xe2/0x180
> [    5.443471][    T1]  ? rest_init+0x140/0x140
> [    5.443471][    T1]  kernel_init+0x18/0x1c0
> [    5.443471][    T1]  ? rest_init+0x140/0x140
> [    5.443471][    T1]  ret_from_fork+0x22/0x30
> [    5.443471][    T1]  </TASK>
> [    5.443471][    T1] Modules linked in:
> [    5.476918][    T1] ---[ end trace 0000000000000000 ]---
> [    5.477623][    T1] RIP: 0010:drm_atomic_helper_check_modeset+0x59/0x2c80
> [    5.478507][    T1] Code: 03 48 89 85 20 ff ff ff 42 80 3c 20 00 74 08 4c 89 f7 e8 7a a0 b6 fe 48 89 5d a8 bb 30 08 00 00 49 03 1e 48 89 d8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 b6 2a 00 00 83 3b 00 4c 89 b5 58 ff ff
> [    5.481043][    T1] RSP: 0018:ffffc9000001f580 EFLAGS: 00010206
> [    5.481851][    T1] RAX: 06864a4b00000166 RBX: 3432525800000b30 RCX: ffffc9000001f890
> [    5.482887][    T1] RDX: dffffc0000000000 RSI: ffffc9000001f888 RDI: ffffc9000001f888
> [    5.483950][    T1] RBP: ffffc9000001f6c0 R08: ffff88811d82c800 R09: ffffc9000001f898
> [    5.484993][    T1] R10: ffffc9000001f88c R11: ffffffff82b8a800 R12: dffffc0000000000
> [    5.486020][    T1] R13: 1ffff92000003f13 R14: ffffc9000001f890 R15: 0000000000000014
> [    5.487054][    T1] FS:  0000000000000000(0000) GS:ffffffff880c6000(0000) knlGS:0000000000000000
> [    5.488258][    T1] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    5.489116][    T1] CR2: 00007f6aae86f480 CR3: 0000000008036000 CR4: 00000000000406f0
> [    5.490109][    T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [    5.491150][    T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [    5.492241][    T1] Kernel panic - not syncing: Fatal exception
> [    5.493037][    T1] Kernel Offset: disabled
>
>
> =========================================================================================
> tbox_group/testcase/rootfs/kconfig/compiler/sleep:
>      vm-snb/boot/yocto-x86_64-minimal-20190520.cgz/x86_64-randconfig-a003-20220801/clang-16/1
>
> commit:
>      fe2bb20302a87cfeda355e4be3cc3029478a5214
>      d88f8edb095214f8c36eeec6b89cebcfcbe3ea62
>
> fe2bb20302a87cfe d88f8edb095214f8c36eeec6b89
> ---------------- ---------------------------
>           fail:runs  %reproduction    fail:runs
>               |             |             |
>               :30         133%          40:40    dmesg.Kernel_panic-not_syncing:Fatal_exception
>               :30         133%          40:40    dmesg.RIP:drm_atomic_helper_check_modeset
>
>
> The kconfig of this boot test has "# CONFIG_LRU_GEN is not set"

This means the aforementioned commit was not built at all. So it
shouldn't cause the crash.

> We also tried to enable CONFIG_LRU_GEN and re-test it, then boot is successful.

Nor should it fix the crash.

> https://github.com/steev/linux lenovo-x13s-5.19.0

This tree has other patches. In case you want to make sure MGLRU has
nothing to do with the crash, please try the patchset on top of the
official 5.19.0 and try again.

Thanks.


  reply	other threads:[~2022-08-25  4:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220824053353.GA45627@inn2.lkp.intel.com>
2022-08-25  1:54 ` kernel test robot
2022-08-25  4:18   ` Yu Zhao [this message]
2022-09-01  9:04     ` [LKP] " Yujie Liu
2022-09-01 19:28       ` Nathan Chancellor

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='CAOUHufYrGRzMPsAygCeV49JvSTY-jr88aLtJdFH+-=vTkwZqsw@mail.gmail.com' \
    --to=yuzhao@google.com \
    --cc=Hi-Angel@yandex.ru \
    --cc=bgeffon@google.com \
    --cc=d@chaos-reins.com \
    --cc=djbyrne@mtu.edu \
    --cc=heftig@archlinux.org \
    --cc=holger@applied-asynchrony.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oleksandr@natalenko.name \
    --cc=sofia.trinh@edi.works \
    --cc=steev@kali.org \
    --cc=steven@liquorix.net \
    --cc=suleiman@google.com \
    --cc=szhai2@cs.rochester.edu \
    --cc=vaibhav@linux.ibm.com \
    --cc=yujie.liu@intel.com \
    /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