Bug 111521 - [CI][SHARDS] igt@perf_pmu@cpu-hotplug - dmesg-warn - WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:1541 setup_local_APIC
Summary: [CI][SHARDS] igt@perf_pmu@cpu-hotplug - dmesg-warn - WARNING: CPU: 0 PID: 0 a...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-29 13:24 UTC by Martin Peres
Modified: 2019-11-29 19:25 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features:


Attachments

Description Martin Peres 2019-08-29 13:24:43 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6795/shard-skl1/igt@perf_pmu@cpu-hotplug.html

<4> [2238.710497] ------------[ cut here ]------------
<4> [2238.710534] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:1541 setup_local_APIC+0x258/0x3b0
<4> [2238.710541] Modules linked in: vgem snd_hda_codec_hdmi i915 snd_hda_intel snd_intel_nhlt snd_hda_codec x86_pkg_temp_thermal coretemp snd_hwdep crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel btusb btrtl btbcm btintel snd_pcm bluetooth cdc_ether usbnet r8152 mii ecdh_generic ecc i2c_hid pinctrl_sunrisepoint pinctrl_intel prime_numbers
<4> [2238.710626] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G     U            5.3.0-rc6-CI-CI_DRM_6795+ #1
<4> [2238.710634] Hardware name: Google Caroline/Caroline, BIOS MrChromebox 08/27/2018
<4> [2238.710646] RIP: 0010:setup_local_APIC+0x258/0x3b0
<4> [2238.710658] Code: 41 89 ce 48 c1 e2 20 49 c1 e6 0a 4c 03 34 24 48 09 d0 49 29 c6 4d 85 f6 0f 8f 73 fe ff ff 48 c7 c7 a0 ed 07 82 e8 41 b3 0e 00 <0f> 0b e9 15 ff ff ff 49 83 ee 01 eb de a9 00 00 01 00 8b 15 24 60
<4> [2238.710667] RSP: 0018:ffffffff82203ee0 EFLAGS: 00010082
<4> [2238.710677] RAX: 0000000000000024 RBX: 0000000000000020 RCX: 0000000000000002
<4> [2238.710686] RDX: 0000000000000000 RSI: ffff88817aa266f8 RDI: 00000000ffffffff
<4> [2238.710692] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
<4> [2238.710700] R10: ffffffff82203f38 R11: 0000000000000000 R12: 00000000000000f0
<4> [2238.710707] R13: 0000000000400000 R14: ffffffffffffe612 R15: 0000000000000000
<4> [2238.710717] FS:  0000000000000000(0000) GS:ffff88817aa00000(0000) knlGS:0000000000000000
<4> [2238.710725] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [2238.710733] CR2: 00007f46420a58c0 CR3: 0000000006210001 CR4: 00000000003606f0
<4> [2238.710739] Call Trace:
<4> [2238.710772]  apic_ap_setup+0x5/0x20
<4> [2238.710783]  start_secondary+0x58/0x1b0
<4> [2238.710801]  secondary_startup_64+0xa4/0xb0
<4> [2238.710844] irq event stamp: 19069092
<4> [2238.710859] hardirqs last  enabled at (19069091): [<ffffffff81058bff>] switch_mm+0x2f/0x50
<4> [2238.710869] hardirqs last disabled at (19069092): [<ffffffff81041564>] native_play_dead+0x14/0x100
<4> [2238.710881] softirqs last  enabled at (19069066): [<ffffffff810b8168>] irq_enter+0x58/0x60
<4> [2238.710890] softirqs last disabled at (19069065): [<ffffffff810b814d>] irq_enter+0x3d/0x60
<4> [2238.710902] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:1541 setup_local_APIC+0x258/0x3b0
<4> [2238.710909] ---[ end trace 5ca19a1c47fb8a1a ]---
Comment 1 CI Bug Log 2019-08-29 13:26:43 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@perf_pmu@cpu-hotplug - dmesg-warn - WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:1541 setup_local_APIC
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6795/shard-skl1/igt@perf_pmu@cpu-hotplug.html
Comment 2 Chris Wilson 2019-08-29 18:55:24 UTC
Fwiw, the oops is

        /*
         * Double-check whether this APIC is really registered.
         * This is meaningless in clustered apic mode, so we skip it.
         */
        BUG_ON(!apic->apic_id_registered());

This needs to be forwarded onto

Thomas Gleixner <tglx@linutronix.de> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT),commit_signer:8/11=73%,authored:4/11=36%,added_lines:53/106=50%,removed_lines:15/54=28%)
Ingo Molnar <mingo@redhat.com> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT),commit_signer:2/11=18%)
Borislav Petkov <bp@alien8.de> (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT),commit_signer:3/11=27%)
"H. Peter Anvin" <hpa@zytor.com> (reviewer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT))
Comment 3 ashutosh.dixit 2019-11-12 19:19:54 UTC
#assessment

As Chris mentioned, should be a kernel bug, not a FDO bug. Also has happened only once. There are other failures associated with this test here:

https://intel-gfx-ci.01.org/tree/drm-tip/igt@perf_pmu@cpu-hotplug.html

But this failure is not one of them. It happened once in 10 runs, at present we see once in 39 runs. Should wait for once in 100 runs before resolving. Reducing priority to medium and wait till we see results for 100 runs.
Comment 4 Martin Peres 2019-11-29 19:25:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/388.


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.