IOAPIC[0] not in IVRS table
up vote
6
down vote
favorite
I have a fresh Ubuntu install from USB. When I boot the PC it takes me straight to GNU Grub, when I select Ubuntu I get the following messages.
[Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table
[Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
AMD-Vi: Disabling interrupt remapping
I can get to the Ubuntu desktop via "Advanced options for Ubuntu" > "Ubuntu, with Linux 4.2.0-30-generic (recovery mode)" > "resume" but the CPU runs at nearly 100% and is not sustinable.
PC Specs:
AMD A6-6400K
MSI A68HI Mini ITX FM2+ Motherboard
linux ubuntu grub
add a comment |
up vote
6
down vote
favorite
I have a fresh Ubuntu install from USB. When I boot the PC it takes me straight to GNU Grub, when I select Ubuntu I get the following messages.
[Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table
[Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
AMD-Vi: Disabling interrupt remapping
I can get to the Ubuntu desktop via "Advanced options for Ubuntu" > "Ubuntu, with Linux 4.2.0-30-generic (recovery mode)" > "resume" but the CPU runs at nearly 100% and is not sustinable.
PC Specs:
AMD A6-6400K
MSI A68HI Mini ITX FM2+ Motherboard
linux ubuntu grub
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
1
@outisnihil You can useivrs_ioapickernel option to fix IVRS table. See my answer for details.
– Mircea Vutcovici
Oct 1 '17 at 3:19
add a comment |
up vote
6
down vote
favorite
up vote
6
down vote
favorite
I have a fresh Ubuntu install from USB. When I boot the PC it takes me straight to GNU Grub, when I select Ubuntu I get the following messages.
[Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table
[Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
AMD-Vi: Disabling interrupt remapping
I can get to the Ubuntu desktop via "Advanced options for Ubuntu" > "Ubuntu, with Linux 4.2.0-30-generic (recovery mode)" > "resume" but the CPU runs at nearly 100% and is not sustinable.
PC Specs:
AMD A6-6400K
MSI A68HI Mini ITX FM2+ Motherboard
linux ubuntu grub
I have a fresh Ubuntu install from USB. When I boot the PC it takes me straight to GNU Grub, when I select Ubuntu I get the following messages.
[Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table
[Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
AMD-Vi: Disabling interrupt remapping
I can get to the Ubuntu desktop via "Advanced options for Ubuntu" > "Ubuntu, with Linux 4.2.0-30-generic (recovery mode)" > "resume" but the CPU runs at nearly 100% and is not sustinable.
PC Specs:
AMD A6-6400K
MSI A68HI Mini ITX FM2+ Motherboard
linux ubuntu grub
linux ubuntu grub
edited Mar 12 '16 at 20:48
asked Mar 12 '16 at 18:17
Maria Warnes
5116
5116
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
1
@outisnihil You can useivrs_ioapickernel option to fix IVRS table. See my answer for details.
– Mircea Vutcovici
Oct 1 '17 at 3:19
add a comment |
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
1
@outisnihil You can useivrs_ioapickernel option to fix IVRS table. See my answer for details.
– Mircea Vutcovici
Oct 1 '17 at 3:19
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
1
1
@outisnihil You can use
ivrs_ioapic kernel option to fix IVRS table. See my answer for details.– Mircea Vutcovici
Oct 1 '17 at 3:19
@outisnihil You can use
ivrs_ioapic kernel option to fix IVRS table. See my answer for details.– Mircea Vutcovici
Oct 1 '17 at 3:19
add a comment |
2 Answers
2
active
oldest
votes
up vote
7
down vote
The reason the CPU is all the time 100% used I think it is different than the message you are seeing.
About the error message
Now about AMD-Vi: IOAPIC[0] not in IVRS table and AMD-Vi: No southbridge IOAPIC found in IVRS tableerrors. Those messages mean that your CMOS/BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU and SMBus Controller. IVRS = I/O Virtualization Reporting Structure. See also: http://support.amd.com/TechDocs/48882_IOMMU.pdf
What is IOMMU?
IOMMU is a hardware unit that today is part of CPU. It allows to map device-visible virtual addresses to physical addresses.
Why IOMMU?
- IOMMU allows to have better security and protect your computer from some attacks from someone having access to some busses like PCIe and firewire.
- you can expose a physical PCIe device to a VM.
- it is required for SR-IOV (VNF)
Fixing "AMD-Vi: IOAPIC[0] not in IVRS table"
- Update motherboard firmware
The proper fix should come from hardware manufacturer of the motherboard. So if you have a BIOS/firmware update for your motherboard, install it as this might fix the problem. Unfortunately for my motherboard (Asus Crosshair V Formula) the IVRS is broken even in the latest BIOS/firmware update (version 1703, Release Date: 10/17/2012).
- Linux workarround
If the manufacturer of the MB is not offering a fix, you can fix this in Linux by specifying in the kernel startup parameters where those devices are located using ivrs_ioapic option.
Here are the steps to do it. For more details see: https://ubuntuforums.org/showthread.php?t=2254677
Boot your kernel by adding amd_iommu_dump=1 to the kernel options. You can do this via grub menu during boot.
In the kernel log, you will see some lines like:
$ dmesg |grep 'DEV_SPECIAL(IOAPIC|not in IVRS table'
[ 0.133756] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.133995] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 0.134116] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[ 0.134235] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
$
Write down the indexes from IOAPIC. In this case those are 5 and 6. Note the devid, where 00:14.0 is ok and 00:00.1 is incorrect.
Search for the bus address for those devices and write down the addresses (00:00.2 and 00:14.0)
$ lspci -nn | egrep "SMBus | IOMMU"
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
$
Now add as kernel parameters: ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 where index 5 and 6 were found in dmesg output and the values are from lspci output. You can make this permanent by editing /etc/default/grub file, then running grub2-mkconfig -o /boot/grub2/grub.cfg.
- Disable IOMMU in UEFI/BIOS configuration
Disabling IOMMU has a small performance benefit. But it is undesirable to disable it for security and stability of the system. IOMMU is required for certain virtualization setups (PCI pass-through, SR-IOV) and disabling it is not an option.
add a comment |
up vote
2
down vote
I updated the firmware of my motherboard and this has appeared to have fixed it.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1052023%2fioapic0-not-in-ivrs-table%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
up vote
7
down vote
The reason the CPU is all the time 100% used I think it is different than the message you are seeing.
About the error message
Now about AMD-Vi: IOAPIC[0] not in IVRS table and AMD-Vi: No southbridge IOAPIC found in IVRS tableerrors. Those messages mean that your CMOS/BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU and SMBus Controller. IVRS = I/O Virtualization Reporting Structure. See also: http://support.amd.com/TechDocs/48882_IOMMU.pdf
What is IOMMU?
IOMMU is a hardware unit that today is part of CPU. It allows to map device-visible virtual addresses to physical addresses.
Why IOMMU?
- IOMMU allows to have better security and protect your computer from some attacks from someone having access to some busses like PCIe and firewire.
- you can expose a physical PCIe device to a VM.
- it is required for SR-IOV (VNF)
Fixing "AMD-Vi: IOAPIC[0] not in IVRS table"
- Update motherboard firmware
The proper fix should come from hardware manufacturer of the motherboard. So if you have a BIOS/firmware update for your motherboard, install it as this might fix the problem. Unfortunately for my motherboard (Asus Crosshair V Formula) the IVRS is broken even in the latest BIOS/firmware update (version 1703, Release Date: 10/17/2012).
- Linux workarround
If the manufacturer of the MB is not offering a fix, you can fix this in Linux by specifying in the kernel startup parameters where those devices are located using ivrs_ioapic option.
Here are the steps to do it. For more details see: https://ubuntuforums.org/showthread.php?t=2254677
Boot your kernel by adding amd_iommu_dump=1 to the kernel options. You can do this via grub menu during boot.
In the kernel log, you will see some lines like:
$ dmesg |grep 'DEV_SPECIAL(IOAPIC|not in IVRS table'
[ 0.133756] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.133995] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 0.134116] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[ 0.134235] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
$
Write down the indexes from IOAPIC. In this case those are 5 and 6. Note the devid, where 00:14.0 is ok and 00:00.1 is incorrect.
Search for the bus address for those devices and write down the addresses (00:00.2 and 00:14.0)
$ lspci -nn | egrep "SMBus | IOMMU"
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
$
Now add as kernel parameters: ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 where index 5 and 6 were found in dmesg output and the values are from lspci output. You can make this permanent by editing /etc/default/grub file, then running grub2-mkconfig -o /boot/grub2/grub.cfg.
- Disable IOMMU in UEFI/BIOS configuration
Disabling IOMMU has a small performance benefit. But it is undesirable to disable it for security and stability of the system. IOMMU is required for certain virtualization setups (PCI pass-through, SR-IOV) and disabling it is not an option.
add a comment |
up vote
7
down vote
The reason the CPU is all the time 100% used I think it is different than the message you are seeing.
About the error message
Now about AMD-Vi: IOAPIC[0] not in IVRS table and AMD-Vi: No southbridge IOAPIC found in IVRS tableerrors. Those messages mean that your CMOS/BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU and SMBus Controller. IVRS = I/O Virtualization Reporting Structure. See also: http://support.amd.com/TechDocs/48882_IOMMU.pdf
What is IOMMU?
IOMMU is a hardware unit that today is part of CPU. It allows to map device-visible virtual addresses to physical addresses.
Why IOMMU?
- IOMMU allows to have better security and protect your computer from some attacks from someone having access to some busses like PCIe and firewire.
- you can expose a physical PCIe device to a VM.
- it is required for SR-IOV (VNF)
Fixing "AMD-Vi: IOAPIC[0] not in IVRS table"
- Update motherboard firmware
The proper fix should come from hardware manufacturer of the motherboard. So if you have a BIOS/firmware update for your motherboard, install it as this might fix the problem. Unfortunately for my motherboard (Asus Crosshair V Formula) the IVRS is broken even in the latest BIOS/firmware update (version 1703, Release Date: 10/17/2012).
- Linux workarround
If the manufacturer of the MB is not offering a fix, you can fix this in Linux by specifying in the kernel startup parameters where those devices are located using ivrs_ioapic option.
Here are the steps to do it. For more details see: https://ubuntuforums.org/showthread.php?t=2254677
Boot your kernel by adding amd_iommu_dump=1 to the kernel options. You can do this via grub menu during boot.
In the kernel log, you will see some lines like:
$ dmesg |grep 'DEV_SPECIAL(IOAPIC|not in IVRS table'
[ 0.133756] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.133995] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 0.134116] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[ 0.134235] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
$
Write down the indexes from IOAPIC. In this case those are 5 and 6. Note the devid, where 00:14.0 is ok and 00:00.1 is incorrect.
Search for the bus address for those devices and write down the addresses (00:00.2 and 00:14.0)
$ lspci -nn | egrep "SMBus | IOMMU"
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
$
Now add as kernel parameters: ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 where index 5 and 6 were found in dmesg output and the values are from lspci output. You can make this permanent by editing /etc/default/grub file, then running grub2-mkconfig -o /boot/grub2/grub.cfg.
- Disable IOMMU in UEFI/BIOS configuration
Disabling IOMMU has a small performance benefit. But it is undesirable to disable it for security and stability of the system. IOMMU is required for certain virtualization setups (PCI pass-through, SR-IOV) and disabling it is not an option.
add a comment |
up vote
7
down vote
up vote
7
down vote
The reason the CPU is all the time 100% used I think it is different than the message you are seeing.
About the error message
Now about AMD-Vi: IOAPIC[0] not in IVRS table and AMD-Vi: No southbridge IOAPIC found in IVRS tableerrors. Those messages mean that your CMOS/BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU and SMBus Controller. IVRS = I/O Virtualization Reporting Structure. See also: http://support.amd.com/TechDocs/48882_IOMMU.pdf
What is IOMMU?
IOMMU is a hardware unit that today is part of CPU. It allows to map device-visible virtual addresses to physical addresses.
Why IOMMU?
- IOMMU allows to have better security and protect your computer from some attacks from someone having access to some busses like PCIe and firewire.
- you can expose a physical PCIe device to a VM.
- it is required for SR-IOV (VNF)
Fixing "AMD-Vi: IOAPIC[0] not in IVRS table"
- Update motherboard firmware
The proper fix should come from hardware manufacturer of the motherboard. So if you have a BIOS/firmware update for your motherboard, install it as this might fix the problem. Unfortunately for my motherboard (Asus Crosshair V Formula) the IVRS is broken even in the latest BIOS/firmware update (version 1703, Release Date: 10/17/2012).
- Linux workarround
If the manufacturer of the MB is not offering a fix, you can fix this in Linux by specifying in the kernel startup parameters where those devices are located using ivrs_ioapic option.
Here are the steps to do it. For more details see: https://ubuntuforums.org/showthread.php?t=2254677
Boot your kernel by adding amd_iommu_dump=1 to the kernel options. You can do this via grub menu during boot.
In the kernel log, you will see some lines like:
$ dmesg |grep 'DEV_SPECIAL(IOAPIC|not in IVRS table'
[ 0.133756] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.133995] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 0.134116] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[ 0.134235] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
$
Write down the indexes from IOAPIC. In this case those are 5 and 6. Note the devid, where 00:14.0 is ok and 00:00.1 is incorrect.
Search for the bus address for those devices and write down the addresses (00:00.2 and 00:14.0)
$ lspci -nn | egrep "SMBus | IOMMU"
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
$
Now add as kernel parameters: ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 where index 5 and 6 were found in dmesg output and the values are from lspci output. You can make this permanent by editing /etc/default/grub file, then running grub2-mkconfig -o /boot/grub2/grub.cfg.
- Disable IOMMU in UEFI/BIOS configuration
Disabling IOMMU has a small performance benefit. But it is undesirable to disable it for security and stability of the system. IOMMU is required for certain virtualization setups (PCI pass-through, SR-IOV) and disabling it is not an option.
The reason the CPU is all the time 100% used I think it is different than the message you are seeing.
About the error message
Now about AMD-Vi: IOAPIC[0] not in IVRS table and AMD-Vi: No southbridge IOAPIC found in IVRS tableerrors. Those messages mean that your CMOS/BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU and SMBus Controller. IVRS = I/O Virtualization Reporting Structure. See also: http://support.amd.com/TechDocs/48882_IOMMU.pdf
What is IOMMU?
IOMMU is a hardware unit that today is part of CPU. It allows to map device-visible virtual addresses to physical addresses.
Why IOMMU?
- IOMMU allows to have better security and protect your computer from some attacks from someone having access to some busses like PCIe and firewire.
- you can expose a physical PCIe device to a VM.
- it is required for SR-IOV (VNF)
Fixing "AMD-Vi: IOAPIC[0] not in IVRS table"
- Update motherboard firmware
The proper fix should come from hardware manufacturer of the motherboard. So if you have a BIOS/firmware update for your motherboard, install it as this might fix the problem. Unfortunately for my motherboard (Asus Crosshair V Formula) the IVRS is broken even in the latest BIOS/firmware update (version 1703, Release Date: 10/17/2012).
- Linux workarround
If the manufacturer of the MB is not offering a fix, you can fix this in Linux by specifying in the kernel startup parameters where those devices are located using ivrs_ioapic option.
Here are the steps to do it. For more details see: https://ubuntuforums.org/showthread.php?t=2254677
Boot your kernel by adding amd_iommu_dump=1 to the kernel options. You can do this via grub menu during boot.
In the kernel log, you will see some lines like:
$ dmesg |grep 'DEV_SPECIAL(IOAPIC|not in IVRS table'
[ 0.133756] AMD-Vi: DEV_SPECIAL(IOAPIC[0]) devid: 00:14.0
[ 0.133995] AMD-Vi: DEV_SPECIAL(IOAPIC[255]) devid: 00:00.1
[ 0.134116] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
[ 0.134235] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
$
Write down the indexes from IOAPIC. In this case those are 5 and 6. Note the devid, where 00:14.0 is ok and 00:00.1 is incorrect.
Search for the bus address for those devices and write down the addresses (00:00.2 and 00:14.0)
$ lspci -nn | egrep "SMBus | IOMMU"
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
$
Now add as kernel parameters: ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 where index 5 and 6 were found in dmesg output and the values are from lspci output. You can make this permanent by editing /etc/default/grub file, then running grub2-mkconfig -o /boot/grub2/grub.cfg.
- Disable IOMMU in UEFI/BIOS configuration
Disabling IOMMU has a small performance benefit. But it is undesirable to disable it for security and stability of the system. IOMMU is required for certain virtualization setups (PCI pass-through, SR-IOV) and disabling it is not an option.
edited Nov 28 at 22:56
answered Oct 1 '17 at 3:11
Mircea Vutcovici
36637
36637
add a comment |
add a comment |
up vote
2
down vote
I updated the firmware of my motherboard and this has appeared to have fixed it.
add a comment |
up vote
2
down vote
I updated the firmware of my motherboard and this has appeared to have fixed it.
add a comment |
up vote
2
down vote
up vote
2
down vote
I updated the firmware of my motherboard and this has appeared to have fixed it.
I updated the firmware of my motherboard and this has appeared to have fixed it.
answered Apr 4 '16 at 14:32
Maria Warnes
5116
5116
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1052023%2fioapic0-not-in-ivrs-table%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
Updating the firmware didn't work for me. Anyone have any other solutions?
– outis nihil
May 5 '17 at 17:57
1
@outisnihil You can use
ivrs_ioapickernel option to fix IVRS table. See my answer for details.– Mircea Vutcovici
Oct 1 '17 at 3:19