Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1792564 - Consider enabling CONFIG_PCIE_ROCKCHIP_HOST and CONFIG_PHY_ROCKCHIP_PCIE as modules.
Summary: Consider enabling CONFIG_PCIE_ROCKCHIP_HOST and CONFIG_PHY_ROCKCHIP_PCIE as m...
Keywords:
Status: CLOSED DUPLICATE of bug 1704945
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: aarch64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-18 00:54 UTC by Luke Yelavich
Modified: 2020-02-17 14:47 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-11 11:01:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Luke Yelavich 2020-01-18 00:54:13 UTC
1. Please describe the problem:

The configuration options in the summary are not currently enabled in Fedora 31 or rawhide. Enabling these to build as modules allows the use of PCI Express devices on boards using RockChip SoCs such as the RockPro64.


2. What is the Version-Release number of the kernel:

Kernel 5.4.12 in Fedora 31, but the kernel packaging on pagure for rawhide also has these currently disabled.


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
I don't think these config options have ever been enabled

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below
I have a RockPro64 running Fedora 31, and cannot use the connected SATA PCIE card. Rebuilding the kernel locally with these options enabled as modules allows me to use the attached drives on the SATA card.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Have not actually tested on rawhide, but checking the packaging, I suspect it would not.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

No logs currently, don't really think any are really necessary, but can grab them if required.

Comment 1 Jeremy Cline 2020-02-07 19:40:22 UTC
Hi,

I've enabled both of these modules in Rawhide starting with kernel-5.6.0-0.rc0.git5.1.fc32 and I've dropped it into the v5.5 rebase for stable Fedora releases.

Comment 2 Peter Robinson 2020-02-11 09:14:40 UTC
This was explicitly disabled because it caused issues across a number of devices. Who is on the hook to deal with those issues?

Comment 3 Peter Robinson 2020-02-11 11:01:59 UTC
Still an issue: [   33.654926] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!

And this is a duplicate where it's well where this is well documented.

*** This bug has been marked as a duplicate of bug 1704945 ***

Comment 4 Jeremy Cline 2020-02-11 14:35:17 UTC
Whoops, sorry. I either forgot or missed it. I'll flip it back off.

Comment 5 Peter Robinson 2020-02-11 14:37:09 UTC
(In reply to Jeremy Cline from comment #4)
> Whoops, sorry. I either forgot or missed it. I'll flip it back off.

already did

Comment 6 Jeremy Cline 2020-02-11 14:44:20 UTC
Thanks.

I do look at the git history of a config, so linking to bugzillas (as you did when you turned this back off) should keep me from forgetfully flipping things back on that are known to be broken.


Note You need to log in before you can comment on or make changes to this bug.