On Wednesday, 14 November 2018 12:41:53 MST Stefan Ehmann wrote:
> On 11/14/18 5:41 AM, Conrad Meyer wrote:
> > Ok I'll go ahead and commit that too.
>
> Applied to 12.0-BETA, Ryzen 7 2700 values are now in the 30-55C range.
> Looks reasonable.
Much better here, too:
dev.amdtemp.3.core0.sensor0
On 11/14/18 5:41 AM, Conrad Meyer wrote:
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
> thing. I guess that patch never landed? 10
Perfect! Sounds like we are on the right track, at least.
Best,
Conrad
On Tue, Nov 13, 2018 at 8:55 PM Rebecca Cran wrote:
>
> On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote:
> > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> > I.e., sometimes the CPU cho
On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote:
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
> thing. I guess that pa
Please try r340426 :-).
On Tue, Nov 13, 2018 at 8:41 PM Conrad Meyer wrote:
>
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
> thing.
You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
I.e., sometimes the CPU chooses to report on a range from 0-225C and
sometimes -49C-206C. I think someone else's 2990WX did the same
thing. I guess that patch never landed? 102°C - 49°C is the very
reasonable 53°C.
Yeah, si
On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote:
>
> On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote:
>
> > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat
> > plausible 75?C (still pretty warm even for load). How good is your
> > cooling solution?
>
> D'oh, of
On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote:
> Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat
> plausible 75?C (still pretty warm even for load). How good is your
> cooling solution?
D'oh, of course it's -54 instead of +54 (For some reason I presumed a positi
On Tue, Nov 13, 2018 at 8:05 PM Rebecca Cran wrote:
>
> 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 thou
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 l
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 unde
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 generatio
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 f
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
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 not.
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
> > >> errors. Not sure if they are related.
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.
> >
> > It s a bit legacy )
> > Try mine: http://www.netlab.l
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 they do not attach, it suggests
> 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
>> errors. Not sure if they are related.
>
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). Don't
On 11/13/18 10:40 PM, Daniel Eischen wrote:
>
>> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>>
>>> 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,
>
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
> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>
>> 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. amdt
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 number
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
>>> report any temperature sensors, and acpi seems to have some
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 w
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.
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.linkpc.net/downloa
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 Pm2ControlBlock
loader.conf 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
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 attem
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 th
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 i
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 th
inging up my iwn interface and HDMI 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
d 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.
-p
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
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 l
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 now
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 deb
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,
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], AE_ALREADY_EXIS
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-472)
>> ACPI Error: Method parse/
ptr_t
+#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS
#define ACPI_USE_DO_WHILE_0
#define ACPI_USE_LOCAL_CACHE
#define ACPI_USE_NATIVE_DIVIDE
hi there - i was wondering if anyone has taken a look at this issue. I
am still seeing these ACPI errors on recent CURRENT systems:
ACPI Error: No po
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-472
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-472)
>> ACPI Error: Method parse/
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 (2018020
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/e
Have you checked for BIOS updates? The BIOS on recent Skylake laptops
have been a running disaster. At least the Dell XPS laptops had ACPI
errors be fixed by an update.
-M
On Sat, Jul 30, 2016 at 10:43 PM, Ben Woods wrote:
> Hi everyone,
>
> I get the following ACPI errors in my d
Hi everyone,
I get the following ACPI errors in my dmesg when booting my NEC Lavie HZ750
laptop with FreeBSD 12-current. I have noticed things not functioning
correct (except suspend/resume not working), but then again I don't really
know much about ACPI or what I should expect to see. Any
* Steve Ames <[EMAIL PROTECTED]> [030908 20:26]:
>
> Hey. I installed a new motherboard today and now I get a lot of ACPI
> errors (with a kernel from today and one from a few days back). This
> anything to worry about?
Not really, just annoying. A fair number (all t
Hey. I installed a new motherboard today and now I get a lot of ACPI
errors (with a kernel from today and one from a few days back). This
anything to worry about?
-Steve
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc046a248.
acpi0: on motherboard
acpi0: power button is handled
It would help if you would tell me when you last had a working kernel.
The output of acpidump -t -d -o martin.dsdt > martin.asl would also help.
-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
Martin wrote:
Hi,
I have more problems to report with the ACPI support and will submit a
PR, if you want. I don't know when this got broken.
Here some pieces of my dmesg:
---
FreeBSD 5.1-CURRENT #0: Thu Sep 4 22:38:56 CEST 2003
[...]
acpi0: on motherboard
Take a look at PR kern/48494, ther
Am Do, 2003-09-04 um 23.56 schrieb David O'Brien:
> Athlon-based?
No.
CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x383f9ff
It's an old Abit mainboard, but everything always worked here.
Martin
_
On Thu, Sep 04, 2003 at 11:30:49PM +0200, Martin wrote:
> I have more problems to report with the ACPI support and will submit a
> PR, if you want. I don't know when this got broken.
...
> As you can see I recompiled today to confirm that the problem
> still exists. This is only about floppy. Every
Hi,
I have more problems to report with the ACPI support and will submit a
PR, if you want. I don't know when this got broken.
Here some pieces of my dmesg:
---
FreeBSD 5.1-CURRENT #0: Thu Sep 4 22:38:56 CEST 2003
[...]
acpi0: on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 8 ent
On Wed, Jun 18, 2003 at 09:11:23AM +0200, Maikel Verheijen wrote:
> I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get
> quite a lot (well: 48 :) of these errors on boot:
>
> ACPI-0293: *** Warning: Buffer created with zero length in AML
> -0166: *** Error: UtAlloc
Hi list!
I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get
quite a lot (well: 48 :) of these errors on boot:
ACPI-0293: *** Warning: Buffer created with zero length in AML
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
Are those harmfull? Is there
>It seems like the fix right now is to disable it.
>Put this line:
>hint.acpi.0.disabled="1"
>in /boot/device.hints
Thankyou, this has given me a nice clean bootup now and I can reboot without
it panicing.
I'm still curious to learn what all that stuff ment though!
---
Matt ([EMAIL PROTECTED])
h
ot of ACPI errors on bootup and also a panic when I try to
reboot it, though luckily after it's synced the disks.
I have saved the dmesg output to http://tao.xtaz.co.uk/dmesg.txt
I was wondering if somebody could tell me what all those errors (and the
random gibberish at the top) is about. I a
Hi,
I have just recently installed -CURRENT on my desktop as I've been using it
succesfully on a server for months now. However this desktop has much more
advanced hardware. Whilst it does work perfectly and I have device support for
everything I get a lot of ACPI errors on bootup and a
>From dmesg.boot:
acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
ACPI-1287: *** Error: Method execution failed, AE_ERROR
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04ff0a8.
Timecounter "
"David O'Brien" wrote:
> Ever since the last ACPI import, I get all this output (non-verbose)
> boot. What's the change on them going away soon?
>
> acpi0: on motherboard
> ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
> ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE
Ever since the last ACPI import, I get all this output (non-verbose)
boot. What's the change on them going away soon?
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND
ACPI-1287: *** Error
On Thu, 2 Jan 2003, Adrian Neumaier wrote:
> on of the problems this here:
>
> ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
> ACPI-1287: *** Error: Method execution failed, AE_ERROR
> ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
> ACPI-1287: *** Er
Hi,
i have a hp omnibook xe4100 and the acpi stuff has some problems i dont
know how to solve them.
on of the problems this here:
ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
ACPI-1287: *** Error: Method execution failed, AE_ERROR
ACPI-0432: *** Error: Handler for [Embed
> On Thu, 28 Nov 2002 13:38:13 +0900 (JST), Mitsuru IWASAKI
><[EMAIL PROTECTED]> said:
Mitsuru> The patches against today's CURRENT at:
Mitsuru>
http://people.freebsd.org/~iwasaki/acpi/acpica-20021118-20021122-test20021128.diff
Mitsuru> Please try this if you have problems about
In message <[EMAIL PROTECTED]>, Hongbo Li wrot
e:
>I installed FBSD-current on my laptop(IBM Thinkpad
>A21m). These were some error messages about ACPI in
>dmesg:
>
>system power profile changed to 'economy'
>ACPI-0432: *** Error: Handler for
>[EmbeddedControl] returned AE_ERROR
>ACPI-1287:
I installed FBSD-current on my laptop(IBM Thinkpad
A21m). These were some error messages about ACPI in
dmesg:
system power profile changed to 'economy'
ACPI-0432: *** Error: Handler for
[EmbeddedControl] returned AE_ERROR
ACPI-1287: *** Error: Method execution failed,
AE_ERROR
ACPI-043
Saturday, November 30, 2002 4:34 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000
> based system
>
> * Mitsuru IWASAKI ([EMAIL PROTECTED]):
>
> Iwasaki-san,
> list members,
>
>
: Saturday, November 30, 2002 4:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000
based system
* Mitsuru IWASAKI ([EMAIL PROTECTED]):
Iwasaki-san,
list members,
> > > ACPI-0438: *** Error: L
* Mitsuru IWASAKI ([EMAIL PROTECTED]):
Iwasaki-san,
list members,
> > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
> > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
>
> I think that this was caused by the following spec changes.
> From CHANGES.txt:
Hi,
> A freshly built system with Now 28 sources now throws the ACPI errors
> seen in the dmesg output. The former ACPI snapshot did not complain in
> any way on this system.
[snip]
> > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
> > ACPI-12
A freshly built system with Now 28 sources now throws the ACPI errors
seen in the dmesg output. The former ACPI snapshot did not complain in
any way on this system.
The board in question is a Gigabyte BX2000 with F7 BIOS.
--Thomas
dmesg:
> Copyright (c) 1992-2002 The FreeBSD Proj
* De: Mitsuru IWASAKI <[EMAIL PROTECTED]> [ Data: 2002-11-27 ]
[ Subjecte: Call for testers: acpica-unix-20021122 (was Re: ACPI errors and
then panic - fixed!) ]
> The patches against today's CURRENT at:
> http://people.freebsd.org/~iwasaki/acpi/acpica-20021118-20021122-
Hi all,
> > Our web person is out today, so things will be posted Monday at the
> > earliest.
> >
> > I'll email Iwasaki-san the latest release, so y'all can get going if you
> > want.
>
> Thank you!
> I've just confirmed that the deleted object problem had been solved in
> the latest release (A
Hi,
> Our web person is out today, so things will be posted Monday at the
> earliest.
>
> I'll email Iwasaki-san the latest release, so y'all can get going if you
> want.
Thank you!
I've just confirmed that the deleted object problem had been solved in
the latest release (Andy sent it to me).
I'
; To: 'Mitsuru IWASAKI'; Grover, Andrew; Moore, Robert
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
>
>
>
> The deleted object problem has been fixed in the 20021122
> release which
]
Subject: Re: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
Hi, Intel folks.
It seems that there is a bug in cached object utilization.
This causes strange behavior;
first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but
second (or later) evaluation returns AE_TYPE.
> acpi_cmbat0: er
> On Tue, 26 Nov 2002 14:33:09 +0900 (JST), Mitsuru IWASAKI
><[EMAIL PROTECTED]> said:
Mitsuru> Hi,
Mitsuru> Are you trying this with acpica-unix-20021118 patch which was
Mitsuru> announced recently?
Mitsuru>
http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-te
Hi, Intel folks.
It seems that there is a bug in cached object utilization.
This causes strange behavior;
first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but
second (or later) evaluation returns AE_TYPE.
> acpi_cmbat0: error fetching current battery status -- AE_TYPE
The raw DSDT is at:
On Thu, 21 Nov 2002, Mitsuru IWASAKI wrote:
> > On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> > > From: Nate Lawson <[EMAIL PROTECTED]>
> > > Subject: ACPI errors and then panic
> > > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
> > > Message-ID: <
TED]>
Subject: ACPI errors - IBM Thinkpad A31p
Date: 26 Nov 2002 10:35:41 +0530
Message-ID: <[EMAIL PROTECTED]>
> Hi Folks,
>
> I see this error while booting into BSD and I presume this might be the
> problem that acpi on my TP does not work.
>
> The
Hi Folks,
I see this error while booting into BSD and I presume this might be the
problem that acpi on my TP does not work.
The errors are something like this.
acpi0: on motherboard
Using $PIR table, 14 entries at 0xc00fdeb0
ACPI-1354: *** Er
Hi Folks,
I see this error while booting into BSD and I presume this might be the
problem that acpi on my TP does not work.
The errors are something like this.
acpi0: on motherboard
Using $PIR table, 14 entries at 0xc00fdeb0
ACPI-1354: *** Er
Hi,
> On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> > From: Nate Lawson <[EMAIL PROTECTED]>
> > Subject: ACPI errors and then panic
> > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
> > Message-ID: <[EMAIL PROTECTED]>
> >
> > > My laptop app
On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> From: Nate Lawson <[EMAIL PROTECTED]>
> Subject: ACPI errors and then panic
> Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
> Message-ID: <[EMAIL PROTECTED]>
>
> > My laptop appears to work ok without ACPI but of cours
Thank you for the reply.
On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> Hi,
> # ACPI CA related problem should be sent to [EMAIL PROTECTED]
> # so that Intel folks can be aware of the problem.
Ok, I didn't know that.
> From: Nate Lawson <[EMAIL PROTECTED]>
> Subject:
Hi,
# ACPI CA related problem should be sent to [EMAIL PROTECTED]
# so that Intel folks can be aware of the problem.
From: Nate Lawson <[EMAIL PROTECTED]>
Subject: ACPI errors and then panic
Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
> My laptop
My laptop appears to work ok without ACPI but of course I don't get
suspend, resume, etc. I have never been able to get ACPI to work with it,
including with a -current as of 2 hours ago. If ACPI is enabled, I get a
spew of:
ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name
and
On Thu, Sep 05, 2002 at 03:06:30PM +0900, Mitsuru IWASAKI wrote:
> Please try the latest version acpica-unix-20020829, patches for
> FreeBSD at:
> http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020829-test20020905.diff
Hi Mitsuru,
I applied your patches today and besides the "Revision
Hi,
> Below is a trimmed dmesg from booting yesterdays CURRENT on my
> SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset).
> I heven't found anything wrong with the OS, it is just that the boot
> seems to be a bit on the chatty side :-)
> Is this caused by a bad BIOS setting or is there
Below is a trimmed dmesg from booting yesterdays CURRENT on my
SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset).
I heven't found anything wrong with the OS, it is just that the boot
seems to be a bit on the chatty side :-)
Is this caused by a bad BIOS setting or is there something stra
Mitsuru IWASAKI wrote:
> [move to -current because STABLE don't have acpica support yet]
>
> Hi,
>
> > System: TOS 5005-S504
> > Error with any kernel build:
> > Using $PIR table, 0 entries at 0xc00f0190
> > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNAT
URE
> >
-Original Message-
From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]]
Sent: Sun 8/4/2002 8:59 AM
To: Robert D Hughes
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: ACPI errors
[move to -current because STABLE don't have acpica support yet]
Reposted because I screwed up the first time and sent it to the wrong list
System: TOS 5005-S504
Error with any kernel build:
Using $PIR table, 0 entries at 0xc00f0190
ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE
ACPI-0213: *** Error: AcpiLoadTables: C
It seems Mitsuru IWASAKI wrote:
> [move to -current because STABLE don't have acpica support yet]
>
> Hi,
>
> > System: TOS 5005-S504
> > Error with any kernel build:
> > Using $PIR table, 0 entries at 0xc00f0190
> > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE
[move to -current because STABLE don't have acpica support yet]
Hi,
> System: TOS 5005-S504
> Error with any kernel build:
> Using $PIR table, 0 entries at 0xc00f0190
> ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE
> ACPI-0213: *** Error: AcpiLoadTables: Could no
When I boot up my gateway solo 2550, I get the following errors
ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
ACPI-1305: *** Error: Method execution failed, AE_ERROR
ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
ACPI-1305: *** Error:
1 - 100 of 104 matches
Mail list logo
