From: Joerg Roedel <joerg.roedel@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Antonio Quartulli <ordex@autistici.org>,
linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0
Date: Tue, 29 May 2012 10:35:53 +0200 [thread overview]
Message-ID: <20120529083552.GN2604@amd.com> (raw)
In-Reply-To: <CAErSpo553_-AivRa7VbjHrFraHaO4NYoYR7A9Am5fkDP-CMvSA@mail.gmail.com>
Hi Antonio,
On Sat, May 26, 2012 at 09:09:52AM -0600, Bjorn Helgaas wrote:
> On Sat, May 26, 2012 at 2:25 AM, Antonio Quartulli <ordex@autistici.org> wrote:
> > [ 1.054279] WARNING: at drivers/pci/search.c:44 pci_find_upstream_pcie_bridge+0x5e/0x70()
> > [ 1.054385] Hardware name: Latitude E5420
> > [ 1.054457] Modules linked in:
> > [ 1.054568] Pid: 1, comm: swapper/0 Not tainted 3.4.0ordex+ #3
> > [ 1.054643] Call Trace:
> > [ 1.054716] [<ffffffff81033d4a>] warn_slowpath_common+0x7a/0xb0
> > [ 1.054793] [<ffffffff81033d95>] warn_slowpath_null+0x15/0x20
> > [ 1.054869] [<ffffffff8123899e>] pci_find_upstream_pcie_bridge+0x5e/0x70
> > [ 1.054949] [<ffffffff813babe7>] intel_iommu_device_group+0x77/0x100
> > [ 1.055027] [<ffffffff813b52d5>] add_iommu_group+0x35/0x60
> > [ 1.055113] [<ffffffff813b52a0>] ? bus_set_iommu+0x50/0x50
> > [ 1.055191] [<ffffffff8132c586>] bus_for_each_dev+0x56/0x90
> > [ 1.055267] [<ffffffff813b528b>] bus_set_iommu+0x3b/0x50
> > [ 1.055344] [<ffffffff818c4920>] intel_iommu_init+0xab0/0xb3f
> > [ 1.055421] [<ffffffff81120b26>] ? sys_mkdirat+0x76/0xd0
> > [ 1.055499] [<ffffffff8189b0db>] ? memblock_find_dma_reserve+0x13d/0x13d
> > [ 1.055578] [<ffffffff8189b0ee>] pci_iommu_init+0x13/0x3e
> > [ 1.055655] [<ffffffff810001ca>] do_one_initcall+0x3a/0x170
> > [ 1.055732] [<ffffffff81897c35>] kernel_init+0x148/0x1cc
> > [ 1.055807] [<ffffffff81897588>] ? do_early_param+0x86/0x86
> > [ 1.055884] [<ffffffff814fc914>] kernel_thread_helper+0x4/0x10
> > [ 1.055963] [<ffffffff8105de60>] ? finish_task_switch+0x80/0x110
> > [ 1.056040] [<ffffffff814fafdd>] ? retint_restore_args+0xe/0xe
> > [ 1.056126] [<ffffffff81897aed>] ? start_kernel+0x30b/0x30b
> > [ 1.056203] [<ffffffff814fc910>] ? gs_change+0xb/0xb
Hmm, this looks like pci_find_upstream_pcie_bridge() found a PCIe device
in the chain which is not a bridge. Can you please post the output of
'lspci -vvv' and 'lspci -t'?
Thanks,
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joerg.roedel@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Antonio Quartulli <ordex@autistici.org>,
<linux-pci@vger.kernel.org>, <iommu@lists.linux-foundation.org>
Subject: Re: warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0
Date: Tue, 29 May 2012 10:35:53 +0200 [thread overview]
Message-ID: <20120529083552.GN2604@amd.com> (raw)
In-Reply-To: <CAErSpo553_-AivRa7VbjHrFraHaO4NYoYR7A9Am5fkDP-CMvSA@mail.gmail.com>
Hi Antonio,
On Sat, May 26, 2012 at 09:09:52AM -0600, Bjorn Helgaas wrote:
> On Sat, May 26, 2012 at 2:25 AM, Antonio Quartulli <ordex@autistici.org> wrote:
> > [ 1.054279] WARNING: at drivers/pci/search.c:44 pci_find_upstream_pcie_bridge+0x5e/0x70()
> > [ 1.054385] Hardware name: Latitude E5420
> > [ 1.054457] Modules linked in:
> > [ 1.054568] Pid: 1, comm: swapper/0 Not tainted 3.4.0ordex+ #3
> > [ 1.054643] Call Trace:
> > [ 1.054716] [<ffffffff81033d4a>] warn_slowpath_common+0x7a/0xb0
> > [ 1.054793] [<ffffffff81033d95>] warn_slowpath_null+0x15/0x20
> > [ 1.054869] [<ffffffff8123899e>] pci_find_upstream_pcie_bridge+0x5e/0x70
> > [ 1.054949] [<ffffffff813babe7>] intel_iommu_device_group+0x77/0x100
> > [ 1.055027] [<ffffffff813b52d5>] add_iommu_group+0x35/0x60
> > [ 1.055113] [<ffffffff813b52a0>] ? bus_set_iommu+0x50/0x50
> > [ 1.055191] [<ffffffff8132c586>] bus_for_each_dev+0x56/0x90
> > [ 1.055267] [<ffffffff813b528b>] bus_set_iommu+0x3b/0x50
> > [ 1.055344] [<ffffffff818c4920>] intel_iommu_init+0xab0/0xb3f
> > [ 1.055421] [<ffffffff81120b26>] ? sys_mkdirat+0x76/0xd0
> > [ 1.055499] [<ffffffff8189b0db>] ? memblock_find_dma_reserve+0x13d/0x13d
> > [ 1.055578] [<ffffffff8189b0ee>] pci_iommu_init+0x13/0x3e
> > [ 1.055655] [<ffffffff810001ca>] do_one_initcall+0x3a/0x170
> > [ 1.055732] [<ffffffff81897c35>] kernel_init+0x148/0x1cc
> > [ 1.055807] [<ffffffff81897588>] ? do_early_param+0x86/0x86
> > [ 1.055884] [<ffffffff814fc914>] kernel_thread_helper+0x4/0x10
> > [ 1.055963] [<ffffffff8105de60>] ? finish_task_switch+0x80/0x110
> > [ 1.056040] [<ffffffff814fafdd>] ? retint_restore_args+0xe/0xe
> > [ 1.056126] [<ffffffff81897aed>] ? start_kernel+0x30b/0x30b
> > [ 1.056203] [<ffffffff814fc910>] ? gs_change+0xb/0xb
Hmm, this looks like pci_find_upstream_pcie_bridge() found a PCIe device
in the chain which is not a bridge. Can you please post the output of
'lspci -vvv' and 'lspci -t'?
Thanks,
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-05-29 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 8:25 warn_slowpath_common in drivers/pci/search.c:44 on linux-3.4.0 Antonio Quartulli
2012-05-26 15:09 ` Bjorn Helgaas
2012-05-29 8:35 ` Joerg Roedel [this message]
2012-05-29 8:35 ` Joerg Roedel
2012-05-29 8:56 ` Antonio Quartulli
2012-05-29 10:16 ` Joerg Roedel
2012-05-29 10:16 ` Joerg Roedel
2012-05-29 16:13 ` Jiang Liu
2013-03-24 14:34 ` Antonio Quartulli
2013-12-08 14:26 ` Antonio Quartulli
[not found] ` <52A4819A.50501-x4xJYDvStAgysxA8WJXlww@public.gmane.org>
2013-12-09 17:25 ` Bjorn Helgaas
2013-12-09 17:25 ` Bjorn Helgaas
2013-12-09 17:36 ` Alex Williamson
2013-12-09 17:36 ` Alex Williamson
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=20120529083552.GN2604@amd.com \
--to=joerg.roedel@amd.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-pci@vger.kernel.org \
--cc=ordex@autistici.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 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.