RE: ACPI Error on HP ProBook 430 G2

r 21, 2016 3:15 AM > To: 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 1220T1734, O. Hartmann wrote: > > Am Tue,

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 <zakharov...@gmail.com> schrieb: Hello! Some time ago new ACPI messages appeared on console and in /var/log/messages. Like these: ACPI Error: Neede

Re: ACPI Error on HP ProBook 430 G2

On 1220T1734, O. Hartmann wrote: > Am Tue, 20 Dec 2016 18:09:20 +0300 > Vladimir Zakharov <zakharov...@gmail.com> schrieb: > > > Hello! > > > > Some time ago new ACPI messages appeared on console and in > > /var/log/messages. Like > > these: > &

Re: ACPI Error on HP ProBook 430 G2

Am Tue, 20 Dec 2016 18:09:20 +0300 Vladimir Zakharov <zakharov...@gmail.com> 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] 0xf800043b8

ACPI Error on HP ProBook 430 G2

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

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 <woods...@gmail.com> wrote: > Hi everyone, > > I get the follow

ACPI errors when booting laptop

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 ideas

Re: Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

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), disablin

Re: Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

> >> 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 FreeBSDx64 kernel: ACPI Error: No ins

Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

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

Re: Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

t 10-11 minutes after starting 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: A

Bug 209222 -r298793 automatic shutdown for "kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323)" and more under virtual box

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

failure with latest merged ACPI on virtualbox

/sys/GENERIC amd64 It's shutdown twice (without warning), logging the following to the messages file: Apr 28 17:08:14 testvm kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20160422/evevent-323) Apr 28 17:08:14 testvm kernel: ACPI Error: No installed handler

Weird ACPI/DRM messages on -current

Hi, I'm using 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287497: Sun Sep 6 17:10:22 CEST 2015 on HP Folio 9470m. After last ports upgrade in /var/log/messages appear weird messages: Apr 28 06:31:10 dork kernel: error: [drm:pid9:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer Apr

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?

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

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?

-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

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?

--- >> >> However, I am not sure about an exact mechanism of the hard system hang that >> I >> experienced without the patch. >> >> BTW, I noticed that only very few drivers make explicit calls to >> pci_set_powerstate and pci_save_state/pci_restore_state. >>

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

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

acpi suspend debugging techniques?

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 make any difference, so the hang happens before the final sleep code

Re: acpi suspend debugging techniques?

> On Aug 30, 2015, at 23:13, Andriy Gapon <a...@freebsd.org> 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 > r

Re: acpi suspend debugging techniques?

USB hardware into S3, but the ACPI BIOS requested S2 and just hung if we had USB in S3. :( -adrian On 30 August 2015 at 23:33, Garrett Cooper <yaneurab...@gmail.com> wrote: > >> On Aug 30, 2015, at 23:13, Andriy Gapon <a...@freebsd.org> wrote: >> >> >>

Re: Weird ACPI/DRM messages on -current

On Fri, Feb 06, 2015 at 05:10:24PM +, Poul-Henning Kamp wrote: Thinkpad T430s: 11.0-CURRENT #15 r278283: Thu Feb 5 22:45:26 UTC 2015 Anybody know what this means ? There is no public documentation about renderer power and clock management. It seems that NDA'ed doc does not contain it

Re: Weird ACPI/DRM messages on -current

On 2015-02-06 12:10, Poul-Henning Kamp wrote: Thinkpad T430s: 11.0-CURRENT #15 r278283: Thu Feb 5 22:45:26 UTC 2015 Anybody know what this means ? Feb 6 17:05:58 critter kernel: error: [drm:pid1090:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS

Re: Weird ACPI/DRM messages on -current

On Feb 6, 2015, at 9:10, Poul-Henning Kamp p...@phk.freebsd.dk wrote: Thinkpad T430s: 11.0-CURRENT #15 r278283: Thu Feb 5 22:45:26 UTC 2015 Anybody know what this means ? Feb 6 17:05:58 critter kernel: error: [drm:pid1090:gen6_sanitize_pm] *ERROR* Power management discrepancy:

Re: Weird ACPI/DRM messages on -current

Can someone just go digging through the include files to see what the difference in bits are? This may be related to increased power usage that's been reported. -a On 6 February 2015 at 13:06, Allan Jude allanj...@freebsd.org wrote: On 2015-02-06 12:10, Poul-Henning Kamp wrote: Thinkpad

Re: Weird ACPI/DRM messages on -current

On Fri, Feb 6, 2015 at 2:00 PM, Adrian Chadd adr...@freebsd.org wrote: Can someone just go digging through the include files to see what the difference in bits are? This may be related to increased power usage that's been reported. -a It's defined in /sys/dev/drm2/i915/i915_reg.h.

Weird ACPI/DRM messages on -current

Thinkpad T430s: 11.0-CURRENT #15 r278283: Thu Feb 5 22:45:26 UTC 2015 Anybody know what this means ? Feb 6 17:05:58 critter kernel: error: [drm:pid1090:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1907, was 1900 Feb 6 17:06:12 critter

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

+1. ThinkPad T420 with nvidia discrete GPU, amd64 using memstick.img dd'ed to USB memstick. (So UEFI boot.) *Vanilla r276247 doesn't boot. No panic, just hang in allocating resource for pcib. Sorry for not recording exact message. *Reverting r276064 alone from r276247 helped. All other

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

El 29/12/14 a les 23.49, Jakob Alvermark ha escrit: On Mon, December 29, 2014 20:12, Marius Strobl wrote: On Mon, Dec 29, 2014 at 05:55:28PM +0100, Roger Pau Monné wrote: El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello, Sorry for not noticing this earlier, I've been without a

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Tue, December 30, 2014 13:39, Roger Pau Monné wrote: El 29/12/14 a les 23.49, Jakob Alvermark ha escrit: On Mon, December 29, 2014 20:12, Marius Strobl wrote: On Mon, Dec 29, 2014 at 05:55:28PM +0100, Roger Pau Monné wrote: El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello,

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

El 28/12/14 a les 22.37, Adrian Chadd ha escrit: Hah sweet! You found the commit! Would you please file a PR so it doesn't get lost? Thanks! -adrian On 28 December 2014 at 12:09, Ian Lepore i...@freebsd.org wrote: On Sun, 2014-12-28 at 20:57 +0100, O. Hartmann wrote: Am Fri,

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello, Sorry for not noticing this earlier, I've been without a computer for some days. Do you get a panic message, or the system just freezes? Can you please post the full boot output with boot_verbose enabled? I'm not able to reproduce

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Mon, Dec 29, 2014 at 05:55:28PM +0100, Roger Pau Monné wrote: El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello, Sorry for not noticing this earlier, I've been without a computer for some days. Do you get a panic message, or the system just freezes? Can you please post

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Mon, Dec 29, 2014 at 08:12:42PM +0100, Marius Strobl wrote: On Mon, Dec 29, 2014 at 05:55:28PM +0100, Roger Pau Monné wrote: El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello, Sorry for not noticing this earlier, I've been without a computer for some days. Do you get a

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Mon, December 29, 2014 20:12, Marius Strobl wrote: On Mon, Dec 29, 2014 at 05:55:28PM +0100, Roger Pau Monné wrote: El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: Hello, Sorry for not noticing this earlier, I've been without a computer for some days. Do you get a panic message,

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Am Fri, 26 Dec 2014 12:23:42 -0700 Ian Lepore i...@freebsd.org schrieb: On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote: On 26 December 2014 at 04:01, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd adr...@freebsd.org schrieb:

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Ian Lepore ian at freebsd.org writes: On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote: On 26 December 2014 at 04:01, O. Hartmann ohartman at zedat.fu- berlin.de wrote: Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd adrian at freebsd.org schrieb: Would you be able to narrow

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Sun, 2014-12-28 at 20:57 +0100, O. Hartmann wrote: Am Fri, 26 Dec 2014 12:23:42 -0700 Ian Lepore i...@freebsd.org schrieb: On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote: On 26 December 2014 at 04:01, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am Thu, 25 Dec 2014

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Hah sweet! You found the commit! Would you please file a PR so it doesn't get lost? Thanks! -adrian On 28 December 2014 at 12:09, Ian Lepore i...@freebsd.org wrote: On Sun, 2014-12-28 at 20:57 +0100, O. Hartmann wrote: Am Fri, 26 Dec 2014 12:23:42 -0700 Ian Lepore i...@freebsd.org

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd adr...@freebsd.org schrieb: Would you be able to narrow it down to a small range of commits? that'll make it easier to chase down. :) Thanks! -adrian On 25 December 2014 at 10:42, O. Hartmann ohart...@zedat.fu-berlin.de wrote:

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On 26 December 2014 at 04:01, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd adr...@freebsd.org schrieb: Would you be able to narrow it down to a small range of commits? that'll make it easier to chase down. :) Thanks! -adrian On 25

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote: On 26 December 2014 at 04:01, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd adr...@freebsd.org schrieb: Would you be able to narrow it down to a small range of commits? that'll make

r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Since 23rd's update of CURRENT, the kernel fails to boot on systems that boot via EFI. Systems with legacy booting seem not to be affected. I just ran today into the problem updating a notebook with a Intel Haswell Intel i5-4200M CPU (Haswell) on a Lenovo ThinkPad E540, bboting via UEFI,

Re: r276200: EFI boot failure: kernel stops booting at pci0: ACPI PCI bus on pcib0

Would you be able to narrow it down to a small range of commits? that'll make it easier to chase down. :) Thanks! -adrian On 25 December 2014 at 10:42, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Since 23rd's update of CURRENT, the kernel fails to boot on systems that boot via EFI.

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 2014-11-17 08:58, Dag-Erling Smørgrav wrote: Dag-Erling Smørgrav d...@des.no writes: Steve Kargl s...@troutmask.apl.washington.edu writes: I'll try that tomorrow. But, I now know that this is related to using hal from ports. If I comment out both enable_dbus and enable_hal in

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote: On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: On 11/13/14

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: Is there a 'random: device_detach():' missing between the 'umass0' and 'da0' messages in the last 4 lines. No. At attach time, the RNG grabs some probe entropy. At detach time it does nothing. M -- Mark R V

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote: On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: Is there a 'random: device_detach():' missing between the 'umass0' and 'da0' messages in the last 4 lines. No. At attach time, the RNG grabs some

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 16 Nov 2014, at 18:21, Ian Lepore i...@freebsd.org wrote: On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote: On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: Is there a 'random: device_detach():' missing between the 'umass0' and 'da0' messages in

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, 2014-11-16 at 18:23 +, Mark R V Murray wrote: On 16 Nov 2014, at 18:21, Ian Lepore i...@freebsd.org wrote: On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote: On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: Is there a 'random:

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 16 Nov 2014, at 18:31, Ian Lepore i...@freebsd.org wrote: The point I'm trying to make here is that you trimmed away the important part of the prior messages and replied only to the part where Steve's debugging efforts were somewhat speculating. The non-speculative part was where he

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, Nov 16, 2014 at 06:34:42PM +, Mark R V Murray wrote: On 16 Nov 2014, at 18:31, Ian Lepore i...@freebsd.org wrote: The point I'm trying to make here is that you trimmed away the important part of the prior messages and replied only to the part where Steve's debugging

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: I?m sorry my commit caused the problem. Nothing to be sorry about. This is -current after all. Thanks :-) I?m also trying to find out why, but I don?t know enough about USB or mass-storage devices to

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote: On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: If you have not read the entire thread, once the laptop keyboard and video output lock up, I can ssh into the laptop. If I run usbconfig,

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 11/16/14 20:03, Steve Kargl wrote: On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote: On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: If you have not read the entire thread, once the laptop keyboard and video output lock up, I can ssh into the

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote: On 11/16/14 20:03, Steve Kargl wrote: On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote: On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote: If you have not read the entire

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 11/16/14 20:29, Steve Kargl wrote: On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote: On 11/16/14 20:03, Steve Kargl wrote: On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote: On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote:

Re: USB locks up system -- WAS Re: shutdown or acpi problem

... or since you can ssh into the thing, try as root: procstat -ka -adrian On 16 November 2014 11:33, Hans Petter Selasky h...@selasky.org wrote: On 11/16/14 20:29, Steve Kargl wrote: On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote: On 11/16/14 20:03, Steve Kargl

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, Nov 16, 2014 at 04:34:38PM -0800, Adrian Chadd wrote: ... or since you can ssh into the thing, try as root: procstat -ka I'll try that tomorrow. But, I now know that this is related to using hal from ports. If I comment out both enable_dbus and enable_hal in /etc/rc.conf, the

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sun, Nov 16, 2014 at 08:33:15PM +0100, Hans Petter Selasky wrote: thread apply all bt That will give you the backtrace of all threads. Grep for usbconfig, and figure out which line is causing the problem in the kernel. Then look at the USB explore threads and see where they are stuck

Re: USB locks up system -- WAS Re: shutdown or acpi problem

Steve Kargl s...@troutmask.apl.washington.edu writes: I'll try that tomorrow. But, I now know that this is related to using hal from ports. If I comment out both enable_dbus and enable_hal in /etc/rc.conf, the system works as I would expect (ie., usb now works for unplugging devices!). I

Re: USB locks up system -- WAS Re: shutdown or acpi problem

Dag-Erling Smørgrav d...@des.no writes: Steve Kargl s...@troutmask.apl.washington.edu writes: I'll try that tomorrow. But, I now know that this is related to using hal from ports. If I comment out both enable_dbus and enable_hal in /etc/rc.conf, the system works as I would expect (ie.,

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: On 11/13/14 19:15, Steve Kargl wrote: On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: On 11/13/14 19:15, Steve Kargl wrote: On Thu, Nov 13, 2014 at 10:03:32AM -0800,

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote: On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: On 11/13/14

USB locks up system -- WAS Re: shutdown or acpi problem

) Origin=GenuineIntel Id=0x6fd Family=0x6 Model=0xf Stepping=13 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features

Re: USB locks up system -- WAS Re: shutdown or acpi problem

,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2000LM AMD Features2=0x1LAHF VT-x: (disabled in BIOS) HLT,PAUSE TSC: P-state invariant, performance statistics real memory

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote: On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote: I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now' work. I get to the end of

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote: On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote: I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On 11/13/14 19:15, Steve Kargl wrote: On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote: On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote: I have a kernel/world from r274273 sources, which is exhibiting a new

Re: USB locks up system -- WAS Re: shutdown or acpi problem

On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote: On 11/13/14 19:15, Steve Kargl wrote: On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote: On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote: On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:

shutdown or acpi problem

I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now' work. I get to the end of shutdown and see for example All buffers synced Uptime: 4h23m15s and then the laptop just sits there. It does not power off

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now' work. I get to the end of shutdown and see for example All

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote: I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now' work. I get to the end of shutdown and see for example All buffers synced Uptime:

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 03:12:46PM -0800, NGie Cooper wrote: On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: I have a kernel/world from r274273 sources, which is exhibiting a new issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'

Re: shutdown or acpi problem

On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl s...@troutmask.apl.washington.edu wrote On Wed, Nov 12, 2014 at 03:12:46PM -0800, NGie Cooper wrote: On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: I have a kernel/world from r274273 sources, which is

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote: On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl s...@troutmask.apl.washington.edu wrote I run 'make delete-old' and 'make delete-old-libs' after each installworld. In this case, I was upgrading from r271492 to r274273. The

Re: shutdown or acpi problem

On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl s...@troutmask.apl.washington.edu wrote On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote: On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl s...@troutmask.apl.washington.edu wrote I run 'make delete-old' and 'make delete-old-libs'

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 6:27 PM, Chris H bsd-li...@bsdforge.com wrote: ... How so? It's been necessary for as long as I can remember. Just to confirm, I looked to see if anything had changed: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html seems not. Do note; I'm

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 6:43 PM, NGie Cooper yaneurab...@gmail.com wrote: On Wed, Nov 12, 2014 at 6:27 PM, Chris H bsd-li...@bsdforge.com wrote: ... How so? It's been necessary for as long as I can remember. Just to confirm, I looked to see if anything had changed:

Re: shutdown or acpi problem

On Wed, Nov 12, 2014 at 06:27:13PM -0800, Chris H wrote: On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl s...@troutmask.apl.washington.edu wrote On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote: On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl s...@troutmask.apl.washington.edu

Re: [Xen-devel] [PATCH RFC 09/13] xen: change quality of the MADT ACPI enumerator

On 14/02/14 18:51, John Baldwin wrote: On Thursday, February 13, 2014 8:49:24 pm Andrew Cooper wrote: On 08/02/2014 21:42, John Baldwin wrote: On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote: Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can force the usage

Re: [PATCH RFC 10/13] xen: add ACPI bus to xen_nexus when running as Dom0

On 08/02/14 22:50, John Baldwin wrote: On Tuesday, December 24, 2013 12:20:59 PM Roger Pau Monne wrote: Also disable a couple of ACPI devices that are not usable under Dom0. Hmm, setting debug.acpi.disabled in this way is a bit hacky. It might be fine however if there's no way for the user

Re: [PATCH RFC 10/13] xen: add ACPI bus to xen_nexus when running as Dom0

On Friday, February 14, 2014 5:38:15 am Roger Pau Monné wrote: On 08/02/14 22:50, John Baldwin wrote: On Tuesday, December 24, 2013 12:20:59 PM Roger Pau Monne wrote: Also disable a couple of ACPI devices that are not usable under Dom0. Hmm, setting debug.acpi.disabled in this way

Re: [Xen-devel] [PATCH RFC 09/13] xen: change quality of the MADT ACPI enumerator

On Thursday, February 13, 2014 8:49:24 pm Andrew Cooper wrote: On 08/02/2014 21:42, John Baldwin wrote: On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote: Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can force the usage of the Xen mptable enumerator even

Re: [PATCH RFC 10/13] xen: add ACPI bus to xen_nexus when running as Dom0

On Tuesday, December 24, 2013 12:20:59 PM Roger Pau Monne wrote: Also disable a couple of ACPI devices that are not usable under Dom0. Hmm, setting debug.acpi.disabled in this way is a bit hacky. It might be fine however if there's no way for the user to set it before booting the kernel

Re: [PATCH RFC 09/13] xen: change quality of the MADT ACPI enumerator

On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote: Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can force the usage of the Xen mptable enumerator even when ACPI is detected. Hmm, so I think one question is why does the existing MADT parser not work

Re: [Xen-devel] [PATCH RFC 09/13] xen: change quality of the MADT ACPI enumerator

On 08/02/2014 21:42, John Baldwin wrote: On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote: Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can force the usage of the Xen mptable enumerator even when ACPI is detected. Hmm, so I think one question is why does

[PATCH RFC 09/13] xen: change quality of the MADT ACPI enumerator

Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can force the usage of the Xen mptable enumerator even when ACPI is detected. --- sys/x86/acpica/madt.c |2 +- sys/x86/xen/mptable.c |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sys/x86/acpica/madt.c

[PATCH RFC 10/13] xen: add ACPI bus to xen_nexus when running as Dom0

Also disable a couple of ACPI devices that are not usable under Dom0. --- sys/x86/xen/xen_nexus.c | 24 +--- 1 files changed, 21 insertions(+), 3 deletions(-) diff --git a/sys/x86/xen/xen_nexus.c b/sys/x86/xen/xen_nexus.c index 288e6b6..823b3bc 100644 --- a/sys/x86/xen

Re: amd64/181357: LCD Brightness Control not working on Lenovo X121e (ACPI issue?)

Hello, regarding this PR I made some further observation. Even the acpi_ec_write seems to not have any effect on the brightness, the values set to the appropriate register (IBM_EC_BRIGHTNESS 0x31) survive a reboot. Looks like the values are stored correctly, but EC doesn't care for them

Re: amd64/181357: LCD Brightness Control not working on Lenovo X121e (ACPI issue?)

On 24/08/2013 17:08, Matthias Petermann wrote: regarding this PR I made some further observation. Even the acpi_ec_write seems to not have any effect on the brightness, the values set to the appropriate register (IBM_EC_BRIGHTNESS 0x31) survive a reboot. My LCD brightness control stopped

Re: amd64/181357: LCD Brightness Control not working on Lenovo X121e (ACPI issue?)

Am 24.08.2013 20:02, schrieb Dominic Fandrey: My LCD brightness control stopped working when I switched to NEW_XORG with Intel KMS (on stable/9). It's the same issue when I run in console only mode (without Xorg, without KMS kernel module loaded). What Lenovo model are you using?

amd64/181358: Suspend to RAM not working correctly on Lenovo X121e (ACPI issue?)

Hello, regarding the issue mentioned in the subject (Lenovo Thinkpad X121e not able to resume after suspend to ram) there is finally some progress. I found this few months old discussion[1] on freebsd-acpi (related to Thinkpad X201): I had a similar problem. After syncing with FreeBSD 10

Re: FreeBSD-head hang when shutdown by ACPI with Intel GPU and new Xorg and SandyBridge

On Fri, 12 Jul 2013 18:05:47 +0200 Lars Engels lars.eng...@0x20.net wrote: On Fri, Jul 12, 2013 at 11:26:06AM +0100, David Chisnall wrote: On 12 Jul 2013, at 10:01, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: As the KMS code does not switch the display mode back, once X

Re: FreeBSD-head hang when shutdown by ACPI with Intel GPU and new Xorg and SandyBridge

As the KMS code does not switch the display mode back, once X with KMS starts, you can't get a console back. Is there any solution for this in the works? Johannes Lundberg BRILLIANTSERVICE CO., LTD. http://www.brilliantservice.co.jp On Wed, May 22, 2013 at 5:44 AM, Kevin Oberman

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