From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, mad skateman <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
hypexed@yahoo.com.au, Darren Stevens <darren@stevens-zone.net>,
debian-powerpc@lists.debian.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Lukas Wunner <lukas@wunner.de>,
regressions@lists.linux.dev,
luigi burdo <intermediadc@hotmail.com>, Al <al@datazap.net>
Subject: Re: [PPC] Boot problems after the pci-v6.18-changes
Date: Tue, 11 Nov 2025 06:15:20 +0100 [thread overview]
Message-ID: <a41d2ca1-fcd9-c416-b111-a958e92e94bf@xenosoft.de> (raw)
In-Reply-To: <3a384a25-0256-e827-2d66-9efc5723965d@xenosoft.de>
On 11/07/2025 06:06 AM, Christian Zigotzky wrote:
> On 11/05/2025 11:09 PM, Bjorn Helgaas wrote:
> >> I tested your patch with the RC4 of kernel 6.18 today.
> Unfortunately it
> >> doesn't solve the boot issue.
> >
> > Thanks for testing that. I see now why that approach doesn't work:
> > quirk_disable_aspm_l0s_l1() calls pci_disable_link_state(), which
> > updates the permissible ASPM link states, but pci_disable_link_state()
> > only works for devices at the downstream end of a link. It doesn't
> > work at all for Root Ports, which are at the upstream end of a link.
> >
> > Christian, you originally reported that both X5000 and X1000 were
> > broken. I suspect X1000 may have been fixed in v6.18-rc3 by
> > df5192d9bb0e ("PCI/ASPM: Enable only L0s and L1 for devicetree
> > platforms"), but I would love to have confirmation of that.
>
> Hello Bjorn,
>
> I will enable CONFIG_PCIEASPM and CONFIG_PCIEASPM_DEFAULT for the RC5
> of kernel 6.18 and test it with the X1000.
>
> Thanks,
> christian
>
Hello Bjorn,
I tested the RC5 of kernel 6.18 with CONFIG_PCIEASPM and
CONFIG_PCIEASPM_DEFAULT enabled on my X1000 today. Unfortunately the
boot problems are still present.
Cheers,
Christian
--
Sent with BrassMonkey 33.9.1 (https://github.com/chzigotzky/Web-Browsers-and-Suites-for-Linux-PPC/releases/tag/BrassMonkey_33.9.1)
prev parent reply other threads:[~2025-11-11 5:33 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3eedbe78-1fbd-4763-a7f3-ac5665e76a4a@xenosoft.de>
[not found] ` <15731ad7-83ff-c7ef-e4a1-8b11814572c2@xenosoft.de>
[not found] ` <17e37b22-5839-0e3a-0dbf-9c676adb0dec@xenosoft.de>
[not found] ` <3b210c92-4be6-ce49-7512-bb194475eeab@xenosoft.de>
2021-11-09 15:10 ` [PASEMI] Nemo board doesn't recognize any ATA disks with the pci-v5.16 updates Christian Zigotzky
2021-11-09 16:58 ` Bjorn Helgaas
2021-11-09 22:40 ` Krzysztof Wilczyński
2021-11-09 23:05 ` Arnd Bergmann
2021-11-09 23:18 ` Krzysztof Wilczyński
2021-11-10 16:42 ` Robert Święcki
2021-11-10 3:52 ` Damien Le Moal
2021-11-10 18:07 ` Christian Zigotzky
2021-11-10 18:41 ` Bjorn Helgaas
2021-11-10 19:09 ` Marc Zyngier
2021-11-11 5:24 ` Christian Zigotzky
2021-11-11 7:13 ` Marc Zyngier
2021-11-11 7:47 ` Christian Zigotzky
2021-11-11 10:20 ` Marc Zyngier
2021-11-11 10:44 ` Christian Zigotzky
2021-11-11 11:24 ` Marc Zyngier
2021-11-11 11:54 ` Christian Zigotzky
2021-11-11 22:21 ` Olof Johansson
2021-11-12 11:49 ` Segher Boessenkool
2021-11-11 17:39 ` Marc Zyngier
2021-11-12 9:40 ` Christian Zigotzky
2021-11-12 10:11 ` Christian Zigotzky
2021-11-12 11:00 ` Christian Zigotzky
2021-11-12 13:41 ` Marc Zyngier
2021-11-12 14:15 ` Christian Zigotzky
2021-11-12 14:46 ` Marc Zyngier
2021-11-12 15:01 ` Christian Zigotzky
2021-11-12 15:05 ` Christian Zigotzky
2025-10-08 16:35 ` [PPC] Boot problems after the pci-v6.18-changes Christian Zigotzky
2025-10-08 16:40 ` John Paul Adrian Glaubitz
2025-10-08 16:47 ` Christian Zigotzky
2025-10-08 19:51 ` Bjorn Helgaas
2025-10-09 4:54 ` Christian Zigotzky
2025-10-09 5:37 ` Lukas Wunner
2025-10-11 5:12 ` Christian Zigotzky
2025-10-11 5:25 ` Lukas Wunner
2025-10-11 15:11 ` Manivannan Sadhasivam
2025-10-11 19:34 ` Christian Zigotzky
2025-10-12 7:47 ` Christian Zigotzky
2025-10-12 8:26 ` Christian Zigotzky
2025-10-13 4:46 ` Christian Zigotzky
2025-10-13 5:02 ` Christian Zigotzky
2025-10-13 5:23 ` Christian Zigotzky
2025-10-13 14:50 ` Christian Zigotzky
2025-10-13 15:02 ` Christian Zigotzky
2025-10-13 15:38 ` Christian Zigotzky
2025-10-13 15:58 ` Manivannan Sadhasivam
[not found] ` <a2ee06b1-28a5-4cb1-9940-b225f9e6d6ee@xenosoft.de>
2025-10-14 4:55 ` Christian Zigotzky
2025-10-15 6:41 ` Manivannan Sadhasivam
2025-10-13 16:01 ` Manivannan Sadhasivam
2025-10-15 8:13 ` Herve Codina
2025-10-15 11:30 ` Christian Zigotzky
2025-10-15 11:58 ` Herve Codina
2025-10-15 12:27 ` Christian Zigotzky
2025-10-15 12:59 ` Herve Codina
[not found] ` <76026544-3472-4953-910A-376DD42BC6D0@xenosoft.de>
2025-10-15 13:17 ` Christian Zigotzky
2025-10-15 13:34 ` Herve Codina
2025-10-15 16:54 ` Christian Zigotzky
2025-10-15 17:15 ` Christian Zigotzky
2025-10-16 3:28 ` Christian Zigotzky
2025-10-16 7:36 ` Christian Zigotzky
2025-10-16 7:53 ` Manivannan Sadhasivam
2025-10-16 10:44 ` Christian Zigotzky
2025-10-17 5:35 ` Christian Zigotzky
2025-10-15 16:23 ` Manivannan Sadhasivam
2025-10-15 13:07 ` Christian Zigotzky
2025-10-15 12:50 ` Manivannan Sadhasivam
2025-10-23 7:38 ` Herve Codina
2025-10-23 8:49 ` Manivannan Sadhasivam
2025-10-23 9:19 ` Herve Codina
2025-10-23 16:59 ` Bjorn Helgaas
2025-10-15 23:40 ` Bjorn Helgaas
2025-10-13 21:06 ` Bjorn Helgaas
2025-10-14 18:51 ` Bjorn Helgaas
2025-10-30 22:11 ` Bjorn Helgaas
2025-11-01 5:39 ` Christian Zigotzky
2025-11-01 7:59 ` Christian Zigotzky
2025-11-01 17:06 ` Manivannan Sadhasivam
2025-11-03 18:28 ` Christian Zigotzky
2025-11-05 22:09 ` Bjorn Helgaas
2025-11-06 8:48 ` Hongxing Zhu
2025-11-06 18:25 ` Bjorn Helgaas
2025-11-07 2:26 ` Hongxing Zhu
2025-11-07 5:06 ` Christian Zigotzky
2025-11-11 5:15 ` Christian Zigotzky [this message]
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=a41d2ca1-fcd9-c416-b111-a958e92e94bf@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=al@datazap.net \
--cc=bhelgaas@google.com \
--cc=darren@stevens-zone.net \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=helgaas@kernel.org \
--cc=hypexed@yahoo.com.au \
--cc=info@xenosoft.de \
--cc=intermediadc@hotmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=madskateman@gmail.com \
--cc=mani@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rtd2@xtra.co.nz \
/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).