ACPI error preventing boot after kernel updateACPI problem with recent kernelsCorrupt LVM metadata header...
Interpretation of non-significant results as "trends"
Why is a semiprime used as the modulus in RSA?
This LM317 diagram doesn't make any sense to me
What does "spinning upon the shoals" mean?
Category-theoretic treatment of diffs, patches and merging?
Is "wissen" the only verb in German to have an irregular present tense?
QR codes, do people use them?
What factors could lead to bishops establishing monastic armies?
Why is a mixture of two normally distributed variables only bimodal if their means differ by at least two times the common standard deviation?
Write a function
Gory anime with pink haired girl escaping an asylum
Clarinets in the Rite of Spring
How many Jimmys can fit?
My previous employer committed a severe violation of the law and is also being sued by me. How do I explain the situation to future employers?
Matrices with shadows
How to use Adostop Eco stop bath?
How to understand flavors and when to use combination of them?
How do I explain that I don't want to maintain old projects?
I'm feeling like my character doesn't fit the campaign
What was the significance of Spider-Man: Far From Home being an MCU Phase 3 film instead of a Phase 4 film?
Is it ok for parents to kiss and romance with each other while their 2- to 8-year-old child watches?
Is there a formal/better word than "skyrocket" for the given context?
Who goes first? Person disembarking bus or the bicycle?
Findminimum of Integral
ACPI error preventing boot after kernel update
ACPI problem with recent kernelsCorrupt LVM metadata header after kernel updateLinux Mint: ACPI PCC probe and usb descriptor errors during bootMay ACPI wakeup states be modified from the kernel?ACPI kernel parameter options for HP ProLiant DL380 G5Working acpi kernel options for Asus FX503VD?Find correct ACPI drivers without trial-and-error`acpi=off` results in `BUG: unable to handle kernel NULL pointer dereference`Kernel panics only with ACPI enabledACPI error message AE_NOT_FOUND. Why is this happening now? It did not happen previously
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
not certain if this is a generic Linux query or an Ubuntu query, but here goes.
I have a Z800 workstation, which was running Xubuntu 18.04, with kernel 4.15 . It's a dual processor machine. It has the latest BIOS available for this machine ( 3.61, from some time last year ).
I just applied a batch of updates. Now my machine will not boot. The error is :
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dsfield-212)
ACPI Error: Method parse/execution failed _SB.PCIO._OSC, AE_ALREADY_EXISTS (20170831/psparse-550)
I have read https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips, and
https://askubuntu.com/questions/1093882/unable-to-boot-after-installation-acpi-errors, and many other things, and am suitably horrified by the mess that is ACPI, but would still really like my machine to work again.
I have tried many combinations of kernel parameters. Using 'acpi=off' results in a kernel panic. All the other variations I have tried of the many acpi related options ( including acpi=ht, and specifying the acpi_serialize option ) gives the same result as given above.
This occurs no matter which 4.15 kernel I try to start, not just the latest one. I have several historical 4.15 kernels, one of which I was using prior to this update, and yet now they all give this error. I also have an ancient 4.4 kernel, which does not give this error, but hangs before starting my desktop - but that's no great surpise.
I would love to be able to revert the BIOS just to see what effect that had, but the HP site doesn't seem to list historical versions.
So I think what I don't understand is what can an update change which would affect the ACPI behaviour of any 4.15 kernel, including those that previously worked ? If there's some other list that would be more suitable for this query, feel free to redirect me.
linux-kernel acpi
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
not certain if this is a generic Linux query or an Ubuntu query, but here goes.
I have a Z800 workstation, which was running Xubuntu 18.04, with kernel 4.15 . It's a dual processor machine. It has the latest BIOS available for this machine ( 3.61, from some time last year ).
I just applied a batch of updates. Now my machine will not boot. The error is :
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dsfield-212)
ACPI Error: Method parse/execution failed _SB.PCIO._OSC, AE_ALREADY_EXISTS (20170831/psparse-550)
I have read https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips, and
https://askubuntu.com/questions/1093882/unable-to-boot-after-installation-acpi-errors, and many other things, and am suitably horrified by the mess that is ACPI, but would still really like my machine to work again.
I have tried many combinations of kernel parameters. Using 'acpi=off' results in a kernel panic. All the other variations I have tried of the many acpi related options ( including acpi=ht, and specifying the acpi_serialize option ) gives the same result as given above.
This occurs no matter which 4.15 kernel I try to start, not just the latest one. I have several historical 4.15 kernels, one of which I was using prior to this update, and yet now they all give this error. I also have an ancient 4.4 kernel, which does not give this error, but hangs before starting my desktop - but that's no great surpise.
I would love to be able to revert the BIOS just to see what effect that had, but the HP site doesn't seem to list historical versions.
So I think what I don't understand is what can an update change which would affect the ACPI behaviour of any 4.15 kernel, including those that previously worked ? If there's some other list that would be more suitable for this query, feel free to redirect me.
linux-kernel acpi
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
not certain if this is a generic Linux query or an Ubuntu query, but here goes.
I have a Z800 workstation, which was running Xubuntu 18.04, with kernel 4.15 . It's a dual processor machine. It has the latest BIOS available for this machine ( 3.61, from some time last year ).
I just applied a batch of updates. Now my machine will not boot. The error is :
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dsfield-212)
ACPI Error: Method parse/execution failed _SB.PCIO._OSC, AE_ALREADY_EXISTS (20170831/psparse-550)
I have read https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips, and
https://askubuntu.com/questions/1093882/unable-to-boot-after-installation-acpi-errors, and many other things, and am suitably horrified by the mess that is ACPI, but would still really like my machine to work again.
I have tried many combinations of kernel parameters. Using 'acpi=off' results in a kernel panic. All the other variations I have tried of the many acpi related options ( including acpi=ht, and specifying the acpi_serialize option ) gives the same result as given above.
This occurs no matter which 4.15 kernel I try to start, not just the latest one. I have several historical 4.15 kernels, one of which I was using prior to this update, and yet now they all give this error. I also have an ancient 4.4 kernel, which does not give this error, but hangs before starting my desktop - but that's no great surpise.
I would love to be able to revert the BIOS just to see what effect that had, but the HP site doesn't seem to list historical versions.
So I think what I don't understand is what can an update change which would affect the ACPI behaviour of any 4.15 kernel, including those that previously worked ? If there's some other list that would be more suitable for this query, feel free to redirect me.
linux-kernel acpi
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
not certain if this is a generic Linux query or an Ubuntu query, but here goes.
I have a Z800 workstation, which was running Xubuntu 18.04, with kernel 4.15 . It's a dual processor machine. It has the latest BIOS available for this machine ( 3.61, from some time last year ).
I just applied a batch of updates. Now my machine will not boot. The error is :
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dsfield-212)
ACPI Error: Method parse/execution failed _SB.PCIO._OSC, AE_ALREADY_EXISTS (20170831/psparse-550)
I have read https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips, and
https://askubuntu.com/questions/1093882/unable-to-boot-after-installation-acpi-errors, and many other things, and am suitably horrified by the mess that is ACPI, but would still really like my machine to work again.
I have tried many combinations of kernel parameters. Using 'acpi=off' results in a kernel panic. All the other variations I have tried of the many acpi related options ( including acpi=ht, and specifying the acpi_serialize option ) gives the same result as given above.
This occurs no matter which 4.15 kernel I try to start, not just the latest one. I have several historical 4.15 kernels, one of which I was using prior to this update, and yet now they all give this error. I also have an ancient 4.4 kernel, which does not give this error, but hangs before starting my desktop - but that's no great surpise.
I would love to be able to revert the BIOS just to see what effect that had, but the HP site doesn't seem to list historical versions.
So I think what I don't understand is what can an update change which would affect the ACPI behaviour of any 4.15 kernel, including those that previously worked ? If there's some other list that would be more suitable for this query, feel free to redirect me.
linux-kernel acpi
linux-kernel acpi
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 8 mins ago
mderoussmderouss
1
1
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
mderouss is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
mderouss is a new contributor. Be nice, and check out our Code of Conduct.
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%2f528743%2facpi-error-preventing-boot-after-kernel-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
mderouss is a new contributor. Be nice, and check out our Code of Conduct.
mderouss is a new contributor. Be nice, and check out our Code of Conduct.
mderouss is a new contributor. Be nice, and check out our Code of Conduct.
mderouss is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2f528743%2facpi-error-preventing-boot-after-kernel-update%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