public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>
Cc: SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>,
	WillDeacon <will@kernel.org>, JoergRoedel <joro@8bytes.org>,
	stable@vger.kernel.org
Subject: Re: Linux 5.17.5
Date: Sun, 1 May 2022 16:23:25 +0200	[thread overview]
Message-ID: <Ym6X3enhptEUyyJG@kroah.com> (raw)
In-Reply-To: <a5c7406e-64b0-7522-fef0-27fec1ac6698@web.de>

On Sun, May 01, 2022 at 02:37:36PM +0200, Jörg-Volker Peetz wrote:
> Greg Kroah-Hartman wrote on 27/04/2022 15:11:
> > I'm announcing the release of the 5.17.5 kernel.
> > 
> > All users of the 5.17 kernel series must upgrade.
> > 
> > The updated 5.17.y git tree can be found at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.17.y
> > and can be browsed at the normal kernel.org git web browser:
> > 	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > 
> > thanks,
> > 
> > greg k-h
> > 
> <snip>
> Hi,
> 
> while booting a self compiled kernel 5.17.5, the following warning appeared in
> the logs:
> 
> Apr 28 15:57:41 xxx kernel: WARNING: CPU: 0 PID: 1 at
> drivers/iommu/amd/init.c:851 amd_iommu_enable_interrupts+0x312/0x3f0
> Apr 28 15:57:41 xxx kernel: Modules linked in:
> Apr 28 15:57:41 xxx kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.5 #1
> Apr 28 15:57:41 xxx kernel: Hardware name: Micro-Star International Co., Ltd.
> MS-7C94/MAG B550M MORTAR (MS-7C94), BIOS 1.94 09/23/2021
> Apr 28 15:57:41 xxx kernel: RIP: 0010:amd_iommu_enable_interrupts+0x312/0x3f0
> Apr 28 15:57:41 xxx kernel: Code: ff ff 49 8b 7f 18 89 04 24 e8 2a ff f6 ff 8b
> 04 24 e9 7b fd ff ff 0f 0b 4d 8b 3f 49 81 ff 90 15 ac b0 0f 85 35 fd ff ff eb 82
> <0f> 0b 4d 8b 3f 49 81 ff 90 15 ac b0 0f 85 21 fd ff ff e9 6b ff ff
> Apr 28 15:57:41 xxx kernel: RSP: 0018:ffffaf47c005fdd8 EFLAGS: 00010246
> Apr 28 15:57:41 xxx kernel: RAX: 0000000f03059ee4 RBX: 0000000000000000 RCX:
> 0000000000000000
> Apr 28 15:57:41 xxx kernel: RDX: 0000000000009da4 RSI: 0000000000009428 RDI:
> 0000000f03050140
> Apr 28 15:57:41 xxx kernel: RBP: 0000000080000000 R08: ffffffffffffffff R09:
> 0000000000000000
> Apr 28 15:57:41 xxx kernel: R10: 00000000000000d1 R11: 0000000000000000 R12:
> 000ffffffffffff8
> Apr 28 15:57:41 xxx kernel: R13: 0800000000000000 R14: 0008000000000000 R15:
> ffff8f7380190000
> Apr 28 15:57:41 xxx kernel: FS:  0000000000000000(0000)
> GS:ffff8f8171c00000(0000) knlGS:0000000000000000
> Apr 28 15:57:41 xxx kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> Apr 28 15:57:41 xxx kernel: CR2: ffff8f81ae1ff000 CR3: 00000008a740a000 CR4:
> 0000000000750ef0
> Apr 28 15:57:41 xxx kernel: PKRU: 55555554
> Apr 28 15:57:41 xxx kernel: Call Trace:
> Apr 28 15:57:41 xxx kernel: <TASK>
> Apr 28 15:57:41 xxx kernel: iommu_go_to_state+0x10e0/0x138d
> Apr 28 15:57:41 xxx kernel: ? e820__memblock_setup+0x78/0x78
> Apr 28 15:57:41 xxx kernel: amd_iommu_init+0xa/0x20
> Apr 28 15:57:41 xxx kernel: pci_iommu_init+0x11/0x3a
> Apr 28 15:57:41 xxx kernel: do_one_initcall+0x47/0x180
> Apr 28 15:57:41 xxx kernel: kernel_init_freeable+0x162/0x1a7
> Apr 28 15:57:41 xxx kernel: ? rest_init+0xc0/0xc0
> Apr 28 15:57:41 xxx kernel: kernel_init+0x11/0x110
> Apr 28 15:57:41 xxx kernel: ret_from_fork+0x22/0x30
> Apr 28 15:57:41 xxx kernel: </TASK>
> 
> Is this serious?
> CPU is AMD Ryzen 7 5700G (RENOIR).
> The config file is attached.
> With kernel 5.17.3 this warning did not appear.

Can you use 'git bisect' to track down the offending change?

thanks,

greg k-h

  reply	other threads:[~2022-05-01 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 13:11 Linux 5.17.5 Greg Kroah-Hartman
2022-04-27 13:11 ` Greg Kroah-Hartman
2022-05-01 12:37 ` Jörg-Volker Peetz
2022-05-01 14:23   ` Greg KH [this message]
2022-05-02  9:23     ` JoergRoedel
2022-05-02  9:42   ` JoergRoedel
2022-05-02  9:45   ` JoergRoedel
2022-05-02 10:40     ` Jörg-Volker Peetz
2022-05-02 22:17     ` Jörg-Volker Peetz
2022-05-04  8:16       ` JoergRoedel
2022-05-04  9:51         ` Jörg-Volker Peetz
2022-05-04 13:21         ` Jörg-Volker Peetz
2022-05-20 10:30           ` Joerg Roedel
2022-05-20 10:48             ` Jörg-Volker Peetz
2022-05-20 11:14               ` Joerg Roedel
2022-05-20 16:21                 ` Jörg-Volker Peetz

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=Ym6X3enhptEUyyJG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=joro@8bytes.org \
    --cc=jvpeetz@web.de \
    --cc=stable@vger.kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=will@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox