Bug 1188654 - IOMMU enabled blocks recognition of Via VL805 USB 3.0 chipset ; 3.18.3-201.fc21.x86_64
Summary: IOMMU enabled blocks recognition of Via VL805 USB 3.0 chipset ; 3.18.3-201.fc...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-03 13:30 UTC by bob
Modified: 2023-07-04 08:16 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:12:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output with iommu disabled (74.91 KB, text/plain)
2015-02-03 13:48 UTC, bob
no flags Details
lsusb output with iommu disabled (verbose) (23.34 KB, text/plain)
2015-02-03 13:49 UTC, bob
no flags Details
dmesg output with iommu enabled (151.33 KB, text/plain)
2015-02-03 13:49 UTC, bob
no flags Details
lsusb output with iommu enabled (verbose) (14.83 KB, text/plain)
2015-02-03 13:50 UTC, bob
no flags Details

Description bob 2015-02-03 13:30:58 UTC
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

Comment 2 bob 2015-02-03 13:48:33 UTC
Created attachment 987580 [details]
dmesg output with iommu disabled

Comment 3 bob 2015-02-03 13:49:19 UTC
Created attachment 987581 [details]
lsusb output with iommu disabled (verbose)

Comment 4 bob 2015-02-03 13:49:54 UTC
Created attachment 987582 [details]
dmesg output with iommu enabled

Comment 5 bob 2015-02-03 13:50:26 UTC
Created attachment 987583 [details]
lsusb output with iommu enabled (verbose)

Comment 6 bob 2015-02-20 10:07:10 UTC
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.

Comment 7 bob 2015-02-23 11:20:01 UTC
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 8 Fedora 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 9 Fedora 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 10 Fedora 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.

Comment 11 bob 2016-09-15 13:03:29 UTC
Reopening as it has never been fixed and remains a problem in F24.

Comment 12 Laura Abbott 2016-09-23 19:15:07 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 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.

Comment 13 bob 2016-09-24 12:44:57 UTC
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 14 Justin 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 15 Justin 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 16 charli 2022-07-05 11:44:43 UTC Comment hidden (spam)
Comment 18 DareDeviled09 2022-10-14 12:08:51 UTC Comment hidden (spam)
Comment 19 DareDeviled09 2022-10-17 06:45:05 UTC Comment hidden (spam)
Comment 21 Rubel Ahmed 2023-03-29 05:52:53 UTC Comment hidden (spam)
Comment 22 Rubel Ahmed 2023-03-31 14:10:41 UTC Comment hidden (spam)
Comment 23 shane watson 2023-04-07 08:14:37 UTC Comment hidden (spam)
Comment 24 shane watson 2023-04-11 10:40:12 UTC Comment hidden (spam)
Comment 25 aiden wills 2023-05-20 06:35:02 UTC Comment hidden (spam)

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