skullnobrains
asked on
Boot ko after _osi bios call
boot ko after bios _osi linux query ignored.
Hello all
I have a system that will not boot and just hang after the above message ( see attached photograph ) from an old ubuntu 14
I am pretty sure the issue is hardware since the os has multiple bootable oses and all of them hang somewhere after an acpi message. Tested with multiple linux and freebsd kernels. Not tested windows yet.
... and the laptop fell yesterday. It did work for s few hours normally afterwards and was cleanly shutdown without issues
My questions are
Do you happen to know what is the next step in the boot sequence ? I suspect loading graphic drivers but i am unsure and a dmesg output would help.
Do you happen to know some options i can pass the kernel in order to circumvent and go on with my work till i fix this ? I tried various combinations of noapic noacpi vga... i would be more than happy with a working command line and a vesa screen
Thanks for your time
IMG_20200221_081832.jpg
Hello all
I have a system that will not boot and just hang after the above message ( see attached photograph ) from an old ubuntu 14
I am pretty sure the issue is hardware since the os has multiple bootable oses and all of them hang somewhere after an acpi message. Tested with multiple linux and freebsd kernels. Not tested windows yet.
... and the laptop fell yesterday. It did work for s few hours normally afterwards and was cleanly shutdown without issues
My questions are
Do you happen to know what is the next step in the boot sequence ? I suspect loading graphic drivers but i am unsure and a dmesg output would help.
Do you happen to know some options i can pass the kernel in order to circumvent and go on with my work till i fix this ? I tried various combinations of noapic noacpi vga... i would be more than happy with a working command line and a vesa screen
Thanks for your time
IMG_20200221_081832.jpg
ASKER
update now i got most of my real life work done :
i managed to boot the same os by feeding the whole drive to qemu which confirms the bug is somehow hardware related. unfortunately i did not manage to get the serial console or curses interface to work in windows and this is painfully slow.
i managed to get something more or less usable by booting in single user mode but for some reason the keyboard only works sporadically. i tried dmesg but the bochs bios builtin qemu is quite different from mine so i'm unsure about the boot process order.
i managed to install refind. it is painfully slow but manages to boot windows. it does detect linux but the system reboots if i select any of the linux kernels. i'm unsure they are efi compatible...
not sure where to go from here : maybe reinstall a new system using EFI and throw away most of the old ones i hardly need anymore anyway. got to resume my work so that will be for another time.
either i manage to debug what miraculously broke, or i'll probably install trueos or a barbone bsd somewhere and bhyve into cmos based systems if i need to. i have not checked all i could but tried various working install cds in cms mode and for some reason, nothing manages to boot. but efis do work... ^^
if anyone figures that one out, i'm quite interested into how a system can half break like that. ( i'm currently using that same computer as i write ). the linux is booted in qemu and works slowly but fine.
i managed to boot the same os by feeding the whole drive to qemu which confirms the bug is somehow hardware related. unfortunately i did not manage to get the serial console or curses interface to work in windows and this is painfully slow.
i managed to get something more or less usable by booting in single user mode but for some reason the keyboard only works sporadically. i tried dmesg but the bochs bios builtin qemu is quite different from mine so i'm unsure about the boot process order.
i managed to install refind. it is painfully slow but manages to boot windows. it does detect linux but the system reboots if i select any of the linux kernels. i'm unsure they are efi compatible...
not sure where to go from here : maybe reinstall a new system using EFI and throw away most of the old ones i hardly need anymore anyway. got to resume my work so that will be for another time.
either i manage to debug what miraculously broke, or i'll probably install trueos or a barbone bsd somewhere and bhyve into cmos based systems if i need to. i have not checked all i could but tried various working install cds in cms mode and for some reason, nothing manages to boot. but efis do work... ^^
if anyone figures that one out, i'm quite interested into how a system can half break like that. ( i'm currently using that same computer as i write ). the linux is booted in qemu and works slowly but fine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i tried acpi=linux this morning without success after stumbling on a similar thread
this is quite weird since the described bug is software related, and i'm pretty sure i tried about a dozen kernels from multiple oses that previously worked and i have not updated any of them, much less my bios... ^^
i'll try that when i get a chance but that requires rebooting, mingling with the bios to switch back to cms boot... and i'm kinda working at the same time so i cannot afford to reboot.
and since i am the luckiest guy in the world, my internet broke this morning due to construction work for a bike lane in front of my building so i'm using neighbors wifis with whom we share manual redundancy since we use different providers and technologies... which are only available in my laptop since none of my desktops have a wifi card. ...
sorry for the useless complaints but i really feel like someone does not like me today... and thanks a lot for the help. you're definitely one of the guys i like to see chipping in.
this is quite weird since the described bug is software related, and i'm pretty sure i tried about a dozen kernels from multiple oses that previously worked and i have not updated any of them, much less my bios... ^^
i'll try that when i get a chance but that requires rebooting, mingling with the bios to switch back to cms boot... and i'm kinda working at the same time so i cannot afford to reboot.
and since i am the luckiest guy in the world, my internet broke this morning due to construction work for a bike lane in front of my building so i'm using neighbors wifis with whom we share manual redundancy since we use different providers and technologies... which are only available in my laptop since none of my desktops have a wifi card. ...
sorry for the useless complaints but i really feel like someone does not like me today... and thanks a lot for the help. you're definitely one of the guys i like to see chipping in.
It seems to be a "firmware" error... so debatable if it is hardware / software.
There is a call to allow kernel "wakeup" after hibernation from the BIOS, which seems to be "not used correctly" by firmware builders.
Gentoo forums may help occasionally: https://forums.gentoo.org/viewtopic-t-1065164.html
Although that issue has more to do with Too many invalid kernel config items.
(Does yours continue after minutes of waiting?)
This ubuntu forum gives a few more details. https://askubuntu.com/questions/175793/what-does-the-following-dmesg-output-means
ASKER
It continues to a blank grayish screen after a few minutes. i waited about 10 more minutes to no avail.
Secondary consoles are not available at that time yet so there is hardly any debug possibilities. Perhaps with a serial cable... i might try this we.
What is totally crazy is the same kernel and setup worked a few hours before.
My best guess is the boot microcode of some device broke. And that code would be involved in cms boot only.
Currently, i don t really believe the error is even relevant. I think the boot breaks on the step that comes immediately after which i think is probably the graphic card switching from vesa to whatever other mode. But if your trick works, that would proove this assumption wrong. Guess we will know in a few hours.
Once booted through efi, everything seems to work normally but i have not tested every single device so i cannot say for sure.
thanks again for the input
Secondary consoles are not available at that time yet so there is hardly any debug possibilities. Perhaps with a serial cable... i might try this we.
What is totally crazy is the same kernel and setup worked a few hours before.
My best guess is the boot microcode of some device broke. And that code would be involved in cms boot only.
Currently, i don t really believe the error is even relevant. I think the boot breaks on the step that comes immediately after which i think is probably the graphic card switching from vesa to whatever other mode. But if your trick works, that would proove this assumption wrong. Guess we will know in a few hours.
Once booted through efi, everything seems to work normally but i have not tested every single device so i cannot say for sure.
thanks again for the input
i agree with your assessment there is some other (hidden) error later on.
Did you try to boot from some bootable CD/DVD/USB, with different kernels just to see if those might give some more helpful message?
Did you check that the filesystem on your system is still usable? (can be done from CD/DVD as well).
Some grub setups have some "safety boot" as an alternative menu, either providing more data or limiting device support.
ASKER
I did. Every single kernel i booted failed when using cms and succeeded when using efi.
I successfully booted the very same os in qemu so i am shure the filesystem is ok, and the failure occurs way before the rootfs is mounted so i am positive this is totally unrelated with the drive.
I successfully booted the very same os in qemu so i am shure the filesystem is ok, and the failure occurs way before the rootfs is mounted so i am positive this is totally unrelated with the drive.
ASKER
hi @noci, here is some more feedback :
this morning, windows would not boot. don't know why, don't care either, and i'm pretty sure this is totally an unrelated software m$ bug which i probably won't bother debugging.
now the intersting part : i was able to boot successfully with acpi_osi=Linux. and confirmed i still could not vboot without the option. both multiple times.
then i played a little with the bios looking for some weird options related to os compatibility or acpi. turns out this bios is very limited and does not feature any of these. at some point i switched from the graphic card to "internal graphics"... and was able to boot without adding the acpi_whatever option. i reverted back to the graphic card, and i can now boot without the option exactly as before.
as a side note, i noticed the battery which was kinda dying miraculously reported being able to hold for hours while it previously acurately reported about 12 minutes at full charge. not sure whether the report was wrong or something in the microcode miraculously ( and temporarily ) fixed itself.
... so basically i am back to normal without making a single change.
the best i can figure out from this voodoo stuff is that i probably damaged the nvram somewhere near acpi, or possibly the hardware features handling sleep and hibernation ( which had been working quite erradically after an accidental rain a few years ago ) ... and somehow either the chip started working more or less properly after a number of heat and cold, or more likely changing bios settings rewrote the nvram and accidentally corrected whatever was broken.
for reference, here is a little part of the current dmesg
[ 0.335215] cpuidle: using governor ladder
[ 0.335291] cpuidle: using governor menu
[ 0.335431] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.335541] ACPI: bus type PCI registered
[ 0.335616] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.336865] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.336983] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.348702] PCI: Using configuration type 1 for base access
[ 0.351743] bio: create slab <bio-0> at 0
[ 0.352212] ACPI: Added _OSI(Module Device)
[ 0.352289] ACPI: Added _OSI(Processor Device)
[ 0.352365] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.352441] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.357928] ACPI : EC: EC description table is found, configuring boot EC
[ 0.372943] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.393291] ACPI: SSDT 00000000bce2d918 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.394847] ACPI: Dynamic OEM Table Load:
[ 0.394991] ACPI: SSDT (null) 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.397648] ACPI: SSDT 00000000bce2e618 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
[ 0.399403] ACPI: Dynamic OEM Table Load:
[ 0.399547] ACPI: SSDT (null) 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
[ 0.401223] ACPI: SSDT 00000000bce2fc18 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
[ 0.402765] ACPI: Dynamic OEM Table Load:
[ 0.402909] ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
[ 0.408368] ACPI: Interpreter enabled
[ 0.408456] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
[ 0.408653] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
[ 0.408872] ACPI: (supports S0 S3 S4 S5)
[ 0.408946] ACPI: Using IOAPIC for interrupt routing
[ 0.409092] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.409600] ACPI: No dock devices found.
[ 0.419037] ACPI: Power Resource [PUBS] (on)
[ 0.437388] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.437964] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.438674] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11)
[ 0.439283] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 9 10 11)
[ 0.439849] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.440507] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.441228] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 *6 7 9 10 11)
[ 0.441838] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11)
[ 0.442381] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[ 0.442471] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.442471] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.442855] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
[ 0.443061] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.443180] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
[ 0.443293] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[ 0.443404] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.444029] PCI host bridge to bus 0000:00
[ 0.444108] pci_bus 0000:00: root bus resource [bus 00-3f]
[ 0.444190] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.444273] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.444355] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.444441] pci_bus 0000:00: root bus resource [mem 0xbfa00000-0xfebfffff]
[ 0.444544] pci 0000:00:00.0: [8086:0c04] type 00 class 0x060000
[ 0.444808] pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400
[ 0.444899] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.445125] pci 0000:00:02.0: [8086:0416] type 00 class 0x030000
[ 0.445166] pci 0000:00:02.0: reg 0x10: [mem 0xf1000000-0xf13fffff 64bit]
[ 0.445185] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.445199] pci 0000:00:02.0: reg 0x20: [io 0x6000-0x603f]
[ 0.445452] pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
[ 0.445475] pci 0000:00:03.0: reg 0x10: [mem 0xf2610000-0xf2613fff 64bit]
[ 0.445787] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
[ 0.445837] pci 0000:00:14.0: reg 0x10: [mem 0xf2600000-0xf260ffff 64bit]
[ 0.445994] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.446144] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.446302] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
this morning, windows would not boot. don't know why, don't care either, and i'm pretty sure this is totally an unrelated software m$ bug which i probably won't bother debugging.
now the intersting part : i was able to boot successfully with acpi_osi=Linux. and confirmed i still could not vboot without the option. both multiple times.
then i played a little with the bios looking for some weird options related to os compatibility or acpi. turns out this bios is very limited and does not feature any of these. at some point i switched from the graphic card to "internal graphics"... and was able to boot without adding the acpi_whatever option. i reverted back to the graphic card, and i can now boot without the option exactly as before.
as a side note, i noticed the battery which was kinda dying miraculously reported being able to hold for hours while it previously acurately reported about 12 minutes at full charge. not sure whether the report was wrong or something in the microcode miraculously ( and temporarily ) fixed itself.
... so basically i am back to normal without making a single change.
the best i can figure out from this voodoo stuff is that i probably damaged the nvram somewhere near acpi, or possibly the hardware features handling sleep and hibernation ( which had been working quite erradically after an accidental rain a few years ago ) ... and somehow either the chip started working more or less properly after a number of heat and cold, or more likely changing bios settings rewrote the nvram and accidentally corrected whatever was broken.
for reference, here is a little part of the current dmesg
[ 0.335215] cpuidle: using governor ladder
[ 0.335291] cpuidle: using governor menu
[ 0.335431] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.335541] ACPI: bus type PCI registered
[ 0.335616] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.336865] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.336983] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.348702] PCI: Using configuration type 1 for base access
[ 0.351743] bio: create slab <bio-0> at 0
[ 0.352212] ACPI: Added _OSI(Module Device)
[ 0.352289] ACPI: Added _OSI(Processor Device)
[ 0.352365] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.352441] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.357928] ACPI : EC: EC description table is found, configuring boot EC
[ 0.372943] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.393291] ACPI: SSDT 00000000bce2d918 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.394847] ACPI: Dynamic OEM Table Load:
[ 0.394991] ACPI: SSDT (null) 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.397648] ACPI: SSDT 00000000bce2e618 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
[ 0.399403] ACPI: Dynamic OEM Table Load:
[ 0.399547] ACPI: SSDT (null) 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
[ 0.401223] ACPI: SSDT 00000000bce2fc18 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
[ 0.402765] ACPI: Dynamic OEM Table Load:
[ 0.402909] ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20120711)
[ 0.408368] ACPI: Interpreter enabled
[ 0.408456] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
[ 0.408653] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
[ 0.408872] ACPI: (supports S0 S3 S4 S5)
[ 0.408946] ACPI: Using IOAPIC for interrupt routing
[ 0.409092] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.409600] ACPI: No dock devices found.
[ 0.419037] ACPI: Power Resource [PUBS] (on)
[ 0.437388] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[ 0.437964] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.438674] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11)
[ 0.439283] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 9 10 11)
[ 0.439849] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.440507] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 0.441228] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 *6 7 9 10 11)
[ 0.441838] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11)
[ 0.442381] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[ 0.442471] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.442471] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.442855] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
[ 0.443061] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.443180] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
[ 0.443293] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[ 0.443404] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.444029] PCI host bridge to bus 0000:00
[ 0.444108] pci_bus 0000:00: root bus resource [bus 00-3f]
[ 0.444190] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.444273] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.444355] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.444441] pci_bus 0000:00: root bus resource [mem 0xbfa00000-0xfebfffff]
[ 0.444544] pci 0000:00:00.0: [8086:0c04] type 00 class 0x060000
[ 0.444808] pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400
[ 0.444899] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.445125] pci 0000:00:02.0: [8086:0416] type 00 class 0x030000
[ 0.445166] pci 0000:00:02.0: reg 0x10: [mem 0xf1000000-0xf13fffff 64bit]
[ 0.445185] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.445199] pci 0000:00:02.0: reg 0x20: [io 0x6000-0x603f]
[ 0.445452] pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
[ 0.445475] pci 0000:00:03.0: reg 0x10: [mem 0xf2610000-0xf2613fff 64bit]
[ 0.445787] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
[ 0.445837] pci 0000:00:14.0: reg 0x10: [mem 0xf2600000-0xf260ffff 64bit]
[ 0.445994] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.446144] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.446302] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
Surprisingly the error also shows in windows... (see this site... dodgy link so i don't reccomend downloading stuff there).. https://www.fileerrors.com/boot-problem-stops-boot-at-acpi-ec-ec-description-table-is-found-configuring-boot-ec.html
Looking at my own systems: (kernel: 4.19.97)
(they boot from EFI),
and BIOS:
EC driver source is: in linux serources: ..../driver/acpi/ec.c / embedded controller: https://en.wikipedia.org/wiki/Embedded_controller
which is more or less in the centre of the action.... (or lack of it).
Looking at my own systems: (kernel: 4.19.97)
[ 0.390894] ACPI: bus type PCI registered
[ 0.496059] ACPI: Added _OSI(Module Device)
[ 0.496059] ACPI: Added _OSI(Processor Device)
[ 0.496059] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.496059] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.496106] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.496187] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.501918] ACPI: 2 ACPI AML tables successfully acquired and loaded
[ 0.542190] ACPI: Interpreter enabled
[ 0.543714] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.543795] ACPI: Using IOAPIC for interrupt routing
[ 0.544956] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.545119] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.545502] ACPI: Enabled 11 GPEs in block 00 to 1F
[ 0.545588] ACPI: Enabled 1 GPEs in block 20 to 5F
[ 0.555690] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.555690] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.555842] acpi PNP0A03:00: _OSC: platform does not support [PCIeCapability LTR]
[ 0.556004] acpi PNP0A03:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.556145] acpi PNP0A03:00: _OSC: OS requested [PME AER PCIeCapability LTR]
[ 0.556232] acpi PNP0A03:00: _OSC: platform willing to grant [PME AER]
[ 0.556318] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.556489] acpi PNP0A03:00: ignoring host bridge window [mem 0x000d0000-0x000dffff window] (conflicts with Adapter ROM [mem 0x000cd800-0x000d0dff])
[ 0.569704] ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *10
[ 1.594293] ACPI: AC Adapter [ACAD] (on-line)
[ 1.594464] ACPI: Power Button [PWRB]
[ 1.594613] ACPI: Sleep Button [SLPB]
[ 1.594753] ACPI: Lid Switch [LID]
[ 1.594893] ACPI: Power Button [PWRF]
[ 1.596205] ACPI: Thermal Zone [THRM] (63 C)
[ 1.597344] battery: ACPI: Battery Slot [BAT1] (battery present)
[ 1.673182] acpi_cpufreq: overriding BIOS provided _PSD data
[ 4.787732] ACPI: bus type USB registered
[ 16.922438] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[ 16.923272] acpi device:00: registered as cooling_device4
[ 16.928202] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[ 16.975025] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B0 8 conflicts with OpRegion 0x0000000000000B00-0x00000 00000000B0 F (\_SB.PCI0.SMBS.SMB0) (20180810/utaddress-204)
[ 16.975034] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
(they boot from EFI),
and BIOS:
[ 0.390894] ACPI: bus type PCI registered
[ 0.496059] ACPI: Added _OSI(Module Device)
[ 0.496059] ACPI: Added _OSI(Processor Device)
[ 0.496059] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.496059] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.496106] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.496187] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.501918] ACPI: 2 ACPI AML tables successfully acquired and loaded
[ 0.542190] ACPI: Interpreter enabled
[ 0.543714] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.543795] ACPI: Using IOAPIC for interrupt routing
[ 0.544956] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.545119] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.545502] ACPI: Enabled 11 GPEs in block 00 to 1F
[ 0.545588] ACPI: Enabled 1 GPEs in block 20 to 5F
[ 0.555690] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.555690] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.555842] acpi PNP0A03:00: _OSC: platform does not support [PCIeCapability LTR]
[ 0.556004] acpi PNP0A03:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 0.556145] acpi PNP0A03:00: _OSC: OS requested [PME AER PCIeCapability LTR]
[ 0.556232] acpi PNP0A03:00: _OSC: platform willing to grant [PME AER]
[ 0.556318] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 0.556489] acpi PNP0A03:00: ignoring host bridge window [mem 0x000d0000-0x000dffff window] (conflicts with Adapter ROM [mem 0x000cd800-0x000d0dff])
[ 0.569704] ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *10
[ 0.569876] ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *11
EC driver source is: in linux serources: ..../driver/acpi/ec.c / embedded controller: https://en.wikipedia.org/wiki/Embedded_controller
which is more or less in the centre of the action.... (or lack of it).
I had typed this hours ago, didn't post it yet until now.
I did find other references to battery issues and Graphics issues. People switching linux native drivers vs. official nvidia drivers. (all were nvidia related).
most had something to do with lenovo.
I did find other references to battery issues and Graphics issues. People switching linux native drivers vs. official nvidia drivers. (all were nvidia related).
most had something to do with lenovo.
ASKER
thanks for all that information. i have been reading quite a lot on acpi issues, and tried various debug steps which do not shed much light.
for some reason, everything is back to normal without changing a single thing. i can boot both legacy and efi oses properly now without any other inconvenience than the same few warnings which existed beforehand and it does not hang whatever i do.
i was wrong regarding the graphic card : the next step is loading some secondary table which is apparently not related to either the battery or the graphics
[ 0.393291] ACPI: SSDT 00000000bce2d918 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.394847] ACPI: Dynamic OEM Table Load:
[ 0.394991] ACPI: SSDT (null) 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
or in your case
[ 0.501918] ACPI: 2 ACPI AML tables successfully acquired and loaded
thanks a lot for your help.
i will mark your acpi_osi comment as the solution since i guess this future users with a similar problem would want to read first
for some reason, everything is back to normal without changing a single thing. i can boot both legacy and efi oses properly now without any other inconvenience than the same few warnings which existed beforehand and it does not hang whatever i do.
i was wrong regarding the graphic card : the next step is loading some secondary table which is apparently not related to either the battery or the graphics
[ 0.393291] ACPI: SSDT 00000000bce2d918 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 0.394847] ACPI: Dynamic OEM Table Load:
[ 0.394991] ACPI: SSDT (null) 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
or in your case
[ 0.501918] ACPI: 2 ACPI AML tables successfully acquired and loaded
thanks a lot for your help.
i will mark your acpi_osi comment as the solution since i guess this future users with a similar problem would want to read first
ASKER
that only allows me to boot into windows 8 so it's pretty much a no-go but i should be able to disable safe boot and install refind or grub as soon as reasonably possible.
nevertheless i'd like to troubleshoot the legacy boot so ideas are still more than welcome