From: "Pali Rohár" <pali@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: mvebu: Mark driver as BROKEN
Date: Tue, 8 Aug 2023 09:56:23 +0200 [thread overview]
Message-ID: <20230808075623.lmhvotnzzjsz5r2o@pali> (raw)
In-Reply-To: <20230808073822.35vlao5bs6bo2b2n@pengutronix.de>
On Tuesday 08 August 2023 09:38:22 Uwe Kleine-König wrote:
> Hello Pali,
>
> On Tue, Aug 08, 2023 at 09:27:01AM +0200, Pali Rohár wrote:
> > On Friday 04 August 2023 15:46:22 Uwe Kleine-König wrote:
> > > On Fri, Aug 04, 2023 at 12:35:13PM +0100, Russell King (Oracle) wrote:
> > > > Uwe has a SATA controller for a bunch of disks in an Armada 370 based
> > > > NAS platform that is connected to PCIe, and removing PCIe support
> > > > effectively makes his platform utterly useless.
> > >
> > > While this is true there is really a problem on my platform with
> > > accessing the hard disks via that pci controller and a 88SE9215 SATA
> > > controller. While it seems to work in principle, it's incredible slow.
> >
> > Exactly those are things which randomly does not work.
>
> I had this slow behaviour consistently on next-20230803 and
> next-20230804 was fine. I thought that meant that there was something
> fixed between these two trees. Do you suggest this is worth to
> investigate as it might just be some butterfly effect that made the
> problem go away?
These issues are there for a longer time, it started appearing after
5.15 lts version. And by your description it means that they were not
fixed yet.
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | https://www.pengutronix.de/ |
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-08 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230114164125.1298-1-pali@kernel.org>
[not found] ` <ZMzicVQEyHyZzBOc@shell.armlinux.org.uk>
2023-08-04 13:46 ` [PATCH] PCI: mvebu: Mark driver as BROKEN Uwe Kleine-König
2023-08-04 17:00 ` Uwe Kleine-König
2023-08-08 7:27 ` Pali Rohár
2023-08-08 7:38 ` Uwe Kleine-König
2023-08-08 7:56 ` Pali Rohár [this message]
[not found] <20230808072605.n3rjfsxuogza7qth@pali>
2023-08-08 16:26 ` Bjorn Helgaas
2023-08-08 19:20 ` Pali Rohár
2023-08-08 19:54 ` Russell King (Oracle)
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=20230808075623.lmhvotnzzjsz5r2o@pali \
--to=pali@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lpieralisi@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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