search for: _sta

...booted correctly into the installer after the reset button was pressed. Error dump from dmesg: Evaluate _OSC Set fails. Status = 0x0005 ACPI-1133: *** Error: Method execution failed [\_SB_.LSTA] (Node f7f5ff00), AE_AML_OPERAND_TYPE ACPI-1133: *** Error: Method execution failed [\_SB_.LATA._STA] (Node f7f001e0), AE_AML_OPERAND_TYPE ACPI-0158: *** Error: Method execution failed [\_SB_.LATA._STA] (Node f7f001e0), AE_AML_OPERAND_TYPE pciehp: Both _OSC and OSHP methods do not exist Evaluate _OSC Set fails. Status = 0x0005 ACPI-1133: *** Error: Method execution failed [\_SB_.LSTA] (Nod...

...der laptops or with the > > pcie_pm_port=off kernel option) > > > > Since 4.8, _DSM is not called anymore by nouveau (when support from the PCI > > core is detected) and this sequence should instead happen: > > - \_SB.PCI0.RP05.PEGP._PS3 (does nothing besides updating _STA) > > - PCIe core removes power for the PCIe port since all its children are in > > D3 and are willing to transition to D3cold. It does so by invoking > > \NVP3._OFF (where \NVP3 is the power resource from \_SB.PCI0.RP05._PR3) > > > > That is how I think it should...

...cold (note, this method is still used in 4.8 on older laptops or with the pcie_pm_port=off kernel option) Since 4.8, _DSM is not called anymore by nouveau (when support from the PCI core is detected) and this sequence should instead happen: - \_SB.PCI0.RP05.PEGP._PS3 (does nothing besides updating _STA) - PCIe core removes power for the PCIe port since all its children are in D3 and are willing to transition to D3cold. It does so by invoking \NVP3._OFF (where \NVP3 is the power resource from \_SB.PCI0.RP05._PR3) That is how I think it should work in theory, but on Ricks laptop running 4.8.4,...

...gt; > > pcie_pm_port=off kernel option) > > > > > > Since 4.8, _DSM is not called anymore by nouveau (when support from the PCI > > > core is detected) and this sequence should instead happen: > > > - \_SB.PCI0.RP05.PEGP._PS3 (does nothing besides updating _STA) > > > - PCIe core removes power for the PCIe port since all its children are in > > > D3 and are willing to transition to D3cold. It does so by invoking > > > \NVP3._OFF (where \NVP3 is the power resource from \_SB.PCI0.RP05._PR3) > > > > > > That...

...s still used in 4.8 on older laptops or with the > pcie_pm_port=off kernel option) > > Since 4.8, _DSM is not called anymore by nouveau (when support from the PCI > core is detected) and this sequence should instead happen: > - \_SB.PCI0.RP05.PEGP._PS3 (does nothing besides updating _STA) > - PCIe core removes power for the PCIe port since all its children are in > D3 and are willing to transition to D3cold. It does so by invoking > \NVP3._OFF (where \NVP3 is the power resource from \_SB.PCI0.RP05._PR3) > > That is how I think it should work in theory, but on Ri...

...diff -r df7cec2c6c03 tools/firmware/hvmloader/acpi/mk_dsdt.c --- a/tools/firmware/hvmloader/acpi/mk_dsdt.c Tue Nov 29 13:30:39 2011 -0500 +++ b/tools/firmware/hvmloader/acpi/mk_dsdt.c Wed Nov 30 15:08:20 2011 +0800 @@ -323,8 +323,6 @@ * the ACPI event: * _EJ0: eject a device * _STA: return a device''s status, e.g. enabled or removed - * Other methods are optional: - * _PS0/3: put them here for debug purpose * * Eject button would generate a general-purpose event, then the * control method for this event uses Notify() to inform OSPM which @...

...d3cold disabled, I noticed that I run > into the exact same error. Does this mean that you disabled d3cold on the GPU via sysfs (the "d3cold_allowed" attribute was 0) and the original problem still occurred in that configuration? > And I verified that the > \_SB.PCI0.PEG0.PG00._STA returns 1, which indicates it should still be > turned on. I don't really understand this comment, so can you explain it a bit to me, please?

...er State 0 { Debug = "_PS0" } Method (_PS3, 0, NotSerialized) // _PS3: Power State 3 { Debug = "_PS3" } } PowerResource (NVP3, 0x00, 0x0000) { Name (_STA, One) // _STA: Status Method (_ON, 0, NotSerialized) // _ON_: Power On { Debug = "NVP3._ON" _STA = One } Method (_OFF, 0, NotSerialized) // _OFF: Power Off { Debug = "NVP3...

On Fri, Oct 28, 2016 at 11:56:30AM +0300, Mika Westerberg wrote: > On Thu, Oct 27, 2016 at 06:06:48PM +0200, Peter Wu wrote: > > On Thu, Oct 27, 2016 at 12:55:08PM +0300, Mika Westerberg wrote: > > > On Thu, Oct 27, 2016 at 09:42:28AM +0000, Rick Kerkhof wrote: > > > > No, there are not. Here is the recursive directory listing: > > > > > > Are

I can confirm what Peter said, path contains \_SB_.PCI0.RP05 and power_state contains D3hot. Op do 27 okt. 2016 11:06 schreef Peter Wu <peter at lekensteyn.nl>: > On Thu, Oct 27, 2016 at 11:17:48AM +0300, Mika Westerberg wrote: > > On Thu, Oct 27, 2016 at 12:56:41AM +0200, Peter Wu wrote: > > > Hi PCI/ACPI PM experts, > > > > > &gt...

These patch update Windows generation ID support on ACPI. First patch mainly update to new specifications while second one introduce again the device in ACPI table. Frediano Ziglio (2): genid: Update Windows generation ID genid: Introduce again Windows generation ID device docs/misc/xenstore-paths.markdown | 6 ++++ tools/firmware/hvmloader/acpi/build.c | 49

...ot.so.0(io_loop_handler_run+0x4c) [0x7f65 99dafb7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f6599dafce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f659 9d300d3] -> dovecot/imap(main+0x325) [0x5654c07cabf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f6599b1b09b] -> dovecot/imap(_sta rt+0x2a) [0x5654c07cad8a] -- K -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200825/7c4713fd/attachment.html>

Hi there, Is there a way to prevent Windows HVM guests from seeing passed through devices like graphics cards as being ejectable? i.e. you pass through a graphics adapter to an HVM guest which happens to be Windows. Windows sees this as a device with hotplug capability. Therefore it shows up in "safely remove hardware" option in the windows system tray. VMWare provides an option to

...its invocation which unfortunately are not known to > > > > > > > > us. > > > > > > > > > > > > > > > > However, it looks like the AML invoked to power down the GPU from > > > > > > > > acpi_pci_set_power_state() gets confused if it is not in PCI D0 at > > > > > > > > that point, so it looks like that AML tries to access device memory on > > > > > > > > the GPU (beyond the PCI config space) or similar which is not > > > > > > > > ac...

so while trying to test with d3cold disabled, I noticed that I run into the exact same error. And I verified that the \_SB.PCI0.PEG0.PG00._STA returns 1, which indicates it should still be turned on. On Thu, Nov 21, 2019 at 11:50 PM Karol Herbst <kherbst at redhat.com> wrote: > > On Thu, Nov 21, 2019 at 11:39 PM Rafael J. Wysocki <rafael at kernel.org> wrote: > > > > On Thu, Nov 21, 2019 at 8:49 PM Mika West...

....y..RTLA.IRQ 1aa0: 30 70 00 49 52 51 30 79 01 7b 50 41 52 43 0a 0f 0p.IRQ0y.{PARC.. 1ab0: 00 49 52 51 30 a4 52 54 4c 41 14 1b 5f 53 52 53 .IRQ0.RTLA.._SRS 1ac0: 09 8b 68 01 49 52 51 30 82 49 52 51 30 60 76 60 ..h.IRQ0.IRQ0`v` 1ad0: 70 60 50 41 52 43 14 18 5f 53 54 41 08 a0 0c 7b p`PARC.._STA...{ 1ae0: 50 41 52 43 0a 80 00 a4 0a 09 a1 04 a4 0a 0b 5b PARC...........[ 1af0: 82 43 0a 4c 4e 4b 42 08 5f 48 49 44 0c 41 d0 0c .C.LNKB._HID.A.. 1b00: 0f 08 5f 55 49 44 0a 02 14 11 5f 44 49 53 08 7d .._UID...._DIS.} 1b10: 50 42 52 43 0a 80 50 42 52 43 14 0b 5f 50 52 53 PBRC..PBRC.._PRS...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I have had a problem detecting the network card on my notebook when ACPI is enabled for a year. The problem still exists in 7.1-RELEASE. with ACPI: ... bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002> irq 17 at device 0.0 on pci8 bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). bge0: couldn't

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must