Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, Nov 13, 2018 at 7:16 PM Daniel Eischen wrote: > > On Tue, 13 Nov 2018, Conrad Meyer wrote: > > > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > >> I've attached it. If it gets filtered by the mail list, I'll > >> make it http accessible. > > > > Thanks Daniel. > > > > It looks

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote: > The 2700 has an offset of 0 though (2700X has 10). > And I'm seeing a difference of more than 30 degrees. I guess something > else must be happening here. I had thought 54 was the right offset for my 2990WX system, but now it's

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018, Conrad Meyer wrote: On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: I've attached it. If it gets filtered by the mail list, I'll make it http accessible. Thanks Daniel. It looks like your hostbridge zero device has a different device id than in my first

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

Of course, Johannes has already thought of this! See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228480 and https://reviews.freebsd.org/D15567 . On Tue, Nov 13, 2018 at 6:41 PM Conrad Meyer wrote: > > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > > I've attached it. If it gets

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

|after upgrading to |after upgrading to |12-CURRENT after r330957|12-CURRENT after r330957 |(ACPI problems) |(ACPI _STA method removed) CC||curr...@freebsd.org -- You

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > I've attached it. If it gets filtered by the mail list, I'll > make it http accessible. Thanks Daniel. It looks like your hostbridge zero device has a different device id than in my first generation Ryzen system. Would you please try the

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018, Conrad Meyer wrote: Hi Daniel, On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote: Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. Maybe

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, Nov 13, 2018 at 5:15 PM Rozhuk Ivan wrote: > > On Tue, 13 Nov 2018 19:41:47 -0500 > Daniel Eischen wrote: > > > >> I'm trying to track down a couple of things. amdtemp doesn't > > >> report any temperature sensors, and acpi seems to have some > >

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018 19:41:47 -0500 Daniel Eischen wrote: > >> I'm trying to track down a couple of things. amdtemp doesn't > >> report any temperature sensors, and acpi seems to have some > >> errors. Not sure if they are related. > > > >

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

Hi Daniel, On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote: > > Greetings, > > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. Maybe not. If

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

> On Nov 13, 2018, at 2:06 PM, Rozhuk Ivan wrote: > > On Tue, 13 Nov 2018 12:59:59 -0500 (EST) > Daniel Eischen wrote: > >> I'm trying to track down a couple of things. amdtemp doesn't >> report any temperature sensors, and acpi seems to have some >> erro

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On 11/13/18 10:14 PM, Conrad Meyer wrote: > On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote: >> After kldload amdtemp I see the following sysctls: >> dev.cpu.0.temperature: 77.1C >> dev.amdtemp.0.core0.sensor0: 77.1C >> >> The temperature I see in BIOS is much lower (maybe around 40.0C).

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

gt;> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen >>>> wrote: >>>>> Greetings, >>>>> >>>>> I'm trying to track down a couple of things. amdtemp doesn't >>>>> report any temperature sensors, and acpi seems to have some >>&

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018 13:14:46 -0800 Conrad Meyer wrote: > You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the > amdtemp sysctl gives you the unadjusted value. On different Ryzen > models the raw value is wrong by different amounts. E.g. on my 1950X, > I have sensor_offset set

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

>>> Greetings, >>>> >>>> I'm trying to track down a couple of things. amdtemp doesn't >>>> report any temperature sensors, and acpi seems to have some >>>> errors. Not sure if they are related. >>>> >>>> These are the A

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote: > After kldload amdtemp I see the following sysctls: > dev.cpu.0.temperature: 77.1C > dev.amdtemp.0.core0.sensor0: 77.1C > > The temperature I see in BIOS is much lower (maybe around 40.0C). Don't > know if just the offset is wrong or the

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On 11/13/18 8:59 PM, Daniel Eischen wrote: > On Tue, 13 Nov 2018, Greg V wrote: > >> >> >> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen >> wrote: >>> Greetings, >>> >>> I'm trying to track down a couple of things.  amdtemp doesn't &

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018, Greg V wrote: On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen wrote: Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. These are the ACPI-related

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen wrote: Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. These are the ACPI-related warnings and errors during boot

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

On Tue, 13 Nov 2018 12:59:59 -0500 (EST) Daniel Eischen wrote: > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. It s a bit legacy ) Try mine: http://www.netlab.l

No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. These are the ACPI-related warnings and errors during boot. Firmware Warning (ACPI): Optional FADT field

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

f fixes my problem too, which I posted in reply to Kyle's r337773 hint (non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection]) Machine here is DH87MC+i3-4330 (LynxPoint/Series8+haswel

non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection]

Am 15.08.2018 um 06:01 schrieb Kyle Evans: On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: On 8/14/18 8:45 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

Hello! On Tue, Aug 14, 2018, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > > > i also attempted to boot using UEFI but the system hangs very early in the > > > boot process. i have reverted to legacy mode for now so that

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

DMI is recognized according to xrandr.  so that solves my immediate problem! :)  interestingly enough i still see the ACPI errors I reported earlier, but perhaps that is a red herring. i'll go back to the tip of master and apply kib's patch and see how it goes. ok great (thank's ccache for mak

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

ves my immediate problem! :)  interestingly enough i still see the ACPI errors I reported earlier, but perhaps that is a red herring. i'll go back to the tip of master and apply kib's patch and see how it goes. -p -- Pete Wright p...@nomadlogic.org @nomadlogi

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: > > On 8/14/18 8:45 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >>> >>> On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > > i also attempted

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On 8/14/18 8:45 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >>> >>> i also attempted to boot using UEFI but the system hangs very early in >>> the >>> boot process. i have reverted to legacy mode for

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other

Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection

On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > i also attempted to boot using UEFI but the system hangs very early in the > boot process. i have reverted to legacy mode for now so that i can work, > but am keen to test out any patches or do any other debugging that is > needed. Hi Pete,

CURRENT from today throws lots of ACPI errors, lost HDMI detection

howdy, running code from today and having lots of issues.  when i boot the system (a kabylake laptop) using legacy mode in the BIOS i see lots of these errors are thrown in dmesg: acpi0: on motherboard Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS01._UPC

Re: acpiconf -s 3 does not call acpi sleep event handlers

For those not on the bug, this is being followed up in PR 230290. On Wed, Aug 1, 2018 at 10:27 PM, Johannes Lundberg wrote: > > > On Thu, Aug 2, 2018 at 06:20 Andriy Gapon wrote: >> >> On 02/08/2018 01:17, Conrad Meyer wrote: >> > I don't understand the concern. There is only one listener to

Re: acpiconf -s 3 does not call acpi sleep event handlers

On Thu, 2018-08-02 at 08:20 +0300, Andriy Gapon wrote: > On 02/08/2018 01:17, Conrad Meyer wrote: > > > > I don't understand the concern.  There is only one listener to the > > event and it just invokes ReqSleepState, which is responsible for > > performing all suspend behavior.  The behavior is

Re: acpiconf -s 3 does not call acpi sleep event handlers

On Thu, Aug 2, 2018 at 06:20 Andriy Gapon wrote: > On 02/08/2018 01:17, Conrad Meyer wrote: > > I don't understand the concern. There is only one listener to the > > event and it just invokes ReqSleepState, which is responsible for > > performing all suspend behavior. The behavior is identical

Re: acpiconf -s 3 does not call acpi sleep event handlers

On 02/08/2018 01:17, Conrad Meyer wrote: > I don't understand the concern. There is only one listener to the > event and it just invokes ReqSleepState, which is responsible for > performing all suspend behavior. The behavior is identical between > lid close and acpiconf. Unless someone is

Re: acpiconf -s 3 does not call acpi sleep event handlers

is perhaps poorly named. The event currently indicates >> >> that the lid was closed. And the final registered eventhandler for >> >> the event calls ReqSleepState. >> >> >> >> The ReqSleepState routine, as well as the userspace ioctl that >> >> 'acpiconf -s'

Re: acpiconf -s 3 does not call acpi sleep event handlers

qSleepState routine, as well as the userspace ioctl that >> 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather >> than invoking the acpi sleep event), were introduced together in >> r170976. >> > > Unless there's a way of calling suspend properly

Re: acpiconf -s 3 does not call acpi sleep event handlers

ndler for > >> the event calls ReqSleepState. > >> > >> The ReqSleepState routine, as well as the userspace ioctl that > >> 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather > >> than invoking the acpi sleep event), were introduced togethe

Re: acpiconf -s 3 does not call acpi sleep event handlers

eqSleepState. > > The ReqSleepState routine, as well as the userspace ioctl that > 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather > than invoking the acpi sleep event), were introduced together in > r170976. > > Unless there's a way of calling suspen

Re: acpiconf -s 3 does not call acpi sleep event handlers

that 'acpiconf -s' uses (which just invokes ReqSleepState directly, rather than invoking the acpi sleep event), were introduced together in r170976. Best, Conrad On Wed, Aug 1, 2018 at 8:05 AM, Johannes Lundberg wrote: > Hi > > As the title says, callbacks registered with > EVENTHAND

acpiconf -s 3 does not call acpi sleep event handlers

Hi As the title says, callbacks registered with EVENTHANDLER_REGISTER(acpi_sleep_event, does not get called when calling acpiconf -s 3. They do however, when suspending with lid or sleep button. Is this deliberate or an oversight? Cheers ___

Firmware Error (ACPI): Failure looking up [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND

(ACPI): Failure looking up [\_SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20171214/psargs-503) Jul 13 10:00:32 kernel: ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20171214/psparse-677) Jul 13 10:00:32 kernel: Firmware Error (ACPI): Failure looking up [\_SB.PCI0.LPCB.HEC.ECAV

ACPI is broken on CURRENT

I couldn't make the S3 suspend to work at all. Please see the bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654 Yuri ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: New ACPI Errors

On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs

Re: New ACPI Errors

On 02/16/2018 13:54, Pete Wright wrote: On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node

Re: X1 Carbon 6th gen. ACPI issues

On 03/10, Kirill Ponomarev wrote: > Hi, > > it seems new Carbonss have some issues with S3 according to this Lenovo > thread: > https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-Suspend-to/td-p/3998182 > > The same issues we have in CURRENT: >

X1 Carbon 6th gen. ACPI issues

Hi, it seems new Carbonss have some issues with S3 according to this Lenovo thread: https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-Suspend-to/td-p/3998182 The same issues we have in CURRENT: hw.acpi.supported_sleep_state: S4 S5 If someone

Re: ACPI panic on boot with new Lua loader and other minor issues

On Wed, Feb 21, 2018 at 8:55 AM, Warner Losh wrote: > > > On Wed, Feb 21, 2018 at 6:58 AM, Kyle Evans wrote: >> >> On Wed, Feb 21, 2018 at 4:43 AM, Juan Ramón Molina Menor >> wrote: >> > Le 20/02/2018 à 22:45, Kyle Evans a écrit : >> >> >> >>

Re: ACPI panic on boot with new Lua loader and other minor issues

On Wed, Feb 21, 2018 at 6:58 AM, Kyle Evans wrote: > On Wed, Feb 21, 2018 at 4:43 AM, Juan Ramón Molina Menor > wrote: > > Le 20/02/2018 à 22:45, Kyle Evans a écrit : > >> > >> On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor < > lis...@club.fr> > >>

Re: ACPI panic on boot with new Lua loader and other minor issues

> Le 20/02/2018 ? 22:45, Kyle Evans a ?crit?: > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ram?n Molina Menor > > wrote: > >> [... snip ...] > >> > >> Moreover, the "boot [kernel]" loader command does not work: > >> > >> OK ls /boot/kernel.old/kernel > >>

Re: ACPI panic on boot with new Lua loader and other minor issues

On Wed, Feb 21, 2018 at 4:43 AM, Juan Ramón Molina Menor wrote: > Le 20/02/2018 à 22:45, Kyle Evans a écrit : >> >> On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor >> wrote: >>> >>> [... snip ...] >>> >>> Moreover, the "boot [kernel]" loader command does

Re: ACPI panic on boot with new Lua loader and other minor issues

Le 20/02/2018 à 22:45, Kyle Evans a écrit : On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: [... snip ...] Moreover, the "boot [kernel]" loader command does not work: OK ls /boot/kernel.old/kernel /boot/kernel.old/kernel OK boot kernel.old Command failed

Re: ACPI panic on boot with new Lua loader and other minor issues

On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: > [... snip ...] > > Moreover, the "boot [kernel]" loader command does not work: > > OK ls /boot/kernel.old/kernel > /boot/kernel.old/kernel > OK boot kernel.old > Command failed > OK boot /boot/kernel.old/kernel

Re: ACPI panic on boot with new Lua loader and other minor issues

g without device atpic requires a local APIC For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous message: https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html OK show hint.acpi.0.disabled 1 Setting ACPI to On resolves the issue. Hi Kyle. As Da

Re: ACPI panic on boot with new Lua loader and other minor issues

On Feb 19, 2018 3:38 PM, "Kyle Evans" wrote: On Mon, Feb 19, 2018 at 4:32 PM, Warner Losh wrote: > > > On Mon, Feb 19, 2018 at 2:57 PM, Devin Teske wrote: >> >> >> >> > On Feb 19, 2018, at 2:21 PM, Kyle Evans wrote:

Re: ACPI panic on boot with new Lua loader and other minor issues

> On Feb 19, 2018, at 4:32 PM, Warner Losh wrote: > > > >> On Mon, Feb 19, 2018 at 2:57 PM, Devin Teske wrote: >> >> >> > On Feb 19, 2018, at 2:21 PM, Kyle Evans wrote: >> > >> > It seems that the Forth loader might be doing

Re: ACPI panic on boot with new Lua loader and other minor issues

ve done a full build of r329555 to test the new Lua boot loader. >> >> >> >> Both the new and the old kernels panic after being loaded with: >> >> >> >> panic: running without device atpic requires a local APIC >> >> >>

Re: ACPI panic on boot with new Lua loader and other minor issues

panic after being loaded with: > >> > >> panic: running without device atpic requires a local APIC > >> > >> For reasons unknown, ACPI is off, as shown by David Wolfskill in > a previous > >> message: > >> > > https://lists.free

Re: ACPI panic on boot with new Lua loader and other minor issues

w Lua boot loader. >> >> Both the new and the old kernels panic after being loaded with: >> >> panic: running without device atpic requires a local APIC >> >> For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous >> message: >> https:/

Re: ACPI panic on boot with new Lua loader and other minor issues

after being loaded with: >> >> panic: running without device atpic requires a local APIC >> >> For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous >> message: >> https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html &

Re: ACPI panic on boot with new Lua loader and other minor issues

On Mon, Feb 19, 2018 at 4:32 PM, Warner Losh wrote: > > > On Mon, Feb 19, 2018 at 2:57 PM, Devin Teske wrote: >> >> >> >> > On Feb 19, 2018, at 2:21 PM, Kyle Evans wrote: >> > >> > It seems that the Forth loader might be doing something

Re: ACPI panic on boot with new Lua loader and other minor issues

On Mon, Feb 19, 2018 at 2:57 PM, Devin Teske wrote: > > > > On Feb 19, 2018, at 2:21 PM, Kyle Evans wrote: > > > > It seems that the Forth loader might be doing something sneaky and > > replacing the standard common "boot" with a Forth boot that handles >

Re: ACPI panic on boot with new Lua loader and other minor issues

ithout device atpic requires a local APIC For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous message: https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html OK show hint.acpi.0.disabled 1 Setting ACPI to On resolves the issue. Hi Kyle. As David

Re: ACPI panic on boot with new Lua loader and other minor issues

> On Feb 19, 2018, at 2:21 PM, Kyle Evans wrote: > > It seems that the Forth loader might be doing something sneaky and > replacing the standard common "boot" with a Forth boot that handles > this a lot better. CC'ing dteske@ so they can confirm. I can indeed confirm this

Re: ACPI panic on boot with new Lua loader and other minor issues

t; I have done a full build of r329555 to test the new Lua boot loader. >> >> Both the new and the old kernels panic after being loaded with: >> >> panic: running without device atpic requires a local APIC >> >> For reasons unknown, ACPI is off, as shown by

Re: ACPI panic on boot with new Lua loader and other minor issues

requires a local APIC For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous message: https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html That has been fixed (for me, at least). My last two build/smoke-tests were at r329517 and r329561; I believe

Re: ACPI panic on boot with new Lua loader and other minor issues

ernels panic after being loaded with: > > panic: running without device atpic requires a local APIC > > For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous > message: > https://lists.freebsd.org/pipermail/freebsd-current/ 2018-February/068497.html > > OK show h

Re: ACPI panic on boot with new Lua loader and other minor issues

requires a local APIC > > For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous > message: > https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html > > OK show hint.acpi.0.disabled > 1 > > Setting ACPI to On resolves the issue. As Davi

Re: ACPI panic on boot with new Lua loader and other minor issues

gt; > For reasons unknown, ACPI is off, as shown by David Wolfskill in a > previous message: > https://lists.freebsd.org/pipermail/freebsd-current/2018-February/068497.html That has been fixed (for me, at least). My last two build/smoke-tests were at r329517 and r329561; I believe that r

ACPI panic on boot with new Lua loader and other minor issues

Moreover, the "boot [kernel]" loader command does not work: OK ls /boot/kernel.old/kernel /boot/kernel.old/kernel OK boot kernel.old Command failed OK boot /boot/kernel.old/kernel Command failed OK boot kernel Command failed I forgot that I tried starting with "unload", which seems to

ACPI panic on boot with new Lua loader and other minor issues

I have done a full build of r329555 to test the new Lua boot loader. Both the new and the old kernels panic after being loaded with: panic: running without device atpic requires a local APIC For reasons unknown, ACPI is off, as shown by David Wolfskill in a previous message: https

Re: New ACPI Errors

On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs

Re: New ACPI Errors

On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs

Re: New ACPI Errors

On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL

New ACPI Errors

Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse

ACPI Suspend/Resume on Lenovo 3000 G530 4151

="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 Features=0xafebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE> Features2=0xc00e31d<SSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,OS

Re: Add support for ACPI Module Device ACPI0004?

"PNP0C02", NULL >>> >> >> >> > > }; >>> >> >> >> > > +static char *sysres_ids[] = { "PNP0C01", "PNP0C02", >>> >> >> >> > > "ACPI0004", NULL }; >>> >> >

Re: Add support for ACPI Module Device ACPI0004?

t;> > > "ACPI0004", NULL }; >> >> >> >> > > >> >> >> >> > Hmm, so the role of C01 and C02 is to reserve system resources, >> >> >> >> > though we >> >> >> >> > in turn allow any

Re: Add support for ACPI Module Device ACPI0004?

}; > >> >> >> > > +static char *sysres_ids[] = { "PNP0C01", "PNP0C02", > >> >> >> > > "ACPI0004", NULL }; > >> >> >> > > > >> >> >> > Hmm, so the ro

Re: Add support for ACPI Module Device ACPI0004?

t;> > > "ACPI0004", NULL }; >> >> >> > > >> >> >> > Hmm, so the role of C01 and C02 is to reserve system resources, >> >> >> > though we >> >> >> > in turn allow any child o

Re: Add support for ACPI Module Device ACPI0004?

L }; > >> >> > > +static char *sysres_ids[] = { "PNP0C01", "PNP0C02", > >> >> > > "ACPI0004", NULL }; > >> >> > > > >> >> > Hmm, so the role of C01 and C02 is to reserve system resourc

Re: Add support for ACPI Module Device ACPI0004?

004", >> >> > > NULL }; >> >> > > >> >> > Hmm, so the role of C01 and C02 is to reserve system resources, though >> >> > we >> >> > in turn allow any child of acpi0 to suballocate those ranges (since >>

RE: Add support for ACPI Module Device ACPI0004?

", > NULL }; > > >> > > > > >> > Hmm, so the role of C01 and C02 is to reserve system resources, > though we > > >> > in turn allow any child of acpi0 to suballocate those ranges (since > historically > > >> > c01 and c0

Re: Add support for ACPI Module Device ACPI0004?

erve system resources, though we > >> > in turn allow any child of acpi0 to suballocate those ranges (since > >> > historically > >> > c01 and c02 tend to allocate I/O ranges that are then used by things > >> > like the > >> > EC, PS/2 keyb

Re: Add support for ACPI Module Device ACPI0004?

= { "PNP0C01", "PNP0C02", "ACPI0004", >> > > NULL }; >> > > >> > Hmm, so the role of C01 and C02 is to reserve system resources, though we >> > in turn allow any child of acpi0 to suballocate those ranges (since >> >

Re: Add support for ACPI Module Device ACPI0004?

> Hmm, so the role of C01 and C02 is to reserve system resources, though we > > in turn allow any child of acpi0 to suballocate those ranges (since > > historically > > c01 and c02 tend to allocate I/O ranges that are then used by things like > > the > > EC, PS/2 keybo

RE: Add support for ACPI Module Device ACPI0004?

te those ranges (since > historically > c01 and c02 tend to allocate I/O ranges that are then used by things like the > EC, PS/2 keyboard controller, etc.). From my reading of ACPI0004 in the ACPI > 6.1 spec it's not quite clear that ACPI0004 is like that? In particular, it > seems

Re: Add support for ACPI Module Device ACPI0004?

On Wednesday, April 19, 2017 12:26:51 PM Dexuan Cui wrote: > The ACPI firmware of Hyper-V UEFI VM has a Module Device whose Hardware > ID is "ACPI0004". The module device has a _CRS object defining some MMIO > ranges, which are needed when physical PCIe devices are passed

Add support for ACPI Module Device ACPI0004?

The ACPI firmware of Hyper-V UEFI VM has a Module Device whose Hardware ID is "ACPI0004". The module device has a _CRS object defining some MMIO ranges, which are needed when physical PCIe devices are passed through to the VM. Currently it looks FreeBSD doesn't make use of the ACPI mod

Re: ACPI Error on HP ProBook 430 G2

branch, vendor-sys/acpica/20161222/, see: https://svnweb.freebsd.org/changeset/base/310451 But not yet to "master" (12-current) ? Is that correct? My console has been filling up with messages like this: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName u

Re: ACPI Error on HP ProBook 430 G2

reebsd.org [mailto:owner-freebsd- > > a...@freebsd.org] On Behalf Of Edward Tomasz Napierala > > Sent: Wednesday, December 21, 2016 3:15 AM > > To: O. Hartmann <ohartm...@walstatt.org> > > Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir > > Zakhar

Re: ACPI Error on HP ProBook 430 G2

d to the following > branch, vendor-sys/acpica/20161222/, see: > > https://svnweb.freebsd.org/changeset/base/310451 > > But not yet to "master" (12-current) ? > > Is that correct? > > My console has been filling up with messages like this: > >> ACPI Ex

RE: ACPI Error on HP ProBook 430 G2

c: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir > Zakharov <zakharov...@gmail.com> > Subject: Re: ACPI Error on HP ProBook 430 G2 > > On 01/03/17 16:26, Moore, Robert wrote: > > Not sure I understand. The fix has been committed, and is part of > vers

RE: ACPI Error on HP ProBook 430 G2

sz Napierala > <tr...@freebsd.org>; O. Hartmann <ohartm...@walstatt.org> > Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir > Zakharov <zakharov...@gmail.com> > Subject: Re: ACPI Error on HP ProBook 430 G2 > > On 12/22/16 21:04, Moore, Robert wrote:

Re: ACPI Error on HP ProBook 430 G2

/310451 But not yet to "master" (12-current) ? Is that correct? My console has been filling up with messages like this: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20161117/dswexec-498) ACPI Error: Method parse/execution failed [\1

Re: ACPI Error on HP ProBook 430 G2

On 12/22/16 21:04, Moore, Robert wrote: ACPICA version 20161222 happened today, with a fix for the problem below. +1 When will the fix be merged to -head ? --HPS ___ freebsd-current@freebsd.org mailing list

RE: ACPI Error on HP ProBook 430 G2

z Napierala <tr...@freebsd.org>; O. Hartmann > <ohartm...@walstatt.org> > Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir > Zakharov <zakharov...@gmail.com> > Subject: RE: ACPI Error on HP ProBook 430 G2 > > We have fixed this issue for the la

<    1   2   3   4   5   6   7   8   9   10   >