From: Bjorn Helgaas <bjorn.helgaas@gmail.com>
To: Carlo Pisani <carlojpisani@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Subject: Re: Oxford Semiconductor Ltd OX16PCI954 - weird dmesg
Date: Mon, 28 Oct 2019 13:48:27 -0500 [thread overview]
Message-ID: <CABhMZUXADeHV+iUgFyDF+3BcQRFKDkMbwdkDAvBuYLd2XY=HCw@mail.gmail.com> (raw)
In-Reply-To: <CA+QBN9DZyFynoUt+7sS_AcC-Wio-McJKCz8-RYfDWV0jv8iCzw@mail.gmail.com>
On Mon, Oct 28, 2019 at 12:37 PM Carlo Pisani <carlojpisani@gmail.com> wrote:
>
> > > > These resources are supplied to the PCI core, probably from DT. A
> > > > complete dmesg log would show more.
>
> The rb532 does not have device tree support, so the answer is no.
> I am using a common vanilla kernel without any extra patch.
What's your .config file? The knowledge about the host bridge windows
must be compiled in somewhere.
> 00:02.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S
> [Rhine-III] (rev 86)
> Subsystem: AST Research Inc Device 086c
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping+ SERR- FastB2B- DisINTx-
> 00:05.0 Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad
> 16950 UART) function 0 (Uart) (rev 01) (prog-if 06 [16950])
> Subsystem: Oxford Semiconductor Ltd Device 0000
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> > If those UARTs are capable of DMA, it's conceivable they could corrupt
> something.
>
> yes, it looks like something corrupts the memory.
The UARTs do not have DMA enabled (BusMaster-) in the lspci output, so
they shouldn't be able to corrupt memory. The NICs *do* have DMA
enabled. Does the problem still happen if you turn off the NIC
drivers (via-rhine and ath9k, it looks like)?
next prev parent reply other threads:[~2019-10-28 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+QBN9C_o8HanAzXpDUN410g2o5+xfx64pbX3_VHVDKcj5N3kA@mail.gmail.com>
2019-10-28 17:13 ` Oxford Semiconductor Ltd OX16PCI954 - weird dmesg Bjorn Helgaas
2019-10-28 16:37 ` Carlo Pisani
2019-10-28 18:48 ` Bjorn Helgaas [this message]
2019-10-28 18:06 ` Carlo Pisani
2019-10-28 19:43 ` Bjorn Helgaas
2019-10-28 18:49 ` Carlo Pisani
2019-11-04 14:59 ` Bjorn Helgaas
2019-10-28 16:46 ` Carlo Pisani
[not found] <CA+QBN9D4bckEZmNhLJPBmr92St1W2GGyazLGR9kANFk2cfV8Pg@mail.gmail.com>
2019-11-04 16:30 ` Bjorn Helgaas
[not found] <CA+QBN9B4qfxpEa69TB=+MngG9bN0puwByAeGCMxk_Y7fgaKhpQ@mail.gmail.com>
2019-11-04 16:07 ` Bjorn Helgaas
[not found] <CA+QBN9AzXHifP4=F1O1jjbGP0yNxBZeTPgPJvpcKFb9Z4f30KA@mail.gmail.com>
2019-11-04 15:58 ` Bjorn Helgaas
2019-10-24 17:11 [PATCH v6 00/30] PCI: Allow BAR movement during hotplug Sergey Miroshnichenko
2019-10-24 17:11 ` [PATCH v6 01/30] PCI: Fix race condition in pci_enable/disable_device() Sergey Miroshnichenko
2019-10-25 14:33 ` Oxford Semiconductor Ltd OX16PCI954 - weird dmesg Carlo Pisani
2019-10-25 16:37 ` Bjorn Helgaas
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='CABhMZUXADeHV+iUgFyDF+3BcQRFKDkMbwdkDAvBuYLd2XY=HCw@mail.gmail.com' \
--to=bjorn.helgaas@gmail.com \
--cc=bjorn@helgaas.com \
--cc=carlojpisani@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@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).