From: kernel test robot <oliver.sang@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<intel-gfx@lists.freedesktop.org>, <rui.zhang@intel.com>,
<yu.c.chen@intel.com>, <jani.nikula@linux.intel.com>,
<joonas.lahtinen@linux.intel.com>, <rodrigo.vivi@intel.com>,
<matthew.d.roper@intel.com>, <andi.shyti@linux.intel.com>,
<anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<riana.tauro@intel.com>, Raag Jadav <raag.jadav@intel.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH v1] drm/i915/dg2: enable G8 with a workaround
Date: Mon, 14 Oct 2024 14:30:55 +0800 [thread overview]
Message-ID: <202410141449.699cfd23-oliver.sang@intel.com> (raw)
In-Reply-To: <20241007122424.642796-1-raag.jadav@intel.com>
Hello,
kernel test robot noticed "UBSAN:array-index-out-of-bounds_in_drivers/gpu/drm/i915/i915_drv.h" on:
commit: 3d845c2240623759952e06027546304b127ec1c5 ("[PATCH v1] drm/i915/dg2: enable G8 with a workaround")
url: https://github.com/intel-lab-lkp/linux/commits/Raag-Jadav/drm-i915-dg2-enable-G8-with-a-workaround/20241007-202716
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link: https://lore.kernel.org/all/20241007122424.642796-1-raag.jadav@intel.com/
patch subject: [PATCH v1] drm/i915/dg2: enable G8 with a workaround
in testcase: suspend-stress
version:
with following parameters:
mode: freeze
iterations: 10
config: x86_64-rhel-8.3-func
compiler: gcc-12
test machine: 4 threads (Broadwell) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202410141449.699cfd23-oliver.sang@intel.com
kern :warn : [ 28.439916] ------------[ cut here ]------------
kern :err : [ 28.440035] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/i915/i915_drv.h:466:28
kern :err : [ 28.440211] index 58 is out of range for type 'u32 [2]'
kern :warn : [ 28.440322] CPU: 1 UID: 0 PID: 202 Comm: systemd-udevd Not tainted 6.12.0-rc1-00198-g3d845c224062 #1
kern :warn : [ 28.440489] Hardware name: /NUC5i3RYB, BIOS RYBDWi35.86A.0363.2017.0316.1028 03/16/2017
kern :warn : [ 28.440636] Call Trace:
kern :warn : [ 28.440703] <TASK>
kern :warn : [ 28.440764] dump_stack_lvl (lib/dump_stack.c:123 (discriminator 1))
kern :warn : [ 28.440862] __ubsan_handle_out_of_bounds (lib/ubsan.c:232 lib/ubsan.c:429)
kern :warn : [ 28.440977] gt_init_workarounds (drivers/gpu/drm/i915/i915_drv.h:466 drivers/gpu/drm/i915/gt/intel_workarounds.c:1689) i915
kern :warn : [ 28.441968] ? __pfx_gt_init_workarounds (drivers/gpu/drm/i915/gt/intel_workarounds.c:1665) i915
kern :warn : [ 28.442781] ? fwtable_write32 (drivers/gpu/drm/i915/intel_uncore.c:2012 (discriminator 11)) i915
kern :warn : [ 28.443526] intel_gt_init_workarounds (drivers/gpu/drm/i915/gt/intel_workarounds.c:1725) i915
kern :warn : [ 28.444297] intel_gt_init (drivers/gpu/drm/i915/gt/intel_gt.c:715) i915
kern :warn : [ 28.445032] i915_gem_init (drivers/gpu/drm/i915/i915_gem.c:1191) i915
kern :warn : [ 28.445793] i915_driver_probe (drivers/gpu/drm/i915/i915_driver.c:799) i915
kern :warn : [ 28.446517] ? __pfx_i915_driver_probe (drivers/gpu/drm/i915/i915_driver.c:751) i915
kern :warn : [ 28.447243] ? drm_privacy_screen_get (drivers/gpu/drm/drm_privacy_screen.c:168) drm
kern :warn : [ 28.447499] ? intel_display_driver_probe_defer (drivers/gpu/drm/i915/display/intel_display_driver.c:81) i915
kern :warn : [ 28.448300] ? i915_pci_probe (drivers/gpu/drm/i915/i915_pci.c:996) i915
kern :warn : [ 28.449003] ? __pfx_i915_pci_probe (drivers/gpu/drm/i915/i915_pci.c:957) i915
kern :warn : [ 28.449712] local_pci_probe (drivers/pci/pci-driver.c:324)
kern :warn : [ 28.449811] pci_call_probe (drivers/pci/pci-driver.c:392)
kern :warn : [ 28.449905] ? _raw_spin_lock (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:134 kernel/locking/spinlock.c:154)
kern :warn : [ 28.449998] ? __pfx_pci_call_probe (drivers/pci/pci-driver.c:352)
kern :warn : [ 28.450095] ? kernfs_add_one (fs/kernfs/dir.c:819)
kern :warn : [ 28.450190] ? pci_assign_irq (drivers/pci/irq.c:149)
kern :warn : [ 28.450282] ? pci_match_device (drivers/pci/pci-driver.c:159 (discriminator 1))
kern :warn : [ 28.450379] ? kernfs_put (arch/x86/include/asm/atomic.h:67 (discriminator 1) include/linux/atomic/atomic-arch-fallback.h:2278 (discriminator 1) include/linux/atomic/atomic-instrumented.h:1384 (discriminator 1) fs/kernfs/dir.c:557 (discriminator 1))
kern :warn : [ 28.450465] pci_device_probe (drivers/pci/pci-driver.c:452)
kern :warn : [ 28.450557] ? pci_dma_configure (drivers/pci/pci-driver.c:1656)
kern :warn : [ 28.450653] really_probe (drivers/base/dd.c:579 drivers/base/dd.c:658)
kern :warn : [ 28.450741] __driver_probe_device (drivers/base/dd.c:738 drivers/base/dd.c:798)
kern :warn : [ 28.450841] driver_probe_device (drivers/base/dd.c:830)
kern :warn : [ 28.450937] __driver_attach (drivers/base/dd.c:1217)
kern :warn : [ 28.451028] ? __pfx___driver_attach (drivers/base/dd.c:1157)
kern :warn : [ 28.451124] bus_for_each_dev (drivers/base/bus.c:369)
kern :warn : [ 28.451217] ? __pfx_bus_for_each_dev (drivers/base/bus.c:358)
kern :warn : [ 28.451318] ? klist_add_tail (include/linux/list.h:150 include/linux/list.h:183 lib/klist.c:104 lib/klist.c:137)
kern :warn : [ 28.451410] bus_add_driver (drivers/base/bus.c:675)
kern :warn : [ 28.451500] driver_register (drivers/base/driver.c:246)
kern :warn : [ 28.451594] i915_init (drivers/gpu/drm/i915/i915_driver.c:1395) i915
kern :warn : [ 28.452466] ? __pfx_i915_init (drivers/gpu/drm/i915/i915_config.c:13) i915
kern :warn : [ 28.453207] do_one_initcall (init/main.c:1269)
kern :warn : [ 28.453304] ? __pfx_do_one_initcall (init/main.c:1260)
kern :warn : [ 28.453408] ? kasan_unpoison (mm/kasan/shadow.c:157 mm/kasan/shadow.c:151 mm/kasan/shadow.c:182)
kern :warn : [ 28.453499] ? kasan_unpoison (mm/kasan/shadow.c:156 mm/kasan/shadow.c:182)
kern :warn : [ 28.453592] do_init_module (kernel/module/main.c:2543)
kern :warn : [ 28.453687] init_module_from_file (kernel/module/main.c:3198)
kern :warn : [ 28.453787] ? __pfx_init_module_from_file (kernel/module/main.c:3174)
kern :warn : [ 28.453895] ? __pfx_userfaultfd_unmap_complete (fs/userfaultfd.c:810)
kern :warn : [ 28.454012] ? __pfx__raw_spin_lock (kernel/locking/spinlock.c:153)
kern :warn : [ 28.454112] idempotent_init_module (kernel/module/main.c:3210)
kern :warn : [ 28.454214] ? __pfx_idempotent_init_module (kernel/module/main.c:3202)
kern :warn : [ 28.454321] ? __pfx___seccomp_filter (kernel/seccomp.c:1218)
kern :warn : [ 28.454424] ? fdget (include/linux/atomic/atomic-arch-fallback.h:479 include/linux/atomic/atomic-instrumented.h:50 fs/file.c:1141 fs/file.c:1155)
kern :warn : [ 28.454504] ? security_capable (security/security.c:1142)
kern :warn : [ 28.454599] __x64_sys_finit_module (include/linux/file.h:68 kernel/module/main.c:3238 kernel/module/main.c:3220 kernel/module/main.c:3220)
kern :warn : [ 28.454698] do_syscall_64 (arch/x86/entry/common.c:52 arch/x86/entry/common.c:83)
kern :warn : [ 28.454790] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
kern :warn : [ 28.454900] RIP: 0033:0x7efbffb92229
kern :warn : [ 28.454984] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3f 4c 2b 00 f7 d8 64 89 01 48
All code
========
0: 00 f3 add %dh,%bl
2: c3 retq
3: 66 2e 0f 1f 84 00 00 nopw %cs:0x0(%rax,%rax,1)
a: 00 00 00
d: 0f 1f 40 00 nopl 0x0(%rax)
11: 48 89 f8 mov %rdi,%rax
14: 48 89 f7 mov %rsi,%rdi
17: 48 89 d6 mov %rdx,%rsi
1a: 48 89 ca mov %rcx,%rdx
1d: 4d 89 c2 mov %r8,%r10
20: 4d 89 c8 mov %r9,%r8
23: 4c 8b 4c 24 08 mov 0x8(%rsp),%r9
28: 0f 05 syscall
2a:* 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax <-- trapping instruction
30: 73 01 jae 0x33
32: c3 retq
33: 48 8b 0d 3f 4c 2b 00 mov 0x2b4c3f(%rip),%rcx # 0x2b4c79
3a: f7 d8 neg %eax
3c: 64 89 01 mov %eax,%fs:(%rcx)
3f: 48 rex.W
Code starting with the faulting instruction
===========================================
0: 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax
6: 73 01 jae 0x9
8: c3 retq
9: 48 8b 0d 3f 4c 2b 00 mov 0x2b4c3f(%rip),%rcx # 0x2b4c4f
10: f7 d8 neg %eax
12: 64 89 01 mov %eax,%fs:(%rcx)
15: 48 rex.W
kern :warn : [ 28.455283] RSP: 002b:00007ffe0d7f9428 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern :warn : [ 28.455429] RAX: ffffffffffffffda RBX: 000055b5a7168b10 RCX: 00007efbffb92229
kern :warn : [ 28.455562] RDX: 0000000000000000 RSI: 00007efc004ab265 RDI: 0000000000000014
kern :warn : [ 28.455695] RBP: 00007efc004ab265 R08: 0000000000000000 R09: 00007ffe0d7f99a0
kern :warn : [ 28.455826] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000
kern :warn : [ 28.455959] R13: 000055b5a7170fe0 R14: 0000000000020000 R15: 000055b575213cbc
kern :warn : [ 28.456095] </TASK>
kern :warn : [ 28.456422] ---[ end trace ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241014/202410141449.699cfd23-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-14 6:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 12:24 [PATCH v1] drm/i915/dg2: enable G8 with a workaround Raag Jadav
2024-10-07 13:05 ` Nilawar, Badal
2024-10-07 13:17 ` Nilawar, Badal
2024-10-08 3:43 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-10-08 3:53 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-08 17:24 ` [PATCH v1] " Jani Nikula
2024-10-09 12:47 ` Raag Jadav
2024-10-09 13:05 ` Jani Nikula
2024-10-09 16:42 ` Raag Jadav
2024-10-09 16:50 ` Jani Nikula
2024-10-09 19:05 ` Matt Roper
2024-10-14 4:31 ` Gupta, Anshuman
2024-10-15 8:37 ` Raag Jadav
2024-10-14 6:30 ` kernel test robot [this message]
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=202410141449.699cfd23-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lkp@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.