How to report a hardware-specific issue with Ubuntu stability
up vote
0
down vote
favorite
I had been fighting with boot stability for my Ryzen 2400G desktop, initially because of buggy BIOS from ASRock, but then afterwards because of what I consider a subtle issue. After installing 18.04 and 18.10 with the same results, the system would rarely boot reliably (but would on occasion), I figured out that I needed to add a boot flag,
iommu=soft
to /etc/default/grub. This webpage from Majaro clued me in,
https://forum.manjaro.org/t/amd-ryzen-problems-and-fixes/55533
I have not found any information like this on Ask Ubuntu, but maybe I'm wrong. Considering there are TONS of posts regarding Ryzen (in)stability issues, and none of them seem especially relevant anymore (newer kernels are available), what should I do with this information? Is this a bug? Is there an Ubuntu webpage for Ryzen APU issues? Could this have been an issue with the motherboard+CPU combination and not Ubuntu?
boot grub2 amd-processor
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
add a comment |
up vote
0
down vote
favorite
I had been fighting with boot stability for my Ryzen 2400G desktop, initially because of buggy BIOS from ASRock, but then afterwards because of what I consider a subtle issue. After installing 18.04 and 18.10 with the same results, the system would rarely boot reliably (but would on occasion), I figured out that I needed to add a boot flag,
iommu=soft
to /etc/default/grub. This webpage from Majaro clued me in,
https://forum.manjaro.org/t/amd-ryzen-problems-and-fixes/55533
I have not found any information like this on Ask Ubuntu, but maybe I'm wrong. Considering there are TONS of posts regarding Ryzen (in)stability issues, and none of them seem especially relevant anymore (newer kernels are available), what should I do with this information? Is this a bug? Is there an Ubuntu webpage for Ryzen APU issues? Could this have been an issue with the motherboard+CPU combination and not Ubuntu?
boot grub2 amd-processor
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I had been fighting with boot stability for my Ryzen 2400G desktop, initially because of buggy BIOS from ASRock, but then afterwards because of what I consider a subtle issue. After installing 18.04 and 18.10 with the same results, the system would rarely boot reliably (but would on occasion), I figured out that I needed to add a boot flag,
iommu=soft
to /etc/default/grub. This webpage from Majaro clued me in,
https://forum.manjaro.org/t/amd-ryzen-problems-and-fixes/55533
I have not found any information like this on Ask Ubuntu, but maybe I'm wrong. Considering there are TONS of posts regarding Ryzen (in)stability issues, and none of them seem especially relevant anymore (newer kernels are available), what should I do with this information? Is this a bug? Is there an Ubuntu webpage for Ryzen APU issues? Could this have been an issue with the motherboard+CPU combination and not Ubuntu?
boot grub2 amd-processor
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
I had been fighting with boot stability for my Ryzen 2400G desktop, initially because of buggy BIOS from ASRock, but then afterwards because of what I consider a subtle issue. After installing 18.04 and 18.10 with the same results, the system would rarely boot reliably (but would on occasion), I figured out that I needed to add a boot flag,
iommu=soft
to /etc/default/grub. This webpage from Majaro clued me in,
https://forum.manjaro.org/t/amd-ryzen-problems-and-fixes/55533
I have not found any information like this on Ask Ubuntu, but maybe I'm wrong. Considering there are TONS of posts regarding Ryzen (in)stability issues, and none of them seem especially relevant anymore (newer kernels are available), what should I do with this information? Is this a bug? Is there an Ubuntu webpage for Ryzen APU issues? Could this have been an issue with the motherboard+CPU combination and not Ubuntu?
boot grub2 amd-processor
boot grub2 amd-processor
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
asked Nov 27 at 1:30
Nasser Mohieddin Abukhdeir
1
1
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44
add a comment |
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1096344%2fhow-to-report-a-hardware-specific-issue-with-ubuntu-stability%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
First, and most importantly, complain to the manufacturer and complain to the shop that sold it to you. You paid them (a lot of) your hard-earned money, and received lousy-or-defective hardware in exchange. If folks keep buying their (defective) systems, then why should they bother to fix the problem? Convince the shop to stop stocking broken systems, and then perhaps the manufacturer will fix their product. Second, and least important, file a bug report against the 'linux' package using these instructions (warning: it's NOT fast or easy!)
– user535733
Nov 27 at 2:44