Description of problem:
When IOMMU is enabled in BIOS and 3.18.3-201 is booted on an AMD 970 chipset, the recognition of the VIA VL805 chipset for USB 3.0 is prevented. The USB 3.0 ports on the motherboard provided by the VL 805 chipset are non-functional; the USB 2.0 ports provided by the AMD 970 southbridge work fine.
When IOMMU is disabled in BIOS the VL805 chipset is properly recognized and the USB 3.0 ports are functional.
Problem also reported on Ubuntu and Mint, where users disable IOMMU to gain USB 3.0 functionality, but I can't find a bug report.
Version-Release number of selected component (if applicable):
3.18.3-201.fc21.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Toggle status of IOMMU between on/off in BIOS.
2. Boot kernel 3.18.3-201.fc21.x86_64
3. VIA VL803 chipset and USB 3.0 ports are dead if IOMMU enabled.
Additional info:
Motherboard = Gigabyte GA-970A-UD3P
Chipset = AMD 970
How can I follow the development of a fix for this bug by the kernel maintainers? I've filed enough kernel bugs to know that nobody from the kernel group ever posts here, even when the bugs are being addressed. Thanks.
Trying to be a little more clear on the bug -- the USB device driver appears to be causing AMD-Vi page fault errors when IOMMU is enabled.
Comment 8Fedora Kernel Team
2015-04-28 18:34:00 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs.
Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22.
If you experience different issues, please open a new bug report for those.
Comment 9Fedora End Of Life
2015-11-04 12:20:27 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '21'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 21 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 10Fedora End Of Life
2015-12-02 08:29:27 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.
Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.
If you experience different issues, please open a new bug report for those.
This bug has already been filed against currently supported versions. Nobody appears to have noticed.
All of these new AMD IOMMU related bug reports have received no responses, just as this F21 one did during F21's entire support lifetime. This ongoing lack of attention creates the impression that nobody cares to address problems with AMD IOMMU.
F24 Bug 1376455 opened 2016-09-15 09:11:42 EDT
F25-Alpha-2 Bug 1377011 2016-09-17 09:10:10 EDT
Comment 14Justin M. Forbes
2017-04-11 14:52:32 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
If you experience different issues, please open a new bug report for those.
Comment 15Justin M. Forbes
2017-04-28 17:12:00 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the
relevant data from the latest kernel you are running and any data that might have been requested previously.
Comment 16charli
2022-07-05 11:44:43 UTC
Comment hidden (spam)
Comment 19DareDeviled09
2022-10-17 06:45:05 UTC
Comment hidden (spam)
It has been simply incredibly generous with you to provide openly what exactly many individuals would’ve marketed for an ebook to end up making some cash for their end, primarily given that you could have tried it in the event you wanted https://www.reddit.com/r/redditpsychic/comments/y245oz/where_to_find_psychic/ psychic reddit
Comment 20litletampin
2023-01-11 07:07:27 UTC
Comment hidden (spam)
Comment 25aiden wills
2023-05-20 06:35:02 UTC
Comment hidden (spam)
One of the most frustrating things you may experience with a printer is when it suddenly prints blank pages. And if you’re worTking on a crucial document or file, this problem can be quite maddening. Some Example Blogs :- printer printing blank pages | my printer is printing blank pages printer has ink but prints blank pages | printer keeps printing blank pages
https://esoftsafe.com/fix-printer-printing-blank-pages/