https://bugzilla.kernel.org/show_bug.cgi?id=81841
Marti Raudsepp ma...@juffo.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #22 from Marti Raudsepp ma...@juffo.org ---
Since I did not get further confirmation from Mr. Schopp, I decided to push it
and submit a patch: https://lkml.org/lkml/2014/10/2/223
The phrases Not sure what is going on here and should
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #19 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #15)
It's not clear to me which devices were being put in the same group.
Hi Joel, any updates on this? I posted my IOMMU groups in comment #17 in case
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #20 from Joel Schopp joel.sch...@amd.com ---
What updates are you looking for? Joerg's fix is now upstream.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #21 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #20)
What updates are you looking for? Joerg's fix is now upstream.
Yes, but there's still the issue with southbridge component isolation. You
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #18 from Joerg Roedel j...@8bytes.org ---
The fix is now upstream and part of Linux v3.17-rc2.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Joerg Roedel j...@8bytes.org changed:
What|Removed |Added
CC||j...@8bytes.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #13 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joerg Roedel from comment #12)
Thanks, Joerg
Indeed. Thanks, Joerg. And thanks everyone else too, you have been very
helpful!
I didn't have v3.13 sources handy, but I applied
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #14 from Joerg Roedel j...@8bytes.org ---
Hi Marti,
Indeed. Thanks, Joerg. And thanks everyone else too, you have been very
helpful!
I didn't have v3.13 sources handy, but I applied the attachment 146311
I can start shut down
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #15 from Joel Schopp joel.sch...@amd.com ---
(In reply to Joel Schopp from comment #10)
AMD would need to confirm it.
I don't have an answer for you offhand. Let me do some digging and get you
an answer.
I am sorry if I
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #16 from Alex Williamson alex.william...@redhat.com ---
(In reply to Joel Schopp from comment #15)
(In reply to Joel Schopp from comment #10)
AMD would need to confirm it.
I don't have an answer for you offhand. Let me do
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #17 from Marti Raudsepp ma...@juffo.org ---
It's an ASRock FM2A88X Extreme6+ motherboard with the AMD A88X (Bolton-D4)
chipset.
There are 12 IOMMU groups on the system. The problematic group for me is number
9 because the legacy PCI
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #11 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #10)
How would I go about confirming that? What are the chances that they care,
and provide accurate information to a random person?
Are you
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #1 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145421
-- https://bugzilla.kernel.org/attachment.cgi?id=145421action=edit
crash_netconsole.txt
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #2 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145431
-- https://bugzilla.kernel.org/attachment.cgi?id=145431action=edit
startup_dmesg.txt
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #3 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145441
-- https://bugzilla.kernel.org/attachment.cgi?id=145441action=edit
dmidecode.txt
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Marti Raudsepp ma...@juffo.org changed:
What|Removed |Added
Kernel Version|3.13 (Ubuntu: |3.16.0 (originally Ubuntu
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Alex Williamson alex.william...@redhat.com changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #6 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
vfio: error, group 9 is not viable, please ensure all devices
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #7 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #6)
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #8 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the issue.
I see. This page claims so:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #9 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #8)
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Joel Schopp joel.sch...@amd.com changed:
What|Removed |Added
CC||joel.sch...@amd.com
---
23 matches
Mail list logo
