In message <10399.1543270...@critter.freebsd.dk>, "Poul-Henning Kamp" writes:
>>I'm seeing it on my ThinkPad x230 as well
>
>and on T480 running 13.0-CURRENT r340932M as well:
And seems to be gone with this kernel:
13.0-CURRENT r341006M
Havn't tried the ones in between.
--
P
On 26/11/18 19:59, Yuri Pankov wrote:
> Renato Botelho wrote:
>> On 26/11/18 19:32, Florian Limberger wrote:
>>> Hi,
>>>
>>> On 20.11.18 14:46, Charlie Li wrote:
>>>> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
>&
Renato Botelho wrote:
> On 26/11/18 19:32, Florian Limberger wrote:
>> Hi,
>>
>> On 20.11.18 14:46, Charlie Li wrote:
>>> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
>>> (0xf80003662300) [EmbeddedControl] (20181031/evregion-
On 26/11/18 19:32, Florian Limberger wrote:
> Hi,
>
> On 20.11.18 14:46, Charlie Li wrote:
>> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
>> (0xf80003662300) [EmbeddedControl] (20181031/evregion-288)
>> Nov 20 09:35:19 ardmore
Hi,
On 20.11.18 14:46, Charlie Li wrote:
> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
> (0xf80003662300) [EmbeddedControl] (20181031/evregion-288)
> Nov 20 09:35:19 ardmore kernel: ACPI Error: Region EmbeddedControl
> (ID=3) has no handler (20181031
On 18-11-23 13:05:00, Charlie Li wrote:
> On 23/11/2018 00:02, Ben Widawsky wrote:
> > Thanks both of you. Here's another shot at roughly the same thing I asked
> > the
> > first reporter to try (that patch was wrong). If it doesn't work, can you
> > please
> > post the dmesg?
> >
> This patch w
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 23/11/2018 00:02, Ben Widawsky wrote:
> Thanks both of you. Here's another shot at roughly the same thing I asked the
> first reporter to try (that patch was wrong). If it doesn't work, can you
> please
> post the dmesg?
>
This patch works on my machine as well.
--
Charlie Li
Can't think of
On 18-11-23 16:42:22, Mateusz Piotrowski wrote:
> On Tue, 20 Nov 2018 at 15:47, Charlie Li wrote:
>
> > Somewhere between r340491 and r340650, probably starting from r340595,
> > my ThinkPad W550s started spewing these messages repeatedly in the
> > system log since boot:
> >
> > ...
> >
> > As a
On Tue, 20 Nov 2018 at 15:47, Charlie Li wrote:
> Somewhere between r340491 and r340650, probably starting from r340595,
> my ThinkPad W550s started spewing these messages repeatedly in the
> system log since boot:
>
> ...
>
> As a result, I am now unable to query battery information at the very
With your patch applied, normal behavior seems back again.
"dmesg" output and other relevent files are availabe at:
http://imp.ovh/acpi
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
Hi all,
"patch -p 1 < your_patch" gives me the following *.rej file:
@@ -362,7 +362,8 @@
ret = 0;
goto out;
-}
+} else
+ ecdt = 0;
ret = ACPI_ID_PROBE(device_get_parent(dev), dev, ec_ids, NULL);
if (ret > 0)
@@ -422,16 +434,6 @@
/* Store the value
Thanks both of you. Here's another shot at roughly the same thing I asked the
first reporter to try (that patch was wrong). If it doesn't work, can you please
post the dmesg?
diff --git a/sys/dev/acpica/acpi_ec.c b/sys/dev/acpica/acpi_ec.c
index a21dbc963af..666aba2b3c8 100644
--- a/sys/dev/acpica
On 21/11/2018 11:21, Charlie Li wrote:
> On 20/11/2018 14:37, Ben Widawsky wrote:
>> On 18-11-20 11:28:56, Ben Widawsky wrote:
>>> On 18-11-20 14:09:08, Jung-uk Kim wrote:
I am pretty sure r340644 caused the regression.
>>>
>>> Seems like a good bet. Could you please add the full dmesg as
On 20/11/2018 14:37, Ben Widawsky wrote:
> On 18-11-20 11:28:56, Ben Widawsky wrote:
>> On 18-11-20 14:09:08, Jung-uk Kim wrote:
>>> On 18. 11. 20., Charlie Li wrote:
>>>> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
>>>> (0xfff
Hi again,
Please find the requested files:
http://imp.ovh/18.2.0/acpidump_-dt_output
http://imp.ovh/18.2.0/acpi_ec_values
http://imp.ovh/18.2.0/dmesg_output
Best regards,
Samy
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/ma
Same problem/output as Charlie Li, with a Lenovo T520.
I will post requested output files as soon as possible.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freeb
Hi,
I have the same problem as Charlie Li. In case it could help you address
this I put up the data you requested in a gist:
https://gist.github.com/rebost/f8f231662a7501b14d63f348ee5e4ca2
you can also download it as a zip file:
https://gist.github.com/rebost/f8f231662a7501b14d63f348ee5e4ca2
the
> > > system log since boot:
> > >
> > > Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
> > > (0xf80003662300) [EmbeddedControl] (20181031/evregion-288)
> > > Nov 20 09:35:19 ardmore kernel: ACPI Error: Region EmbeddedCo
20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
> > (0xf80003662300) [EmbeddedControl] (20181031/evregion-288)
> > Nov 20 09:35:19 ardmore kernel: ACPI Error: Region EmbeddedControl
> > (ID=3) has no handler (20181031/exfldio-428)
> > Nov 20 09
On 18. 11. 20., Charlie Li wrote:
> Somewhere between r340491 and r340650, probably starting from r340595,
> my ThinkPad W550s started spewing these messages repeatedly in the
> system log since boot:
>
> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler f
Somewhere between r340491 and r340650, probably starting from r340595,
my ThinkPad W550s started spewing these messages repeatedly in the
system log since boot:
Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR]
(0xf80003662300) [EmbeddedControl] (20181031/evregion-288
navailable] (20161117/dswexec-498)
ACPI Error: Method parse/execution failed
[\134_SB.PCI0.LPCB.H_EC._Q50] (Node 0xf800047fce40),
AE_AML_OPERAND_TYPE (20161117/psparse-560)
acpi_ec0: evaluation of query method _Q50 failed: AE_AML_OPERAND_TYPE
over the holidays, so I assume that means the previous
...@freebsd.org [mailto:owner-freebsd-
> > a...@freebsd.org] On Behalf Of Edward Tomasz Napierala
> > Sent: Wednesday, December 21, 2016 3:15 AM
> > To: O. Hartmann
> > Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> > Zakharov
> > Subj
ception: AE_AML_OPERAND_TYPE, While resolving operands for
>> [OpcodeName unavailable] (20161117/dswexec-498)
>> ACPI Error: Method parse/execution failed
>> [\134_SB.PCI0.LPCB.H_EC._Q50] (Node 0xf800047fce40),
>> AE_AML_OPERAND_TYPE (20161117/psparse-560)
>> acpi_
> -Original Message-
> From: Hans Petter Selasky [mailto:h...@selasky.org]
> Sent: Tuesday, January 3, 2017 8:23 AM
> To: Moore, Robert ; Edward Tomasz Napierala
> ; O. Hartmann
> Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> Zakharov
>
> Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> Zakharov
> Subject: 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
>
/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
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
https://lists.freebsd.org/mailman/listin
z Napierala ; O. Hartmann
>
> Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> Zakharov
> Subject: RE: ACPI Error on HP ProBook 430 G2
>
> We have fixed this issue for the latest version of ACPICA that will
> happen this week, probably 22 december.
>
>
r 21, 2016 3:15 AM
> To: O. Hartmann
> Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> Zakharov
> Subject: Re: ACPI Error on HP ProBook 430 G2
>
> On 1220T1734, O. Hartmann wrote:
> > Am Tue, 20 Dec 2016 18:09:20 +0300
> > Vladimir Zakharov
21.12.2016 13:14, Edward Tomasz Napierała пишет:
On 1220T1734, O. Hartmann wrote:
Am Tue, 20 Dec 2016 18:09:20 +0300
Vladimir Zakharov schrieb:
Hello!
Some time ago new ACPI messages appeared on console and in /var/log/messages.
Like
these:
ACPI Error: Needed type [Reference], found
On 1220T1734, O. Hartmann wrote:
> Am Tue, 20 Dec 2016 18:09:20 +0300
> Vladimir Zakharov schrieb:
>
> > Hello!
> >
> > Some time ago new ACPI messages appeared on console and in
> > /var/log/messages. Like
> > these:
> >
> > AC
Am Tue, 20 Dec 2016 18:09:20 +0300
Vladimir Zakharov schrieb:
> Hello!
>
> Some time ago new ACPI messages appeared on console and in /var/log/messages.
> Like
> these:
>
> ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
> (20161117/exr
Hello!
Some time ago new ACPI messages appeared on console and in /var/log/messages.
Like these:
ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
(20161117/exresop-111)
ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName
unavailable
r the
>>> login prompt)
>>>
>>>> May 2 21:52:18 FreeBSDx64 login: ROOT LOGIN (root) ON ttyv0
>>>> May 2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for
>>>> fixed event - PM_Timer (0), disabling (20160422/evevent-323)
>
:18 FreeBSDx64 login: ROOT LOGIN (root) ON ttyv0
> >> May 2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for
> >> fixed event - PM_Timer (0), disabling (20160422/evevent-323)
> >> May 2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for
> &
Hi,
I'm having the same issue with downloaded ISO from Monday May 2nd under
VirtualBox same version.
It happens at 10 minutes after system is started.
Thanks.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/free
to boot FreeBSD shuts down
> with (for example):
> (the root login line is just to give an idea of the time frame after the
> login prompt)
>
>> May 2 21:52:18 FreeBSDx64 login: ROOT LOGIN (root) ON ttyv0
>> May 2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed ha
to give an idea of the time frame after the login
prompt)
> May 2 21:52:18 FreeBSDx64 login: ROOT LOGIN (root) ON ttyv0
> May 2 22:01:45 FreeBSDx64 kernel: ACPI Error: No installed handler for fixed
> event - PM_Timer (0), disabling (20160422/evevent-323)
> May 2 22:01:45 FreeB
On Sun, 5 Oct 2003, Matt Douhan wrote:
> Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
> failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc47d
> d980), AE_AML_REGION_LIMIT
> Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
> failed [\_SB_.PCI0.LPCB.
Hello
I get the following error msgs on the following system
11:53pm mdouhan @ [dragonfruit] ~ > uname -a
FreeBSD dragonfruit.fruitsalad.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sun Oct
5 23:21:41 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/
sys/DRAGONFRUIT i386
11:54pm mdouhan @ [dragonfr
On Sat, 14 Jun 2003, Doug White wrote:
Hi,
> This might be fixable ... its overrunning a region definition which could
> be a simple bug that could be fixed by extracting the DSDT, convert to
> ASL, fix, recompile, and override. Of course you have to know ASL :)
No I don't really know but rememb
On Sat, 14 Jun 2003, Bjoern A. Zeeb wrote:
> already had this with 5.0 as I do with 5.1 and I suspect it's
> a broken BIOS ?
Or something that the MS interpreter allows and the stringent Intel one
does not.
This might be fixable ... its overrunning a region definition which could
be a simple bug
Hi,
already had this with 5.0 as I do with 5.1 and I suspect it's
a broken BIOS ?
It is a MSI-6210 w/o SCSI onboard but MP. It's the latest BIOS
revision available for this board - I can check the version
on request but I do not really like rebooting again ;-)
--- boot messages ---
...
acpi0: on
from my dmesg:
[snip]
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31
Using $PIR table, 6 entries at 0xc00f1a70
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-
Nate Lawson wrote:
> On Thu, 16 Jan 2003, Peter Schultz wrote:
>
> >ACPI-1287: *** Error: Method execution failed, E_AML_UNINITIALIZED_LOCAL
> >can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL
> >
> >I have a Tyan S1834 and see the above error during boot. I'm not
> >sure i
On Thu, 16 Jan 2003, Peter Schultz wrote:
> ACPI-1287: *** Error: Method execution failed, E_AML_UNINITIALIZED_LOCAL
> can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL
>
> I have a Tyan S1834 and see the above error during boot. I'm not sure
> if this is such a big problem
ACPI-1287: *** Error: Method execution failed, E_AML_UNINITIALIZED_LOCAL
can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL
I have a Tyan S1834 and see the above error during boot. I'm not sure
if this is such a big problem but it would be nice to eliminate the error.
Thank
Hackers,
on yesterday's -current i see
ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR
ACPI-1354: *** Error: Method execution failed, AE_ERROR
this is IBM ThinkPad 390x laptop. dmesg and acpidump are attached.
any ideas?
thanks
max
Copyright (c) 1992-2002 The FreeBSD Pr
Hi!
I updated my notebook from -stable to -current some days ago and get this
message ~ every second:
ACPI-0294: *** Error: Method execution failed, AE_AML_REGION_LIMIT
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Hi!
I updated my notebook from -stable to -current some days ago and get this
message ~ every second:
ACPI-0294: *** Error: Method execution failed, AE_AML_REGION_LIMIT
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
On Tuesday 04 September 2001 03:04 pm, Mike Smith wrote:
> > I'm having a problem with the new acpi. One one of our boxes (amd K7 900
> > Mhz Compaq) does not probe xl properly. It returns Could not probe memory
> > (returns error6). There is no pnp setting in this bios. I went back to
> > pre-com
> I'm having a problem with the new acpi. One one of our boxes (amd K7 900 Mhz
> Compaq) does not probe xl properly. It returns Could not probe memory
> (returns error6). There is no pnp setting in this bios. I went back to
> pre-commit and it works fine. Any suggestions?
There seems to be a c
I'm having a problem with the new acpi. One one of our boxes (amd K7 900 Mhz
Compaq) does not probe xl properly. It returns Could not probe memory
(returns error6). There is no pnp setting in this bios. I went back to
pre-commit and it works fine. Any suggestions?
Beech
--
Micro$oft: "Where c
55 matches
Mail list logo
