From: "Luís Mendes" <luis.p.mendes@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Linux PCI <linux-pci@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jason Cooper <jason@lakedaemon.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Problem with PCIe enumeration of Google/Coral TPU Edge module on Linux
Date: Thu, 2 Apr 2020 15:13:36 +0100 [thread overview]
Message-ID: <CAEzXK1qmYkpHzhbBmYG_Mvk+s6-NAJO-17+VW9fm-=trSZ-v5Q@mail.gmail.com> (raw)
In-Reply-To: <20200401233121.GA152016@google.com>
Hi Bjorn,
The command that worked was:
# sh -c "echo 1 >
/sys/bus/pci/devices/0000\:00\:01.0/pci_bus/0000\:01/bus_rescan"
The only new information compared to yesterday dmesg are the following lines:
...
[ 20.633566] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full
- flow control off
[ 20.633598] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1048.661591] FAT-fs (sda1): Volume was not properly unmounted. Some
data may be corrupt. Please run fsck.
[ 1049.792121] EXT4-fs (sdb1): mounted filesystem with ordered data
mode. Opts: (null)
[60026.321476] pci_bus 0000:01: __pci_bus_assign_resources
[60026.321481] pci_bus 0000:01: pbus_assign_resources_sorted
[60026.321485] pci 0000:01:00.0: __dev_sort_resources
[60026.321487] __assign_resources_sorted
[60026.321490] pci 0000:01:00.0: __pci_bus_assign_resources
[60026.321493] pci 0000:01:00.0: pdev_assign_fixed_resources
Luís
On Thu, Apr 2, 2020 at 12:31 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Wed, Apr 01, 2020 at 10:20:42PM +0100, Luís Mendes wrote:
> > Hi Bjorn,
> >
> > Here is the dmesg output with the new kernel patch:
> > https://paste.ubuntu.com/p/7cv7ZcyrnG/
>
> Thanks. What happens if you do this:
>
> # echo 1 > sys/devices/pci0000:00/0000:00:01.0/pci_bus/0000:01/rescan
>
> (I think on v5.6 that file is "bus_rescan" instead of "rescan".
> There's a patch queued up to change it.)
next prev parent reply other threads:[~2020-04-02 14:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 14:32 Problem with PCIe enumeration of Google/Coral TPU Edge module on Linux Luís Mendes
2020-03-06 21:47 ` Bjorn Helgaas
2020-03-07 12:11 ` Luís Mendes
2020-03-07 15:26 ` Luís Mendes
2020-03-07 21:38 ` Bjorn Helgaas
2020-03-08 5:51 ` Nicholas Johnson
2020-03-09 11:21 ` Luís Mendes
2020-03-11 14:20 ` Luís Mendes
2020-03-29 22:11 ` Luís Mendes
2020-03-30 19:49 ` Bjorn Helgaas
2020-03-31 21:28 ` Luís Mendes
2020-04-01 18:16 ` Bjorn Helgaas
2020-04-01 21:20 ` Luís Mendes
2020-04-01 21:55 ` Luís Mendes
2020-04-01 23:31 ` Bjorn Helgaas
2020-04-02 14:13 ` Luís Mendes [this message]
2020-04-04 1:32 ` Bjorn Helgaas
2020-04-04 21:39 ` Luís Mendes
2020-04-08 23:05 ` Luís Mendes
2020-04-09 15:25 ` Luís Mendes
2020-04-09 15:29 ` Luís Mendes
2020-04-09 16:30 ` Bjorn Helgaas
2020-04-09 17:32 ` Luís Mendes
2020-04-09 18:08 ` Bjorn Helgaas
2020-04-09 20:07 ` Luís Mendes
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='CAEzXK1qmYkpHzhbBmYG_Mvk+s6-NAJO-17+VW9fm-=trSZ-v5Q@mail.gmail.com' \
--to=luis.p.mendes@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-pci@vger.kernel.org \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=thomas.petazzoni@bootlin.com \
/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).