From: Laura Abbott <labbott@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Warning from AMD IOMMU performance counters
Date: Fri, 19 Feb 2016 14:35:36 -0800 [thread overview]
Message-ID: <56C798B8.6080009@redhat.com> (raw)
Hi,
Since about 4.4, we've been seeing reports of this warning on every boot
from some users:
WARNING: CPU: 2 PID: 1 at drivers/iommu/amd_iommu_init.c:2301 amd_iommu_pc_get_set_reg_val+0xa8/0xe0()
Modules linked in:
CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.2-300.fc23.x86_64 #1
Hardware name: Hewlett-Packard HP EliteBook 755 G2/221C, BIOS M84 Ver. 01.10 10/20/2015
0000000000000000 0000000026124b43 ffff88042d687d20 ffffffff813b0c9f
0000000000000000 ffff88042d687d58 ffffffff810a2f12 ffff88042f014800
0000000000000040 0000000000000000 ffffffff81d6c73d 0000000000000000
Call Trace:
[<ffffffff813b0c9f>] dump_stack+0x44/0x55
[<ffffffff810a2f12>] warn_slowpath_common+0x82/0xc0
[<ffffffff81d6c73d>] ? memblock_find_dma_reserve+0x16a/0x16a
[<ffffffff810a305a>] warn_slowpath_null+0x1a/0x20
[<ffffffff814d3f48>] amd_iommu_pc_get_set_reg_val+0xa8/0xe0
[<ffffffff81dafda7>] iommu_go_to_state+0x4d6/0x1384
[<ffffffff813c02ea>] ? kvasprintf+0x7a/0xa0
[<ffffffff81d6c73d>] ? memblock_find_dma_reserve+0x16a/0x16a
[<ffffffff81db0cbd>] amd_iommu_init+0x13/0x201
[<ffffffff81d6c74f>] pci_iommu_init+0x12/0x3c
[<ffffffff81002123>] do_one_initcall+0xb3/0x200
[<ffffffff810c0935>] ? parse_args+0x295/0x4b0
[<ffffffff81d621c8>] kernel_init_freeable+0x189/0x223
[<ffffffff8178dc00>] ? rest_init+0x80/0x80
[<ffffffff8178dc0e>] kernel_init+0xe/0xe0
[<ffffffff81799c8f>] ret_from_fork+0x3f/0x70
[<ffffffff8178dc00>] ? rest_init+0x80/0x80
Full bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1310258
Any idea what might be causing this spew?
Thanks,
Laura
next reply other threads:[~2016-02-19 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 22:35 Laura Abbott [this message]
[not found] ` <56C798B8.6080009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-22 1:52 ` Warning from AMD IOMMU performance counters Wan Zongshun
[not found] ` <56CA69C7.3050508-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-02-23 1:36 ` Laura Abbott
2016-02-23 17:26 ` Laura Abbott
[not found] ` <56CC963A.1080607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-23 17:51 ` Borislav Petkov
[not found] ` <20160223175113.GA3711-fF5Pk5pvG8Y@public.gmane.org>
2016-02-25 14:57 ` Joerg Roedel
[not found] ` <20160225145716.GA18581-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-25 17:47 ` Laura Abbott
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=56C798B8.6080009@redhat.com \
--to=labbott@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).