Hello Samuel,
On Mon, 2016-05-23 at 20:30 -0500, Samuel Smith wrote:
> May 23 19:58:37 t61 laptop-mode: Module
> /usr/share/laptop-mode-tools/modules/wireless-ipw-power is not
> executable or is to be skipped.
> May 23 19:58:37 t61 laptop-mode: Module
> /usr/share/laptop-mode-tools/modules/wireless-iwl-power is not
> executable or is to be skipped.
> May 23 19:58:37 t61 laptop-mode: Module
> /usr/share/laptop-mode-tools/modules/wireless-power is not executable or
> is to be skipped.
Almost all shipped modules are disabled in your setup. Is that intentional ?
> May 23 19:58:37 t61 laptop-mode: Module
> /usr/local/lib/laptop-mode-tools/modules/* is not executable or is to be
> skipped.
> May 23 19:58:37 t61 laptop-mode: Module
> /usr/local/share/laptop-mode-tools/modules/* is not executable or is to
> be skipped.
> May 23 19:58:37 t61 laptop-mode: Module /etc/laptop-mode/modules/* is
> not executable or is to be skipped.
> May 23 19:58:37 t61 laptop-mode: Laptop Mode Tools invoked by parent: 1
> May 23 19:58:37 t61 laptop-mode: Determining power state from
> /sys/class/power_supply/AC/online.
> May 23 19:58:37 t61 laptop-mode: Not trying other options, already found
> a power supply.
> May 23 19:58:37 t61 laptop-mode: On AC power: Deactivating, because
> ENABLE_LAPTOP_MODE_ON_AC is not set.
> May 23 19:58:37 t61 laptop-mode: Laptop mode
> May 23 19:58:37 t61 laptop-mode: Checking if desired state is different
> from current state.
> May 23 19:58:37 t61 laptop-mode: enabled, not active [unchanged]
> May 23 19:58:37 t61 kernel: [81952.371690] thinkpad_acpi: EC reports
> that Thermal Table has changed
> May 23 19:58:37 t61 laptop-mode: Laptop Mode Tools invoked by parent: 1
> May 23 19:58:37 t61 laptop-mode: Determining power state from
> /sys/class/power_supply/AC/online.
> May 23 19:58:37 t61 laptop-mode: Not trying other options, already found
> a power supply.
> May 23 19:58:37 t61 laptop-mode: Battery level polling is disabled.
> May 23 19:58:37 t61 laptop-mode: Prelim lock acquisition on descriptor 8
> with pid 25918
> May 23 19:58:37 t61 laptop-mode: Prelim lock acquisition on descriptor 9
> with pid 25918
> May 23 19:58:37 t61 laptop-mode: Now invoking lmt_main_function with
> arguments --
LMT is being invoked.
Because most (or all) your modules are disabled, it doesn't seem to be applying
any change.
> May 23 19:58:37 t61 laptop-mode: Laptop Mode Tools invoked by parent: 1
> May 23 19:58:37 t61 laptop-mode: Determining power state from
> /sys/class/power_supply/AC/online.
> May 23 19:58:37 t61 laptop-mode: Not trying other options, already found
> a power supply.
> May 23 19:58:37 t61 laptop-mode: On AC power: Deactivating, because
> ENABLE_LAPTOP_MODE_ON_AC is not set.
> May 23 19:58:37 t61 laptop-mode: Laptop mode
> May 23 19:58:37 t61 laptop-mode: Checking if desired state is different
> from current state.
> May 23 19:58:37 t61 laptop-mode: enabled, not active [unchanged]
>
>
>
> Looking into /lib/udev/rules.d/99-laptop-mode.rules:
> ACTION=="change", SUBSYSTEM=="power_supply",
> ENV{POWER_SUPPLY_NAME}=="|AC|ACAD", RUN+="lmt-udev auto"
> ACTION=="add|remove", SUBSYSTEM=="machinecheck", RUN+="lmt-udev auto"
> ACTION=="add|remove", SUBSYSTEM=="usb", RUN+="lmt-udev force
> modules=runtime-pm devices=%k"
>
> This shows that LMT will be executed at least twice, since this is a
> power event with a simultaneous USB event (since most docking stations
> have a built in usb hub)
>
Don't worry about it. Even if both the events trigger at the same time, only 1
would be allowed to execute as the other will not be able to acquire the lock.
> Above the print statement in laptop_mode:
> log "VERBOSE" "Module $SCRIPT is not executable or is to be skipped."
>
> I added "echo $@", and in all cases it printed:
> "force modules=runtime-pm devices=1-1.5.5.2:1.0"
> many times in a row.
>
Must be because that subsystem generated too many events. But like I said, LMT
will not honor all events in a sudden burst. At max only 2 events will be
processed in a burst.
> Commenting out (not the right way of course) the add|remove events for
> usb solved this problem and LMT sets the correct states across AC,
> battery, and Dock now.
That is odd. I'd be interested to know how you came to this conclusion.
What init service are you using?
Can you provide LMT's output based on the init system you are using ?
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
