All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: linux-next: Tree for Feb 8 (Warning at arch/x86/kernel/irq.c:390)
Date: Mon, 8 Feb 2021 19:33:17 -0800	[thread overview]
Message-ID: <62fecf7b-e660-8bf6-c9d7-634c599494dd@infradead.org> (raw)
In-Reply-To: <20210208235246.01cb4daf@canb.auug.org.au>

On 2/8/21 4:52 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20210205:
> 

on x86_64:

Re: commit 1dba8a9538f5164eb8874eed4c7d6799a3c64963
Author: Borislav Petkov <bp@suse.de>
Date:   Thu Jan 7 13:29:05 2021 +0100
    thermal: Move therm_throt there from x86/mce

I am seeing this for CPU = 1,2,3:

[    0.002092] WARNING: CPU: 1 PID: 0 at ../arch/x86/kernel/irq.c:390 thermal_set_handler+0x16/0x35
[    0.002092] Modules linked in:
[    0.002092] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.11.0-rc6-next-20210208 #1
[    0.002092] Hardware name: TOSHIBA PORTEGE R835/Portable PC, BIOS Version 4.10   01/08/2013
[    0.002092] RIP: 0010:thermal_set_handler+0x16/0x35
[    0.002092] Code: 00 00 00 0f 85 e0 fe ff ff 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 85 ff 74 1c 48 81 3d f7 65 61 01 20 b4 41 b2 74 1b 55 48 89 e5 <0f> 0b 48 89 3d e8 65 61 01 5d c3 48 c7 05 db 65 61 01 20 b4 41 b2
[    0.002092] RSP: 0000:ffff9c5a00097e08 EFLAGS: 00010002
[    0.002092] RAX: 0000000000000007 RBX: 0000000000000007 RCX: 00000000000001b2
[    0.002092] RDX: 0000000000000000 RSI: 0000000000000007 RDI: ffffffffb2a6c9d3
[    0.002092] RBP: ffff9c5a00097e08 R08: ffff94c88ba51460 R09: 000000000003007f
[    0.002092] R10: ffff94c88ba51480 R11: 0000000000000000 R12: 0000000000000000
[    0.002092] R13: ffff94c88ba51480 R14: 0000000000000000 R15: 0000000000000000
[    0.002092] FS:  0000000000000000(0000) GS:ffff94c88ba40000(0000) knlGS:0000000000000000
[    0.002092] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.002092] CR2: 0000000000000000 CR3: 0000000093c0a001 CR4: 00000000000606a0
[    0.002092] Call Trace:
[    0.002092]  intel_init_thermal+0x25a/0x2e9
[    0.002092]  init_intel+0x562/0x585
[    0.002092]  identify_cpu+0x298/0x4b0
[    0.002092]  identify_secondary_cpu+0x1a/0x99
[    0.002092]  smp_store_cpu_info+0x5d/0x6b
[    0.002092]  start_secondary+0x5f/0x16c
[    0.002092]  secondary_startup_64_no_verify+0xc2/0xcb
[    0.002092] ---[ end trace 9f8e2ebc792bd614 ]---


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

  parent reply	other threads:[~2021-02-09  4:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 12:52 linux-next: Tree for Feb 8 Stephen Rothwell
2021-02-08 19:30 ` linux-next: Tree for Feb 8 (objtool: warnings: 5) Randy Dunlap
2021-02-08 21:21   ` Josh Poimboeuf
2021-02-08 21:39     ` Randy Dunlap
2021-02-09 22:59       ` Josh Poimboeuf
2021-02-10  0:16         ` Randy Dunlap
2021-02-09  8:06     ` Peter Zijlstra
2021-02-09 23:23       ` [PATCH] ubsan: remove overflow checks Andrey Ryabinin
2021-02-10  0:19         ` Kees Cook
2021-02-10  7:50           ` Peter Zijlstra
2021-02-10 11:55           ` Andrey Rybainin
2021-02-09  8:34   ` [PATCH] lockdep: Noinstr annotate warn_bogus_irq_restore() Peter Zijlstra
2021-02-09 13:24     ` Mark Rutland
2021-02-09 16:03       ` Peter Zijlstra
2021-02-09 16:13         ` Mark Rutland
2021-02-09 18:28         ` Randy Dunlap
2021-02-10 13:59         ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2021-02-09  3:33 ` Randy Dunlap [this message]
2021-02-09 10:17   ` linux-next: Tree for Feb 8 (Warning at arch/x86/kernel/irq.c:390) Borislav Petkov

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=62fecf7b-e660-8bf6-c9d7-634c599494dd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.