Bug 110919 - intel_device_info_init_mmio:925 GEM_BUG_ON(vebox_mask != …)
Summary: intel_device_info_init_mmio:925 GEM_BUG_ON(vebox_mask != …)
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-14 11:03 UTC by emersion
Modified: 2019-07-08 11:20 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features:


Attachments

Description emersion 2019-06-14 11:03:45 UTC
dmesg: https://sr.ht/W-DU.txt

[    9.620561] **********************************************************
[    9.620563] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    9.620564] **                                                      **
[    9.620566] ** trace_printk() being used. Allocating extra memory.  **
[    9.620567] **                                                      **
[    9.620568] ** This means that this is a DEBUG kernel and it is     **
[    9.620569] ** unsafe for production use.                           **
[    9.620571] **                                                      **
[    9.620572] ** If you see this message and you are not debugging    **
[    9.620573] ** the kernel, report this immediately to your vendor!  **
[    9.620575] **                                                      **
[    9.620577] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    9.620578] **********************************************************
[    9.646504] intel_device_info_init_mmio:925 GEM_BUG_ON(vebox_mask != ({ unsigned int first__ = (VECS0); unsigned int count__ = (2); ((&(dev_priv)->__info)->engine_mask & (((~0UL) - (1UL << (first__)) + 1) & (~0UL >> (64 - 1 - (first__ + count__ - 1))))) >> first__; }))
[    9.646580] ------------[ cut here ]------------
[    9.646582] kernel BUG at drivers/gpu/drm/i915/intel_device_info.c:925!
[    9.646603] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
[    9.646610] CPU: 5 PID: 374 Comm: modprobe Not tainted 5.1.0-rc2-g73462b05bd50-pstore+ #1
[    9.646619] Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS ICLSFWR1.R00.3212.A00.1905212112 05/21/2019
[    9.646697] RIP: 0010:intel_device_info_init_mmio+0x262/0x270 [i915]
[    9.646705] Code: dd fe c5 f1 48 8b 35 fd a5 24 00 49 c7 c0 f8 eb 64 c0 b9 9d 03 00 00 48 c7 c2 20 d1 62 c0 48 c7 c7 fd aa 4c c0 e8 ae a3 cc f1 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 66 90 55 53 48 8d af a8 0e 00
[    9.646721] RSP: 0018:ffffb1f140323a80 EFLAGS: 00010282
[    9.646727] RAX: 000000000000003e RBX: 00000000000000f1 RCX: 0000000000000000
[    9.646734] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffa2d5de1b5508
[    9.646741] RBP: ffffa2d5c1440000 R08: 0000000000000001 R09: ffffa2d5dd567000
[    9.646748] R10: 0000000000000000 R11: ffffa2d5de1b5508 R12: 0000000000000001
[    9.646755] R13: 00000000000000f1 R14: 0000000000000005 R15: 0000000000000005
[    9.646762] FS:  00007fafaa5ce540(0000) GS:ffffa2d5dff40000(0000) knlGS:0000000000000000
[    9.646771] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    9.646776] CR2: 00007f16cc57e158 CR3: 000000048bcf6004 CR4: 0000000000760ee0
[    9.646783] PKRU: 55555554
[    9.646787] Call Trace:
[    9.646834]  i915_driver_load+0x716/0x1790 [i915]
[    9.646848]  ? __pm_runtime_resume+0x4f/0x80
[    9.646856]  ? _raw_spin_unlock_irqrestore+0x4c/0x60
[    9.646862]  ? _raw_spin_unlock_irqrestore+0x4c/0x60
[    9.646869]  ? lockdep_hardirqs_on+0xe3/0x1b0
[    9.646911]  i915_pci_probe+0x29/0xa0 [i915]
[    9.646919]  pci_device_probe+0xa1/0x120
[    9.646925]  really_probe+0xf3/0x3e0
[    9.646930]  driver_probe_device+0x10a/0x120
[    9.646936]  device_driver_attach+0x4b/0x50
[    9.646941]  __driver_attach+0x97/0x130
[    9.646947]  ? device_driver_attach+0x50/0x50
[    9.646953]  bus_for_each_dev+0x74/0xc0
[    9.646959]  bus_add_driver+0x13f/0x210
[    9.646964]  ? 0xffffffffc07fe000
[    9.646969]  driver_register+0x56/0xe0
[    9.646974]  ? 0xffffffffc07fe000
[    9.646979]  do_one_initcall+0x58/0x2e0
[    9.646986]  ? do_init_module+0x1d/0x1ea
[    9.646993]  ? rcu_read_lock_sched_held+0x6f/0x80
[    9.646999]  ? kmem_cache_alloc_trace+0x261/0x290
[    9.647007]  do_init_module+0x56/0x1ea
[    9.647012]  load_module+0x2701/0x29e0
[    9.647023]  ? __se_sys_finit_module+0xd3/0xf0
[    9.647029]  __se_sys_finit_module+0xd3/0xf0
[    9.647037]  do_syscall_64+0x55/0x190
[    9.647043]  entry_SYSCALL_64_after_hwframe+0x49/0xbe
Comment 1 emersion 2019-06-14 11:06:38 UTC
(This happens on boot on re-icl-u. After this, `sudo aplay -L` doesn't show any HDMI/DP audio devices.)
Comment 2 Chris Wilson 2019-06-14 11:07:51 UTC
Please do confirm bugs on the current upstream drm-tip before reporting upstream.
Comment 3 Chris Wilson 2019-06-14 11:09:19 UTC
The dmesg also required drm.debug=0x2 to get the right information here.
Comment 4 Lakshmi 2019-06-28 11:43:23 UTC
Simon, can you attach the dmesg with drm.debug=0x2 parameter?
Comment 5 emersion 2019-07-08 11:20:01 UTC
Cannot reproduce anymore.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.