Bug 110289 - H170 and Coffee Lake - WARN_ON(!((dev_priv)->info.platform_mask & (1UL << (INTEL_SKYLAKE))) && !((dev_priv)->info.platform_mask & (1UL << (INTEL_KABYLAKE))))
Summary: H170 and Coffee Lake - WARN_ON(!((dev_priv)->info.platform_mask & (1UL << (IN...
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-30 09:59 UTC by Alex
Modified: 2019-06-25 15:34 UTC (History)
2 users (show)

See Also:
i915 platform: CFL
i915 features: display/Other


Attachments
dmesg with drm.debug=0x1e log_buf_len=4M (116.48 KB, text/plain)
2019-03-30 09:59 UTC, Alex
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2019-03-30 09:59:08 UTC
Created attachment 143816 [details]
dmesg with drm.debug=0x1e log_buf_len=4M

Hi

I tried to use not-standart configuration:
Hardware GIGABYTE GA-H170-HD3 DDR3 and i5-8400

and with many of kernel versions(4.18, 4.19, 4.20, 5.0, 5.1rc2) one error.


# cat /sys/class/drm/card0/error
No error state collected

[    1.613019] [drm:intel_pch_type [i915]] Found SunrisePoint PCH
[    1.613019] ------------[ cut here ]------------
[    1.613019] WARN_ON(!((dev_priv)->info.platform_mask & (1UL << (INTEL_SKYLAKE))) && !((dev_priv)->info.platform_mask & (1UL << (INTEL_KABYLAKE))))
[    1.613052] WARNING: CPU: 5 PID: 344 at drivers/gpu/drm/i915/i915_drv.c:170 intel_pch_type+0x541/0x5b0 [i915]
[    1.613052] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm mpt3sas(+) crc32c_intel raid_class scsi_transport_sas wmi video kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass
[    1.613057] CPU: 5 PID: 344 Comm: systemd-udevd Tainted: G     U            5.0.5-200.fc29.x86_64 #1
[    1.613058] Hardware name: Gigabyte Technology Co., Ltd. H170-HD3 DDR3/H170-HD3 DDR3-CF, BIOS F21e 03/09/2018
[    1.613077] RIP: 0010:intel_pch_type+0x541/0x5b0 [i915]
[    1.613078] Code: f8 e2 6b c0 48 c7 c7 7f 02 6b c0 e8 63 17 b6 ec 0f 0b e9 4e fd ff ff 48 c7 c6 a0 e1 6b c0 48 c7 c7 7f 02 6b c0 e8 49 17 b6 ec <0f> 0b e9 4f fc ff ff 48 c7 c6 78 de 6b c0 48 c7 c7 7f 02 6b c0 e8
[    1.613079] RSP: 0018:ffffb5a0038aba90 EFLAGS: 00010286
[    1.613079] RAX: 0000000000000000 RBX: ffff890954e00000 RCX: 0000000000000000
[    1.613080] RDX: 0000000000000086 RSI: ffffffffaeba96a6 RDI: 0000000000000246
[    1.613080] RBP: ffff89095f108000 R08: 0000000000000002 R09: 0000000000020880
[    1.613080] R10: 00004d70e2fd0406 R11: 0000000000000001 R12: 0000000000000000
[    1.613081] R13: ffff89095b1ce000 R14: 000000000000a144 R15: 000000000000a100
[    1.613082] FS:  00007fe702d83940(0000) GS:ffff89095f740000(0000) knlGS:0000000000000000
[    1.613082] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.613082] CR2: 000055ea6e3f2000 CR3: 000000081624a004 CR4: 00000000003606e0
[    1.613083] Call Trace:
[    1.613104]  i915_driver_load+0x28a/0xe60 [i915]
[    1.613107]  ? _cond_resched+0x15/0x30
[    1.613108]  ? kmem_cache_alloc_trace+0x154/0x1d0
[    1.613109]  ? _cond_resched+0x15/0x30
[    1.613110]  ? mutex_lock+0xe/0x30
[    1.613112]  ? acpi_dev_found+0x5f/0x70
[    1.613113]  local_pci_probe+0x41/0x90
[    1.613115]  pci_device_probe+0x118/0x1a0
[    1.613117]  really_probe+0xf8/0x3b0
[    1.613118]  driver_probe_device+0xb3/0xf0
[    1.613119]  __driver_attach+0xdd/0x110
[    1.613120]  ? driver_probe_device+0xf0/0xf0
[    1.613120]  bus_for_each_dev+0x77/0xc0
[    1.613122]  ? klist_add_tail+0x3b/0x60
[    1.613123]  bus_add_driver+0x152/0x230
[    1.613124]  ? 0xffffffffc078e000
[    1.613125]  driver_register+0x6b/0xb0
[    1.613125]  ? 0xffffffffc078e000
[    1.613127]  do_one_initcall+0x46/0x1c3
[    1.613128]  ? _cond_resched+0x15/0x30
[    1.613129]  ? kmem_cache_alloc_trace+0x154/0x1d0
[    1.613131]  do_init_module+0x5a/0x210
[    1.613132]  load_module+0x2096/0x22d0
[    1.613134]  ? __do_sys_init_module+0x13b/0x180
[    1.613135]  __do_sys_init_module+0x13b/0x180
[    1.613137]  do_syscall_64+0x5b/0x160
[    1.613138]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    1.613139] RIP: 0033:0x7fe703a4c0ee
[    1.613139] Code: 48 8b 0d 9d 1d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 1d 0c 00 f7 d8 64 89 01 48
[    1.613140] RSP: 002b:00007fff0e2a55d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    1.613141] RAX: ffffffffffffffda RBX: 000055ea6d759ef0 RCX: 00007fe703a4c0ee
[    1.613141] RDX: 000055ea6d7499f0 RSI: 0000000000413a8e RDI: 000055ea6dfdf6f0
[    1.613141] RBP: 000055ea6d7499f0 R08: 000055ea6d75d970 R09: 0000000000000006
[    1.613142] R10: 0000000000000007 R11: 0000000000000246 R12: 000055ea6dfdf6f0
[    1.613142] R13: 000055ea6d7543d0 R14: 0000000000020000 R15: 0000000000000000
[    1.613143] ---[ end trace 28cc9eccaeef644d ]---
Comment 1 Lakshmi 2019-04-01 09:42:32 UTC
Alex, is there any impact due to this warning?
Have you noticed any particular pattern that is causing the warning?
Comment 2 Alex 2019-04-02 09:01:15 UTC
I think this error does not affect.
If an integrated video system is enabled in the BIOS, system is very unstable - kernel panic can happen at any time. I tried changing the code to be detected as [drm: intel_pch_type [i915]] Found Cannon Lake PCH (CNP). But this did not work - constant kernel panic.
If iGPU is disabled, the system is stable
Comment 3 Lakshmi 2019-04-12 10:41:01 UTC
(In reply to Alex from comment #2)
> I think this error does not affect.
> If an integrated video system is enabled in the BIOS, system is very
> unstable - kernel panic can happen at any time. I tried changing the code to
> be detected as [drm: intel_pch_type [i915]] Found Cannon Lake PCH (CNP). But
> this did not work - constant kernel panic.
> If iGPU is disabled, the system is stable

So, the attached dmesg is when integrated video system is enabled in the BIOS?
Comment 4 Alex 2019-04-13 12:44:45 UTC
Of course, you see i915 in the log
Now I replaced the memory modules and system began to work stable. Kernel panic stayed.
Comment 5 Lakshmi 2019-05-02 13:02:41 UTC
Chris, any suggestion to this bug?
Comment 6 Chris Wilson 2019-05-02 13:06:58 UTC
The warning is just an unexpected combination of cpu + pch. There's no information regarding the kernel panic.
Comment 7 Lakshmi 2019-06-25 15:34:35 UTC
https://www.gigabyte.com/Motherboard/GA-H170-HD3-rev-10#support-cpu
GA-H170-HD3 motherboard doesn't support CPU model i5-8400.

Closing this bug as INVALID.


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.