Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 2020-05-27 23:38, John Baldwin wrote: No. I get that constantly on a desktop that never suspends/resumes. It only started after upgrading to 12.0. If you have time, could you investigate why the USB host controllers Root HUB PCI register flips to -1U ? Which cause these spurious events ..

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 5/27/20 2:05 PM, Hans Petter Selasky wrote: > On 2020-05-27 15:41, Justin Hibbits wrote: >> On Wed, 27 May 2020 06:27:16 -0700 >> John Baldwin wrote: >> >>> On 5/27/20 2:39 AM, Andriy Gapon wrote: On 27/05/2020 11:13, Andriy Gapon wrote: > I added more diagnostics and it seems to suppo

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 2020-05-27 15:41, Justin Hibbits wrote: On Wed, 27 May 2020 06:27:16 -0700 John Baldwin wrote: On 5/27/20 2:39 AM, Andriy Gapon wrote: On 27/05/2020 11:13, Andriy Gapon wrote: I added more diagnostics and it seems to support the idea that the problem is related to I/O cycles and bridges.

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On Wed, 27 May 2020 06:27:16 -0700 John Baldwin wrote: > On 5/27/20 2:39 AM, Andriy Gapon wrote: > > On 27/05/2020 11:13, Andriy Gapon wrote: > >> I added more diagnostics and it seems to support the idea that the > >> problem is related to I/O cycles and bridges. > >> > >> ACPI timer suddenly

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 27/05/2020 16:27, John Baldwin wrote: > The "solution" I think is to have resume be multi-pass and to resume all the > bridges > first before trying to resume leaf devices (including timers), but that's a > fair bit > of work. It might be that we just need to resume timer interrupts later >

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 5/27/20 2:39 AM, Andriy Gapon wrote: > On 27/05/2020 11:13, Andriy Gapon wrote: >> I added more diagnostics and it seems to support the idea that the problem is >> related to I/O cycles and bridges. >> >> ACPI timer suddenly starts returning 0x and that lasts for tens of >> microseconds

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 27/05/2020 11:13, Andriy Gapon wrote: > I added more diagnostics and it seems to support the idea that the problem is > related to I/O cycles and bridges. > > ACPI timer suddenly starts returning 0x and that lasts for tens of > microseconds before the timer goes back to returning normal

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 27/05/2020 01:14, John Baldwin wrote: > On 5/26/20 11:55 AM, Konstantin Belousov wrote: >> On Tue, May 26, 2020 at 06:22:13PM +0300, Andriy Gapon wrote: >>> I am not sure if this is just a coincidence but it appears as if a write to >>> some >>> PCI configuration register could temporarily inte

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On 5/26/20 11:55 AM, Konstantin Belousov wrote: > On Tue, May 26, 2020 at 06:22:13PM +0300, Andriy Gapon wrote: >> On 25/05/2020 11:37, Andriy Gapon wrote: >>> Also, there is another issue related to atrtc. >>> When I have both drivers attached, and also when I have only atrtc attached >>> (efi.rt.

Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time]

On Tue, May 26, 2020 at 06:22:13PM +0300, Andriy Gapon wrote: > On 25/05/2020 11:37, Andriy Gapon wrote: > > Also, there is another issue related to atrtc. > > When I have both drivers attached, and also when I have only atrtc attached > > (efi.rt.disabled=1), system clock jumps 10 minutes forward

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

On Sat, 20 Jul 2019 00:54:47 +0200 Evilham wrote: > Minor glitches: > - xbacklight doesn't work, neither does intel-backlight because > it's AMD > - Speakers don't appear to work, audio input/output on 3.5 jack > does. > - SD card reader doesn't work (Bounty for 125 USD: > https://bugs.

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

On dg., jul. 21 2019, Cristian Pogolsha wrote: Hi, Thank you for the instructions. I have a question related to post-installation. My system doesn't boot after installing and rebooting the system. It just doesn't find the partition on the drive. I get a blank screen when selecting from the bo

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

On ds., jul. 20 2019, Evilham wrote: Serious issue: I was just debugging this right now, more infos with a proper bug report will come, but I think the system encounters a deadlock sometimes with the drm-kmod / amdgpu which results in a kernel panic. It is a serious issue, but it allows me to use

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

Having same issue with an i915 inside a hp envy On July 19, 2019 3:15:11 PM PDT, Cristian Pogolsha wrote: >Hi, > >I tried recently to boot FreeBSD current r350103 on a Thinkpad A485. >It's >the AMD Ryzen equivalent of the T480. During the boot I encountered >this >ACPI related error >https://driv

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

Hey, thanks for the feedback and your work, didn't think this would be interesting for anyone but the laptop owners. On ds., jul. 20 2019, Greg V. wrote: On July 20, 2019 1:54:47 AM GMT+03:00, Evilham wrote: it even suspends and resumes back to X Wow, that's great news! Desktop Ryzen+

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

On July 20, 2019 1:54:47 AM GMT+03:00, Evilham wrote: > it even suspends and resumes back to X Wow, that's great news! Desktop Ryzen+Vega doesn't (not that I need suspend very much on desktop haha) >- xbacklight doesn't work, neither does intel-backlight because > it's AMD Since it's a Thin

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

Hi Jordy, Thank you for your fast reply. Your links were very helpful. As per the bugzilla report https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760, during the kernel load screen I dropped to shell prompt and changed the boot params with command 'set hw.pci.mcfg="0" I was successful bootin

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

On 7/19/19 3:54 PM, Evilham wrote: > > Serious issue: > I was just debugging this right now, more infos with a proper bug > report will come, but I think the system encounters a deadlock > sometimes with the drm-kmod / amdgpu which results in a kernel panic. > It is a serious issue, but it allows

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

Hey, On ds., jul. 20 2019, Cristian Pogolsha wrote: I tried recently to boot FreeBSD current r350103 on a Thinkpad A485. It's the AMD Ryzen equivalent of the T480. During the boot I encountered this ACPI related error https://drive.google.com/file/d/1dzgSonn6Cuc1YrDeAUYSqHZlcmzaDY2Y/view I

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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] (0xf80003662300) [EmbeddedControl] (20181031/evreg

Re: 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-288) >>> Nov 20 09:35:19 ardmore kernel: A

Re: ACPI Error: No handler for Region [ECOR]

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 kernel: ACPI Error: Region EmbeddedCon

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

___ 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"

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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] (0xf80003662300) [EmbeddedControl] (20181031/

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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

Re: ACPI Error: No handler for Region [ECOR]

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: > > > Somewhere between r340491 and r340650, probably starting from r340595, > > > my ThinkPad W550s started spewing these messages repeatedly in the > > > system log since boo

Re: ACPI Error: No handler for Region [ECOR]

On 18-11-20 14:09:08, Jung-uk Kim wrote: > 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 Err

Re: ACPI Error: No handler for Region [ECOR]

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 for Region [ECOR] > (0xf8000366230

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 : >> >> >> >> On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Me

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> > >> wrote: > >>> > >>> [... snip ...] > >

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 ke

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 not work: >>> >>> OK ls /boot/ker

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 OK boot /boot/ker

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 > Command failed

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

Le 19/02/2018 à 21:21, Kyle Evans a écrit :> Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: 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 require

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: >> > >> > It seems that the Forth loader might be doing something sneaky and >

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 something sneaky and >> > replacing the standard common "boot" w

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

gets sOn Mon, Feb 19, 2018 at 6:11 PM, Peter Lei wrote: > > > On 2/19/18 5:48 PM, Kyle Evans wrote: >> >> >> On Feb 19, 2018 5:44 PM, "Peter Lei" > > wrote: >> >> >> >> On 2/19/18 2:21 PM, Kyle Evans wrote: >> > Hello! >> > >> > On Mon, Feb 19, 2018 at 8

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

On 2/19/18 5:48 PM, Kyle Evans wrote: > > > On Feb 19, 2018 5:44 PM, "Peter Lei" > wrote: > > > > On 2/19/18 2:21 PM, Kyle Evans wrote: > > Hello! > > > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor > mailto:lis...@club.fr>> wrote:

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

On Feb 19, 2018 5:44 PM, "Peter Lei" wrote: On 2/19/18 2:21 PM, Kyle Evans wrote: > Hello! > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: >> 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

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

On 2/19/18 2:21 PM, Kyle Evans wrote: > Hello! > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor > wrote: >> 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

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 sneaky and >> > replacing the standard common "boot" with a

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 > > this a lot better. CC'ing dteske@ so t

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

Le 19/02/2018 à 21:21, Kyle Evans a écrit : Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: 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

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 as fact. Not able to

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

On Mon, Feb 19, 2018 at 3:37 PM, Warner Losh wrote: > > > On Feb 19, 2018 1:23 PM, "Kyle Evans" wrote: > > Hello! > > On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor > wrote: >> I have done a full build of r329555 to test the new Lua boot loader. >> >> Both the new and the old kernels p

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

Le 19/02/2018 à 15:39, David Wolfskill a écrit : On Mon, Feb 19, 2018 at 03:21:50PM +0100, Juan Ramón Molina Menor wrote: 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 req

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

On Feb 19, 2018 1:23 PM, "Kyle Evans" wrote: Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: > 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

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

Hello! On Mon, Feb 19, 2018 at 8:21 AM, Juan Ramón Molina Menor wrote: > 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,

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

On Mon, Feb 19, 2018 at 03:21:50PM +0100, Juan Ramón Molina Menor wrote: > 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 unknow

Re: ACPI Error on HP ProBook 430 G2

03.01.2017 20:21, Jung-uk Kim пишет: On 01/03/2017 11:22, Hans Petter Selasky wrote: On 01/03/17 16:26, Moore, Robert wrote: Not sure I understand. The fix has been committed, and is part of version 20161222. Hi Robert, From what I can see that patches have been pushed to the following bra

Re: ACPI Error on HP ProBook 430 G2

...@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

Re: ACPI Error on HP ProBook 430 G2

On 01/03/2017 11:22, Hans Petter Selasky wrote: > On 01/03/17 16:26, Moore, Robert wrote: >> Not sure I understand. The fix has been committed, and is part of >> version 20161222. >> >> > > Hi Robert, > > From what I can see that patches have been pushed to the following > branch, vendor-sys/acpi

RE: ACPI Error on HP ProBook 430 G2

> -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 >

RE: ACPI Error on HP ProBook 430 G2

> 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 >

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 version 20161222. Hi Robert, From what I can see that patches have been pushed to the following branch, vendor-sys/acpica/20161222/, see: https://svnweb.freebsd.org/changeset/base/31

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 https://lists.freebsd.org/mailman/listin

RE: ACPI Error on HP ProBook 430 G2

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. > >

RE: ACPI Error on HP ProBook 430 G2

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

Re: ACPI Error on HP ProBook 430 G2

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 [Proce

Re: ACPI Error on HP ProBook 430 G2

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 [Processor] 0xf800043

Re: ACPI Error on HP ProBook 430 G2

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/exresop-111) ACPI Exception: AE_AML

Re: ACPI errors when booting laptop

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 dmesg when booti

Re: acpi suspend debugging techniques?

My Radeon card comes back from resume, but the backlight doesn't (it stays off). Think this patch might help with that? I was gonna start a separate thread to ask for help debugging my backlight issue... Thanks, Anthony On 09/03/15 16:06, Adrian Chadd wrote: > oioo, would you please put that ra

Re: acpi suspend debugging techniques?

On 04/09/2015 01:18, Jung-uk Kim wrote: > AFAICT, the whole suspend/resume code looks incomplete and very messy. > In fact, I'll be very surprised if it ever worked. :-( It does seem to work for me with the patch and other people report that the code works for them even without the patch. -- An

Re: acpi suspend debugging techniques?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/03/2015 18:30, David Wolfskill wrote: > [Much trimming, both of older content and recipient addresses -- > dhw] > > On Thu, Sep 03, 2015 at 06:18:52PM -0400, Jung-uk Kim wrote: >> ... AFAICT, the whole suspend/resume code looks incomplete and

Re: acpi suspend debugging techniques?

On 04/09/2015 01:29, Anthony Jenkins wrote: > My Radeon card comes back from resume, but the backlight doesn't (it > stays off). Think this patch might help with that? Likely not, but who knows. > I was gonna start a > separate thread to ask for help debugging my backlight issue... -- Andriy

Re: acpi suspend debugging techniques?

[Much trimming, both of older content and recipient addresses -- dhw] On Thu, Sep 03, 2015 at 06:18:52PM -0400, Jung-uk Kim wrote: > ... > AFAICT, the whole suspend/resume code looks incomplete and very messy. > In fact, I'll be very surprised if it ever worked. :-( > > Jung-uk Kim > ... While

Re: acpi suspend debugging techniques?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/03/2015 13:50, Andriy Gapon wrote: > On 31/08/2015 11:53, Adrian Chadd wrote: >> Try disabling hardware one at a time. Ie, unload usb; unload >> wifi; leave kms loaded for mostly obvious reasons. > > Adrian, Garrett, > > thank you very much f

Re: acpi suspend debugging techniques?

oioo, would you please put that radeon patch into a review? I have an older machine with a radeon card in it that doesn't yet suspend/resume; I can now test it out! -a On 3 September 2015 at 10:50, Andriy Gapon wrote: > On 31/08/2015 11:53, Adrian Chadd wrote: >> Try disabling hardware one at

Re: acpi suspend debugging techniques?

On 31/08/2015 11:53, Adrian Chadd wrote: > Try disabling hardware one at a time. Ie, unload usb; unload wifi; > leave kms loaded for mostly obvious reasons. Adrian, Garrett, thank you very much for your tips. Turned out that it was radeonkms that was causing the problem :-) BTW, here is another

Re: acpi suspend debugging techniques?

hi, Try disabling hardware one at a time. Ie, unload usb; unload wifi; leave kms loaded for mostly obvious reasons. I hit a few of these which turned out to be an issue in the suspend path of a driver - and once I found it was the USB hardware but the BIOS itself that was hanging - FreeBSD put US

Re: acpi suspend debugging techniques?

> On Aug 30, 2015, at 23:13, Andriy Gapon wrote: > > > I would appreciate any pointers at how to debug an ACPI suspend problem that > I have. > > What I have so far. The system hangs when I try to suspend it and it gets > reset > by a watchdog. Setting debug.acpi.suspend_bounce=1 does not

Re: ACPI Lenovo X121e (Model 3045-79G, i3, HD3000) Suspend and LCD Brightness

Hello Kevin, Zitat von Kevin Oberman : Can't help with suspend/resume, but I can point you to the brightness solution. This is probably the same issue that impacts most recent Lenovo laptops. If so, there is a fix in the thread titled "Fixing X220 Video The Right Way" on this (acpi@) mailing li

Re: ACPI Lenovo X121e (Model 3045-79G, i3, HD3000) Suspend and LCD Brightness

Hello Kevin, Zitat von Kevin Oberman : Can't help with suspend/resume, but I can point you to the brightness solution. This is probably the same issue that impacts most recent Lenovo laptops. If so, there is a fix in the thread titled "Fixing X220 Video The Right Way" on this (acpi@) mailing l

Re: ACPI Lenovo X121e (Model 3045-79G, i3, HD3000) Suspend and LCD Brightness

On Sat, Jul 6, 2013 at 11:59 AM, Matthias Petermann wrote: > Hello, > > on a Lenovo X121e (Model 3045-79G, i3, HD3000) I try FreeBSD since 9.1. > Wifi, LAN, Audio, USB peripherials and Video (with KMS patch) just working > fine. Anyway, there are some open items: > > * LCD brightness control doesn

Re: acpi resume related patch

On Mon, Jan 28, 2013 at 10:55 AM, John Baldwin wrote: > On Saturday, January 26, 2013 9:18:57 am Andriy Gapon wrote: >> on 25/01/2013 18:08 Andriy Gapon said the following: >> > on 25/01/2013 15:51 John Baldwin said the following: >> >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: >>

Re: ACPI panic on unplugging the power cord.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-26 11:58:16 -0500, Pawel Jakub Dawidek wrote: > On Fri, Jan 25, 2013 at 04:19:44PM -0500, Jung-uk Kim wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 2013-01-25 04:26:02 -0500, Pawel Jakub Dawidek wrote: >>> On Thu, Jan 24,

Re: acpi resume related patch

On Saturday, January 26, 2013 9:18:57 am Andriy Gapon wrote: > on 25/01/2013 18:08 Andriy Gapon said the following: > > on 25/01/2013 15:51 John Baldwin said the following: > >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: > >>> > >>> If you have ACPI suspend/resume working, if it use

Re: acpi resume related patch

On Mon, Jan 28, 2013 at 03:40:18PM +0200, Andriy Gapon wrote: > on 28/01/2013 15:24 Pawel Jakub Dawidek said the following: > > On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: > >> on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > >>> FYI, it doesn't change anything for me

Re: acpi resume related patch

on 28/01/2013 15:24 Pawel Jakub Dawidek said the following: > On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: >> on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: >>> FYI, it doesn't change anything for me. Resume seems to work, but >>> suspend just reset my laptop. >> >> So

Re: acpi resume related patch

On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: > on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > > FYI, it doesn't change anything for me. Resume seems to work, but > > suspend just reset my laptop. > > Sorry, I am a little confused by this description. > How can you k

Re: acpi resume related patch

on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > FYI, it doesn't change anything for me. Resume seems to work, but > suspend just reset my laptop. Sorry, I am a little confused by this description. How can you know that resume works if suspend resets the machine? -- Andriy Gapon ___

Re: acpi resume related patch

On Sat, Jan 26, 2013 at 04:18:57PM +0200, Andriy Gapon wrote: > on 25/01/2013 18:08 Andriy Gapon said the following: > > on 25/01/2013 15:51 John Baldwin said the following: > >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: > >>> > >>> If you have ACPI suspend/resume working, if it us

Re: acpi resume related patch

On Mon, Jan 28, 2013 at 10:16:43AM +0200, Andriy Gapon wrote: > on 28/01/2013 04:52 Glen Barber said the following: > > On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: > >> > >> If you have ACPI suspend/resume working, if it used to work but stopped > >> working > >> at some time, if

Re: acpi resume related patch

on 28/01/2013 04:52 Glen Barber said the following: > On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: >> >> If you have ACPI suspend/resume working, if it used to work but stopped >> working >> at some time, if it never worked, but you are still hoping, could you please >> test the f

Re: acpi resume related patch

On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: > > If you have ACPI suspend/resume working, if it used to work but stopped > working > at some time, if it never worked, but you are still hoping, could you please > test the following patch and report back? > > http://svn.freebsd.by

Re: acpi resume related patch

On Sun, Jan 27, 2013 at 09:32:28PM -0500, Glen Barber wrote: > On Sun, Jan 27, 2013 at 06:22:28PM -0800, Kevin Oberman wrote: > > Very much the same on my ThinkPad T520. Suspend looks fine. Resume > > turns on the backlight, but that's about it. No wireless and no > > display. The power light conti

Re: acpi resume related patch

On Sun, Jan 27, 2013 at 06:22:28PM -0800, Kevin Oberman wrote: > Very much the same on my ThinkPad T520. Suspend looks fine. Resume > turns on the backlight, but that's about it. No wireless and no > display. The power light continues to pulse, indicating the system > still considers itself suspend

  1   2   3   4   5   6   7   8   9   >