[Bug 172918] [pci] [suspend/resume] ACPI errors at suspend/resume

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172918

John Baldwin j...@freebsd.org changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED
 CC||j...@freebsd.org

--- Comment #2 from John Baldwin j...@freebsd.org ---
The incorrect Dx messages were due to a separate bug from the power resource
one mentioned above.  These messages were fixed in HEAD in 274386.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 102783] [acpi] hw.acpi has thermal controls backwards when external power connected at bootup

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=102783

John Baldwin j...@freebsd.org changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|In Progress |Closed
 CC||j...@freebsd.org

--- Comment #3 from John Baldwin j...@freebsd.org ---
This would be hard to debug without access to a system that exhibits the
problem.  It is possible that the power profile was incorrect, though if
anything it should be the other way around (the system defaults to assuming it
is in performance (i.e. non-battery) mode).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 198603] [acpi] HP ProBook 430 G2: can't change brightness via acpi_hp and acpi_video

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198603

John Baldwin j...@freebsd.org changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED
 CC||j...@freebsd.org

--- Comment #2 from John Baldwin j...@freebsd.org ---
It might also be useful to know if the recent opregion changes in i915kms fixes
this for you the way it fixes it for several thinkpads.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 181283] [acpi_ibm] acpi_ibm module is useless on ThinkPad W530

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181283

John Baldwin j...@freebsd.org changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #1 from John Baldwin j...@freebsd.org ---
Other thinkpads that use Intel integrated graphics are able to control LCD
brightness via the KMS module after r270516 in HEAD (merged to stable/10 in
279961 which is after 10.1).  However, those do not use acpi_ibm, but do work
with acpi_video.  On my x220 the following things appear to work in acpi_ibm:

'mute' sysctl (can write to it to mute, and the mute button change its state,
also writing to it changes the mute light)
'thinklight' sysctl
'fan_speed' sysctl

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 193671] [acpiconf] Extra whitespace at the end of the State: line

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193671

John Baldwin j...@freebsd.org changed:

   What|Removed |Added

 CC||j...@freebsd.org
 Status|New |In Progress

--- Comment #1 from John Baldwin j...@freebsd.org ---
Please see https://reviews.freebsd.org/D2243

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 193671] [acpiconf] Extra whitespace at the end of the State: line

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193671

Jung-uk Kim j...@freebsd.org changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #2 from Jung-uk Kim j...@freebsd.org ---
Created attachment 155290
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155290action=edit
A patch to test

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: How to know the system state if the system is going for halt or poweroff or reboot in FreeBSD

2015-04-06 Thread John Baldwin
On Thursday, March 26, 2015 01:54:45 AM Sibananda Sahu wrote:
 My requirement is to know the exact reason of shutdown, whether is it a
 power-off or a reboot call.
 
 And I can get the information from the “howto” variable that is passed to
 the kern_reboot() function call, but this variable is local to
 kern_reboot() only.

It is passed to the shutdown_* eventhandlers.  So if you register an 
eventhandler
you can get the howto argument that way.  ACPI uses this to power off the 
machine
for a power off request for example:

static void
acpi_shutdown_final(void *arg, int howto)
{
...
if ((howto  RB_POWEROFF) != 0) {
status = AcpiEnterSleepStatePrep(ACPI_STATE_S5);
}


-- 
John Baldwin
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

[Bug 152792] [acpica] [patch] move temperature conversion macros to a common header

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=152792

--- Comment #3 from Jung-uk Kim j...@freebsd.org ---
Generally, I am okay with the change.  However, I don't like TZ_KELVTOC*
macros.  These stuff should stay in acpi_thermal.c.  At least, TZ_KELVTOC()
macro should not be moved.  Also, I don't like TZ_* prefixes.  These macros
should be prefixed with something else.  Actually, I am not even sure whether
sysctl.h is the right file to put these misc. utility macros.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 193671] [acpiconf] Extra whitespace at the end of the State: line

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193671

--- Comment #5 from Jung-uk Kim j...@freebsd.org ---
(In reply to John Baldwin from comment #4)
No, it is not necessary because practically there is only one invalid value,
i.e., ACPI_BATT_STAT_DISCHARG | ACPI_BATT_STAT_CHARGING. :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


[Bug 193671] [acpiconf] Extra whitespace at the end of the State: line

2015-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193671

Jung-uk Kim j...@freebsd.org changed:

   What|Removed |Added

   Assignee|freebsd-acpi@FreeBSD.org|j...@freebsd.org
 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: HP Compaq CQ62/42 acpi

2015-04-06 Thread Da Rock

On 27/03/2015 21:54, Da Rock wrote:

acpi_hp0: HP ACPI-WMI Mapping on acpi_wmi0

acpi_hp0: HP event GUID detected, installing event handler
ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node 0xf80004372e80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Method parse/execution failed [\134_SB_.WMID.WMAD]
(Node 0xf80004372b80), AE_AML_BUFFER_LIMIT 
(20130823/psparse-553)

ACPI Error: Field [D128] at 1040 exceeds Buffer [NULL] size 160
(bits) (20130823/dsopcode-249)
ACPI Error: Method parse/execution failed [\134_SB_.WMID.HWMC]
(Node