kfd: error getting iommu info
I got this error during boot process.
[15.757121] kfd kfd: error getting iommu info. is the iommu enabled?
[15.757182] kfd kfd: Error initializing iommuv2 for device (1002:1318)
[15.757245] Creating topology SYSFS entries
[15.757376] kfd kfd: device (1002:1318) NOT added due to errors
How can I fix it?
linux boot
edited Jan 31 '18 at 9:59
galoget
36319
asked Feb 17 '16 at 18:11
mlibre
564615
add a comment |
I got this error during boot process.
[15.757121] kfd kfd: error getting iommu info. is the iommu enabled?
[15.757182] kfd kfd: Error initializing iommuv2 for device (1002:1318)
[15.757245] Creating topology SYSFS entries
[15.757376] kfd kfd: device (1002:1318) NOT added due to errors
How can I fix it?
linux boot
edited Jan 31 '18 at 9:59
galoget
36319
asked Feb 17 '16 at 18:11
mlibre
564615
add a comment |
I got this error during boot process.
[15.757121] kfd kfd: error getting iommu info. is the iommu enabled?
[15.757182] kfd kfd: Error initializing iommuv2 for device (1002:1318)
[15.757245] Creating topology SYSFS entries
[15.757376] kfd kfd: device (1002:1318) NOT added due to errors
How can I fix it?
linux boot
edited Jan 31 '18 at 9:59
galoget
36319
asked Feb 17 '16 at 18:11
mlibre
564615
I got this error during boot process.
[15.757121] kfd kfd: error getting iommu info. is the iommu enabled?
[15.757182] kfd kfd: Error initializing iommuv2 for device (1002:1318)
[15.757245] Creating topology SYSFS entries
[15.757376] kfd kfd: device (1002:1318) NOT added due to errors
How can I fix it?
linux boot
linux boot
edited Jan 31 '18 at 9:59
galoget
36319
asked Feb 17 '16 at 18:11
mlibre
564615
edited Jan 31 '18 at 9:59
galoget
36319
asked Feb 17 '16 at 18:11
mlibre
564615
edited Jan 31 '18 at 9:59
galoget
36319
edited Jan 31 '18 at 9:59
galoget
36319
edited Jan 31 '18 at 9:59
galoget
36319
36319
asked Feb 17 '16 at 18:11
mlibre
564615
asked Feb 17 '16 at 18:11
mlibre
564615
asked Feb 17 '16 at 18:11
mlibre
564615
564615
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Found this from a Google Search:
UEFI boot was a red herring. The real problem was that you need a kfd.rules file in /etc/udev/rules.d. The file must say:
KERNEL=="kfd", MODE="0666"
Installing mainline 3.19 in Ubuntu 14.10 created this file during package installation (we think?), but Ubuntu 15.04 does not create this file by default. You must do it by hand. Then the HSA software stack works!
Problem solved.
edited Jan 31 '18 at 10:10
galoget
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
add a comment |
Bad BIOS UEFI tables are a common problem, which yield a non funtional iommu.
If on X86 or AMD64 try:
Edit the file /etc/default/grub:
Change the line
GRUB_CMDLINE_LINUX=""
To:
GRUB_CMDLINE_LINUX="iommu=pt"
Run:
sudo update-grub
Reboot.
In many cases the "pass through" function of the kernel will provide iommu funtionality also the BIOS is foobar. The HSA software stack will run on a system with a working iommu funtionality without tiggering the iommu error message.
edited Jan 31 '18 at 10:10
galoget
36319
answered Dec 25 '17 at 18:47
Jan
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f263901%2fkfd-error-getting-iommu-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Found this from a Google Search:
UEFI boot was a red herring. The real problem was that you need a kfd.rules file in /etc/udev/rules.d. The file must say:
KERNEL=="kfd", MODE="0666"
Installing mainline 3.19 in Ubuntu 14.10 created this file during package installation (we think?), but Ubuntu 15.04 does not create this file by default. You must do it by hand. Then the HSA software stack works!
Problem solved.
edited Jan 31 '18 at 10:10
galoget
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
add a comment |
Found this from a Google Search:
UEFI boot was a red herring. The real problem was that you need a kfd.rules file in /etc/udev/rules.d. The file must say:
KERNEL=="kfd", MODE="0666"
Installing mainline 3.19 in Ubuntu 14.10 created this file during package installation (we think?), but Ubuntu 15.04 does not create this file by default. You must do it by hand. Then the HSA software stack works!
Problem solved.
edited Jan 31 '18 at 10:10
galoget
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
add a comment |
Found this from a Google Search:
UEFI boot was a red herring. The real problem was that you need a kfd.rules file in /etc/udev/rules.d. The file must say:
KERNEL=="kfd", MODE="0666"
Installing mainline 3.19 in Ubuntu 14.10 created this file during package installation (we think?), but Ubuntu 15.04 does not create this file by default. You must do it by hand. Then the HSA software stack works!
Problem solved.
edited Jan 31 '18 at 10:10
galoget
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
Found this from a Google Search:
UEFI boot was a red herring. The real problem was that you need a kfd.rules file in /etc/udev/rules.d. The file must say:
KERNEL=="kfd", MODE="0666"
Installing mainline 3.19 in Ubuntu 14.10 created this file during package installation (we think?), but Ubuntu 15.04 does not create this file by default. You must do it by hand. Then the HSA software stack works!
Problem solved.
edited Jan 31 '18 at 10:10
galoget
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
edited Jan 31 '18 at 10:10
galoget
36319
edited Jan 31 '18 at 10:10
galoget
36319
edited Jan 31 '18 at 10:10
galoget
36319
36319
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
answered Jan 23 '17 at 0:58
Mohd Ridzuan Isa
1
1
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
add a comment |
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:04
add a comment |
Bad BIOS UEFI tables are a common problem, which yield a non funtional iommu.
If on X86 or AMD64 try:
Edit the file /etc/default/grub:
Change the line
GRUB_CMDLINE_LINUX=""
To:
GRUB_CMDLINE_LINUX="iommu=pt"
Run:
sudo update-grub
Reboot.
In many cases the "pass through" function of the kernel will provide iommu funtionality also the BIOS is foobar. The HSA software stack will run on a system with a working iommu funtionality without tiggering the iommu error message.
edited Jan 31 '18 at 10:10
galoget
36319
answered Dec 25 '17 at 18:47
Jan
1
add a comment |
Bad BIOS UEFI tables are a common problem, which yield a non funtional iommu.
If on X86 or AMD64 try:
Edit the file /etc/default/grub:
Change the line
GRUB_CMDLINE_LINUX=""
To:
GRUB_CMDLINE_LINUX="iommu=pt"
Run:
sudo update-grub
Reboot.
In many cases the "pass through" function of the kernel will provide iommu funtionality also the BIOS is foobar. The HSA software stack will run on a system with a working iommu funtionality without tiggering the iommu error message.
edited Jan 31 '18 at 10:10
galoget
36319
answered Dec 25 '17 at 18:47
Jan
1
add a comment |
Bad BIOS UEFI tables are a common problem, which yield a non funtional iommu.
If on X86 or AMD64 try:
Edit the file /etc/default/grub:
Change the line
GRUB_CMDLINE_LINUX=""
To:
GRUB_CMDLINE_LINUX="iommu=pt"
Run:
sudo update-grub
Reboot.
In many cases the "pass through" function of the kernel will provide iommu funtionality also the BIOS is foobar. The HSA software stack will run on a system with a working iommu funtionality without tiggering the iommu error message.
edited Jan 31 '18 at 10:10
galoget
36319
answered Dec 25 '17 at 18:47
Jan
1
Bad BIOS UEFI tables are a common problem, which yield a non funtional iommu.
If on X86 or AMD64 try:
Edit the file /etc/default/grub:
Change the line
GRUB_CMDLINE_LINUX=""
To:
GRUB_CMDLINE_LINUX="iommu=pt"
Run:
sudo update-grub
Reboot.
In many cases the "pass through" function of the kernel will provide iommu funtionality also the BIOS is foobar. The HSA software stack will run on a system with a working iommu funtionality without tiggering the iommu error message.
edited Jan 31 '18 at 10:10
galoget
36319
answered Dec 25 '17 at 18:47
Jan
1
edited Jan 31 '18 at 10:10
galoget
36319
edited Jan 31 '18 at 10:10
galoget
36319
edited Jan 31 '18 at 10:10
galoget
36319
36319
answered Dec 25 '17 at 18:47
Jan
1
answered Dec 25 '17 at 18:47
Jan
1
answered Dec 25 '17 at 18:47
Jan
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f263901%2fkfd-error-getting-iommu-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
