Disable GPE ACPI interrupts on boot?ACPI problem with recent kernelsACPI conflicts with ACPI region SMRGDebug...
Sci-fi book (no magic, hyperspace jumps, blind protagonist)
How to play a D major chord lower than the open E major chord on guitar?
What do I need to see before Spider-Man: Far From Home?
Was the 45.9°C temperature in France in June 2019 the highest ever recorded in France?
Was I wrongfully denied boarding for having a Schengen visa issued from the second country on my itinerary?
PhD: When to quit and move on?
Is conquering your neighbors to fight a greater enemy a valid strategy?
How to deal with a Murder Hobo Paladin?
Is there a standard definition of the "stall" phenomena?
Can a USB hub be used to access a drive from 2 devices?
How serious is plagiarism in a master’s thesis?
Why do most airliners have underwing engines, while business jets have rear-mounted engines?
How would a sea turtle end up on its back?
Do the 26 richest billionaires own as much wealth as the poorest 3.8 billion people?
Why does mean tend be more stable in different samples than median?
Advice for making/keeping shredded chicken moist?
Why would "dead languages" be the only languages that spells could be written in?
How important is it for multiple POVs to run chronologically?
What is the highest level of accuracy in motion control a Victorian society could achieve?
Is it possible to spoof an IP address to an exact number?
Sleepy tired vs physically tired
How did the IEC decide to create kibibytes?
What can a novel do that film and TV cannot?
Has there ever been a cold war other than between the U.S. and the U.S.S.R.?
Disable GPE ACPI interrupts on boot?
ACPI problem with recent kernelsACPI conflicts with ACPI region SMRGDebug an ACPI resume failureHow do I remove acpi Warning on boot?May ACPI wakeup states be modified from the kernel?Fedora 24 : acpi=off --> Can't use graphic card nvidiaACPI problem with MSI laptopSerial port only recognized with acpi=off boot flagACPI region does not cover the entire command/response bufferCan't boot kali linux first time (dual boot) UTMP; TMDS & ACPI errors
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
If I look for ACPI interrupts, I find:
/sys/firmware/acpi/interrupts/sci: 55414
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 invalid
/sys/firmware/acpi/interrupts/gpe02: 0 invalid
/sys/firmware/acpi/interrupts/gpe03: 0 invalid
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 enabled
/sys/firmware/acpi/interrupts/gpe07: 0 enabled
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 enabled
/sys/firmware/acpi/interrupts/gpe11: 0 invalid
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 invalid
/sys/firmware/acpi/interrupts/gpe14: 1 enabled
/sys/firmware/acpi/interrupts/gpe15: 0 invalid
/sys/firmware/acpi/interrupts/gpe16: 1 enabled
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 54753 enabled
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 invalid
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid
/sys/firmware/acpi/interrupts/gpe20: 0 invalid
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 enabled
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid
/sys/firmware/acpi/interrupts/gpe38: 0 invalid
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid
/sys/firmware/acpi/interrupts/gpe39: 0 invalid
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled
/sys/firmware/acpi/interrupts/gpe_all: 55414
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid
I wrote a service script to disable this on boot:
#!/bin/bash
### BEGIN INIT INFO
# Provides: disable-gpe17
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
logger -t gpe17 -s "Disabling gpe17 interrupts..."
/etc/pm/sleep.d/30_disable_gpe17 thaw
exit 0
This calls my PM script:
#!/bin/sh
echo 0 > /sys/firmware/acpi/interrupts/gpe17 2>/dev/null
I've made both scripts executable, and added disable-gpe17 to the boot scripts with:
sudo update-rc.d disable-gpe17 defaults
When I look in my boot log, I don't see a record of the syslog entry stating that gpe17 has been disabled.
Is there a better, perhaps udev, way of disabling certain interrupts on boot? If not, why is my service script not running on boot?
I'm on a MacBook Pro 11,5 running kernel 3.19 with Ubuntu 14.04.
acpi firmware
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
add a comment |
If I look for ACPI interrupts, I find:
/sys/firmware/acpi/interrupts/sci: 55414
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 invalid
/sys/firmware/acpi/interrupts/gpe02: 0 invalid
/sys/firmware/acpi/interrupts/gpe03: 0 invalid
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 enabled
/sys/firmware/acpi/interrupts/gpe07: 0 enabled
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 enabled
/sys/firmware/acpi/interrupts/gpe11: 0 invalid
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 invalid
/sys/firmware/acpi/interrupts/gpe14: 1 enabled
/sys/firmware/acpi/interrupts/gpe15: 0 invalid
/sys/firmware/acpi/interrupts/gpe16: 1 enabled
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 54753 enabled
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 invalid
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid
/sys/firmware/acpi/interrupts/gpe20: 0 invalid
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 enabled
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid
/sys/firmware/acpi/interrupts/gpe38: 0 invalid
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid
/sys/firmware/acpi/interrupts/gpe39: 0 invalid
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled
/sys/firmware/acpi/interrupts/gpe_all: 55414
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid
I wrote a service script to disable this on boot:
#!/bin/bash
### BEGIN INIT INFO
# Provides: disable-gpe17
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
logger -t gpe17 -s "Disabling gpe17 interrupts..."
/etc/pm/sleep.d/30_disable_gpe17 thaw
exit 0
This calls my PM script:
#!/bin/sh
echo 0 > /sys/firmware/acpi/interrupts/gpe17 2>/dev/null
I've made both scripts executable, and added disable-gpe17 to the boot scripts with:
sudo update-rc.d disable-gpe17 defaults
When I look in my boot log, I don't see a record of the syslog entry stating that gpe17 has been disabled.
Is there a better, perhaps udev, way of disabling certain interrupts on boot? If not, why is my service script not running on boot?
I'm on a MacBook Pro 11,5 running kernel 3.19 with Ubuntu 14.04.
acpi firmware
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
add a comment |
If I look for ACPI interrupts, I find:
/sys/firmware/acpi/interrupts/sci: 55414
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 invalid
/sys/firmware/acpi/interrupts/gpe02: 0 invalid
/sys/firmware/acpi/interrupts/gpe03: 0 invalid
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 enabled
/sys/firmware/acpi/interrupts/gpe07: 0 enabled
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 enabled
/sys/firmware/acpi/interrupts/gpe11: 0 invalid
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 invalid
/sys/firmware/acpi/interrupts/gpe14: 1 enabled
/sys/firmware/acpi/interrupts/gpe15: 0 invalid
/sys/firmware/acpi/interrupts/gpe16: 1 enabled
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 54753 enabled
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 invalid
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid
/sys/firmware/acpi/interrupts/gpe20: 0 invalid
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 enabled
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid
/sys/firmware/acpi/interrupts/gpe38: 0 invalid
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid
/sys/firmware/acpi/interrupts/gpe39: 0 invalid
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled
/sys/firmware/acpi/interrupts/gpe_all: 55414
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid
I wrote a service script to disable this on boot:
#!/bin/bash
### BEGIN INIT INFO
# Provides: disable-gpe17
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
logger -t gpe17 -s "Disabling gpe17 interrupts..."
/etc/pm/sleep.d/30_disable_gpe17 thaw
exit 0
This calls my PM script:
#!/bin/sh
echo 0 > /sys/firmware/acpi/interrupts/gpe17 2>/dev/null
I've made both scripts executable, and added disable-gpe17 to the boot scripts with:
sudo update-rc.d disable-gpe17 defaults
When I look in my boot log, I don't see a record of the syslog entry stating that gpe17 has been disabled.
Is there a better, perhaps udev, way of disabling certain interrupts on boot? If not, why is my service script not running on boot?
I'm on a MacBook Pro 11,5 running kernel 3.19 with Ubuntu 14.04.
acpi firmware
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
If I look for ACPI interrupts, I find:
/sys/firmware/acpi/interrupts/sci: 55414
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 invalid
/sys/firmware/acpi/interrupts/gpe02: 0 invalid
/sys/firmware/acpi/interrupts/gpe03: 0 invalid
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 enabled
/sys/firmware/acpi/interrupts/gpe07: 0 enabled
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 enabled
/sys/firmware/acpi/interrupts/gpe11: 0 invalid
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 invalid
/sys/firmware/acpi/interrupts/gpe14: 1 enabled
/sys/firmware/acpi/interrupts/gpe15: 0 invalid
/sys/firmware/acpi/interrupts/gpe16: 1 enabled
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 54753 enabled
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 invalid
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid
/sys/firmware/acpi/interrupts/gpe20: 0 invalid
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 enabled
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid
/sys/firmware/acpi/interrupts/gpe38: 0 invalid
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid
/sys/firmware/acpi/interrupts/gpe39: 0 invalid
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled
/sys/firmware/acpi/interrupts/gpe_all: 55414
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid
I wrote a service script to disable this on boot:
#!/bin/bash
### BEGIN INIT INFO
# Provides: disable-gpe17
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
logger -t gpe17 -s "Disabling gpe17 interrupts..."
/etc/pm/sleep.d/30_disable_gpe17 thaw
exit 0
This calls my PM script:
#!/bin/sh
echo 0 > /sys/firmware/acpi/interrupts/gpe17 2>/dev/null
I've made both scripts executable, and added disable-gpe17 to the boot scripts with:
sudo update-rc.d disable-gpe17 defaults
When I look in my boot log, I don't see a record of the syslog entry stating that gpe17 has been disabled.
Is there a better, perhaps udev, way of disabling certain interrupts on boot? If not, why is my service script not running on boot?
I'm on a MacBook Pro 11,5 running kernel 3.19 with Ubuntu 14.04.
acpi firmware
acpi firmware
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
asked Nov 10 '15 at 0:41
Naftuli KayNaftuli Kay
13.2k60 gold badges168 silver badges261 bronze badges
13.2k60 gold badges168 silver badges261 bronze badges
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html
An abbreviated (and corrected, at least for my instance) version is here:
$sudo -s
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
You should now see the CPU load / hear the fans go down.
Make sure this happens again on reboot - still while root privs:
#crontab -e
This opens your favourite editor. Add these lines:
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe16
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe17
Since suspend mode doesn't work for me I didn't bother following the remainder of the instructions on how to create a script that reactivates those settings on resume after suspend.
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
add a comment |
In Linux 4.19, I found that disabling the GPE (echo "disable" > /sys/firmware/acpi/interrupts/gpe17) did not fix this issue anymore. Even with the GPE disabled, the number kept running up and the CPU kept busy. It seems the new solution since Linux 4.10 is masking instead of disabling:
# echo mask > /sys/firmware/acpi/interrupts/gpe17
Or use the boot parameter acpi_mask_gpe=0x17 (in Debian/Ubuntu add this to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT, then run update-grub and reboot).
For more details, see Linux kernel commit 9c4aa1ee which was first merged in Linux 4.10-rc3 and the bug reports linked to from there.
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f242013%2fdisable-gpe-acpi-interrupts-on-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html
An abbreviated (and corrected, at least for my instance) version is here:
$sudo -s
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
You should now see the CPU load / hear the fans go down.
Make sure this happens again on reboot - still while root privs:
#crontab -e
This opens your favourite editor. Add these lines:
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe16
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe17
Since suspend mode doesn't work for me I didn't bother following the remainder of the instructions on how to create a script that reactivates those settings on resume after suspend.
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
add a comment |
I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html
An abbreviated (and corrected, at least for my instance) version is here:
$sudo -s
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
You should now see the CPU load / hear the fans go down.
Make sure this happens again on reboot - still while root privs:
#crontab -e
This opens your favourite editor. Add these lines:
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe16
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe17
Since suspend mode doesn't work for me I didn't bother following the remainder of the instructions on how to create a script that reactivates those settings on resume after suspend.
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
add a comment |
I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html
An abbreviated (and corrected, at least for my instance) version is here:
$sudo -s
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
You should now see the CPU load / hear the fans go down.
Make sure this happens again on reboot - still while root privs:
#crontab -e
This opens your favourite editor. Add these lines:
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe16
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe17
Since suspend mode doesn't work for me I didn't bother following the remainder of the instructions on how to create a script that reactivates those settings on resume after suspend.
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html
An abbreviated (and corrected, at least for my instance) version is here:
$sudo -s
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
#echo "disable" > /sys/firmware/acpi/interrupts/gpe17
You should now see the CPU load / hear the fans go down.
Make sure this happens again on reboot - still while root privs:
#crontab -e
This opens your favourite editor. Add these lines:
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe16
@reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe17
Since suspend mode doesn't work for me I didn't bother following the remainder of the instructions on how to create a script that reactivates those settings on resume after suspend.
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
edited Apr 5 at 23:34
Rui F Ribeiro
40.7k16 gold badges91 silver badges152 bronze badges
40.7k16 gold badges91 silver badges152 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
answered Jan 12 '16 at 14:12
BalthasarBalthasar
1811 silver badge2 bronze badges
1811 silver badge2 bronze badges
add a comment |
add a comment |
In Linux 4.19, I found that disabling the GPE (echo "disable" > /sys/firmware/acpi/interrupts/gpe17) did not fix this issue anymore. Even with the GPE disabled, the number kept running up and the CPU kept busy. It seems the new solution since Linux 4.10 is masking instead of disabling:
# echo mask > /sys/firmware/acpi/interrupts/gpe17
Or use the boot parameter acpi_mask_gpe=0x17 (in Debian/Ubuntu add this to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT, then run update-grub and reboot).
For more details, see Linux kernel commit 9c4aa1ee which was first merged in Linux 4.10-rc3 and the bug reports linked to from there.
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
add a comment |
In Linux 4.19, I found that disabling the GPE (echo "disable" > /sys/firmware/acpi/interrupts/gpe17) did not fix this issue anymore. Even with the GPE disabled, the number kept running up and the CPU kept busy. It seems the new solution since Linux 4.10 is masking instead of disabling:
# echo mask > /sys/firmware/acpi/interrupts/gpe17
Or use the boot parameter acpi_mask_gpe=0x17 (in Debian/Ubuntu add this to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT, then run update-grub and reboot).
For more details, see Linux kernel commit 9c4aa1ee which was first merged in Linux 4.10-rc3 and the bug reports linked to from there.
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
add a comment |
In Linux 4.19, I found that disabling the GPE (echo "disable" > /sys/firmware/acpi/interrupts/gpe17) did not fix this issue anymore. Even with the GPE disabled, the number kept running up and the CPU kept busy. It seems the new solution since Linux 4.10 is masking instead of disabling:
# echo mask > /sys/firmware/acpi/interrupts/gpe17
Or use the boot parameter acpi_mask_gpe=0x17 (in Debian/Ubuntu add this to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT, then run update-grub and reboot).
For more details, see Linux kernel commit 9c4aa1ee which was first merged in Linux 4.10-rc3 and the bug reports linked to from there.
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
In Linux 4.19, I found that disabling the GPE (echo "disable" > /sys/firmware/acpi/interrupts/gpe17) did not fix this issue anymore. Even with the GPE disabled, the number kept running up and the CPU kept busy. It seems the new solution since Linux 4.10 is masking instead of disabling:
# echo mask > /sys/firmware/acpi/interrupts/gpe17
Or use the boot parameter acpi_mask_gpe=0x17 (in Debian/Ubuntu add this to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT, then run update-grub and reboot).
For more details, see Linux kernel commit 9c4aa1ee which was first merged in Linux 4.10-rc3 and the bug reports linked to from there.
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
answered 17 mins ago
Peter NoweePeter Nowee
611 silver badge3 bronze badges
611 silver badge3 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f242013%2fdisable-gpe-acpi-interrupts-on-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
