From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 9 17:20:13 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C9CA106564A for ; Mon, 9 Apr 2012 17:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EE7F88FC17 for ; Mon, 9 Apr 2012 17:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q39HKCUu087748 for ; Mon, 9 Apr 2012 17:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q39HKCcv087747; Mon, 9 Apr 2012 17:20:12 GMT (envelope-from gnats) Resent-Date: Mon, 9 Apr 2012 17:20:12 GMT Resent-Message-Id: <201204091720.q39HKCcv087747@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, zGhdBzhtDl Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79CFC106564A for ; Mon, 9 Apr 2012 17:19:24 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 635A18FC12 for ; Mon, 9 Apr 2012 17:19:24 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q39HJOgr097542 for ; Mon, 9 Apr 2012 17:19:24 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q39HJN3W097541; Mon, 9 Apr 2012 17:19:23 GMT (envelope-from nobody) Message-Id: <201204091719.q39HJN3W097541@red.freebsd.org> Date: Mon, 9 Apr 2012 17:19:23 GMT From: zGhdBzhtDl To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: misc/166793: cDPVgNXLrxPGgBB X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 17:20:13 -0000 >Number: 166793 >Category: misc >Synopsis: cDPVgNXLrxPGgBB >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 09 17:20:12 UTC 2012 >Closed-Date: >Last-Modified: >Originator: zGhdBzhtDl >Release: JQVxbplF >Organization: Solfacym >Environment: “discharging” (with the “Remaining capacity” asnreicing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf –i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says “Laptop is fully charged”, while acpiconf –i 0 says:“Design capacity:65000 mWhLast full capacity:65700 mWhTechnology:secondary (rechargeable)Design voltage:10950 mVCapacity (warn):250 mWhCapacity (low):100 mWhLow/warn granularity:10 mWhWarn/full granularity:10 mWhModel number:bq20z451077VCDEF0123456789ABCDESerial number:Type:LIONz451077VCDEF0123456789ABCDEOEM info:SMPNz451077VCDEF0123456789ABCDEState:highRemaining capacity:95%Remaining time:unknownPresent rate:24127 mWPresent voltage:12161 mV“which is a whole lot better than it would be without thedebug.acpi.max_tasks=“XXXX” in /boot/loader.conf.My sysctl now r eads (with results affected by the debug.acpi.max_tasks=“128”):hw.acpi.supported_sleep_state: S3 S4 S5hw.acpi.power_button_state: S5hw.acpi.sleep_button_state: S3hw.acpi.lid_switch_state: NONEhw.acpi.standby_state: NONEhw.acpi.suspend_state: S3hw.acpi.sleep_delay: 1hw.acpi.s4bios: 0hw.acpi.verbose: 0hw.acpi.disable_on_reboot: 0hw.acpi.handle_reboot: 1hw.acpi.reset_video: 0hw.acpi.cpu.cx_lowest: C1hw.acpi.acline: 1hw.acpi.battery.life: 93hw.acpi.battery.time: –1hw.acpi.battery.state: 0hw.acpi.battery.units: 1hw.acpi.battery.info_expire: 5So, to make a long story short, all I’ve really done is to addbebug.acpi.max_tasks=“128” to /boot/loader.conf. (I’ve tried to increase that number to 2048 without much visible effect). >Description: “discharging” (with the “Remaining capacity” asnreicing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf –i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says “Laptop is fully charged”, while acpiconf –i 0 says:“Design capacity:65000 mWhLast full capacity:65700 mWhTechnology:secondary (rechargeable)Design voltage:10950 mVCapacity (warn):250 mWhCapacity (low):100 mWhLow/warn granularity:10 mWhWarn/full granularity:10 mWhModel number:bq20z451077VCDEF0123456789ABCDESerial number:Type:LIONz451077VCDEF0123456789ABCDEOEM info:SMPNz451077VCDEF0123456789ABCDEState:highRemaining capacity:95%Remaining time:unknownPresent rate:24127 mWPresent voltage:12161 mV“which is a whole lot better than it would be without thedebug.acpi.max_tasks=“XXXX” in /boot/loader.conf.My sysctl now reads (with res ults affected by the debug.acpi.max_tasks=“128”):hw.acpi.supported_sleep_state: S3 S4 S5hw.acpi.power_button_state: S5hw.acpi.sleep_button_state: S3hw.acpi.lid_switch_state: NONEhw.acpi.standby_state: NONEhw.acpi.suspend_state: S3hw.acpi.sleep_delay: 1hw.acpi.s4bios: 0hw.acpi.verbose: 0hw.acpi.disable_on_reboot: 0hw.acpi.handle_reboot: 1hw.acpi.reset_video: 0hw.acpi.cpu.cx_lowest: C1hw.acpi.acline: 1hw.acpi.battery.life: 93hw.acpi.battery.time: –1hw.acpi.battery.state: 0hw.acpi.battery.units: 1hw.acpi.battery.info_expire: 5So, to make a long story short, all I’ve really done is to addbebug.acpi.max_tasks=“128” to /boot/loader.conf. (I’ve tried to increase that number to 2048 without much visible effect). >How-To-Repeat: “discharging” (with the “Remaining capacity” asnreicing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf –i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says “Laptop is fully charged”, while acpiconf –i 0 says:“Design capacity:65000 mWhLast full capacity:65700 mWhTechnology:secondary (rechargeable)Design voltage:10950 mVCapacity (warn):250 mWhCapacity (low):100 mWhLow/warn granularity:10 mWhWarn/full granularity:10 mWhModel number:bq20z451077VCDEF0123456789ABCDESerial number:Type:LIONz451077VCDEF0123456789ABCDEOEM info:SMPNz451077VCDEF0123456789ABCDEState:highRemaining capacity:95%Remaining time:unknownPresent rate:24127 mWPresent voltage:12161 mV“which is a whole lot better than it would be without thedebug.acpi.max_tasks=“XXXX” in /boot/loader.conf.My sysctl now reads (with res ults affected by the debug.acpi.max_tasks=“128”):hw.acpi.supported_sleep_state: S3 S4 S5hw.acpi.power_button_state: S5hw.acpi.sleep_button_state: S3hw.acpi.lid_switch_state: NONEhw.acpi.standby_state: NONEhw.acpi.suspend_state: S3hw.acpi.sleep_delay: 1hw.acpi.s4bios: 0hw.acpi.verbose: 0hw.acpi.disable_on_reboot: 0hw.acpi.handle_reboot: 1hw.acpi.reset_video: 0hw.acpi.cpu.cx_lowest: C1hw.acpi.acline: 1hw.acpi.battery.life: 93hw.acpi.battery.time: –1hw.acpi.battery.state: 0hw.acpi.battery.units: 1hw.acpi.battery.info_expire: 5So, to make a long story short, all I’ve really done is to addbebug.acpi.max_tasks=“128” to /boot/loader.conf. (I’ve tried to increase that number to 2048 without much visible effect). >Fix: “discharging” (with the “Remaining capacity” asnreicing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf –i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says “Laptop is fully charged”, while acpiconf –i 0 says:“Design capacity:65000 mWhLast full capacity:65700 mWhTechnology:secondary (rechargeable)Design voltage:10950 mVCapacity (warn):250 mWhCapacity (low):100 mWhLow/warn granularity:10 mWhWarn/full granularity:10 mWhModel number:bq20z451077VCDEF0123456789ABCDESerial number:Type:LIONz451077VCDEF0123456789ABCDEOEM info:SMPNz451077VCDEF0123456789ABCDEState:highRemaining capacity:95%Remaining time:unknownPresent rate:24127 mWPresent voltage:12161 mV“which is a whole lot better than it would be without thedebug.acpi.max_tasks=“XXXX” in /boot/loader.conf.My sysctl now reads (with res ults affected by the debug.acpi.max_tasks=“128”):hw.acpi.supported_sleep_state: S3 S4 S5hw.acpi.power_button_state: S5hw.acpi.sleep_button_state: S3hw.acpi.lid_switch_state: NONEhw.acpi.standby_state: NONEhw.acpi.suspend_state: S3hw.acpi.sleep_delay: 1hw.acpi.s4bios: 0hw.acpi.verbose: 0hw.acpi.disable_on_reboot: 0hw.acpi.handle_reboot: 1hw.acpi.reset_video: 0hw.acpi.cpu.cx_lowest: C1hw.acpi.acline: 1hw.acpi.battery.life: 93hw.acpi.battery.time: –1hw.acpi.battery.state: 0hw.acpi.battery.units: 1hw.acpi.battery.info_expire: 5So, to make a long story short, all I’ve really done is to addbebug.acpi.max_tasks=“128” to /boot/loader.conf. (I’ve tried to increase that number to 2048 without much visible effect). >Release-Note: >Audit-Trail: >Unformatted: