Bug 46521
Summary: | PM timer events can not be disabled - Hitachi HTS54503(AMD Athlon II) | ||
---|---|---|---|
Product: | ACPI | Reporter: | Robert Yates (jamesluton) |
Component: | BIOS | Assignee: | Lv Zheng (lv.zheng) |
Status: | ASSIGNED --- | ||
Severity: | normal | CC: | aaron.lu, alan, chris, jamesluton, julian_dasma, lenb, lv.zheng, Robert.Moore, rui.zhang, tianyu.lan |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996782 | ||
Kernel Version: | 3.8(upstream) | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Acpi Table Dump
syslog from ubuntu 10.04 LTS live cd 3.8 upstream log dmesg from kernel 3.13 fix_event.patch dmesg after Lan Tianyu patch new logs with debug kernel new logs with debug kernel CONFIG_RTC_DRV_CMOS disabled |
Description
Robert Yates
2012-08-28 14:39:21 UTC
Created attachment 78691 [details]
Acpi Table Dump
please attach the .config file you are using. sorry i dont know what .config you mean, there is no .config file for anything. home kernel: [ 513.883742] ACPI Error: No installed handler for fixed event [0x00000000] (20120320/evevent-284) Fixed event 0 happens to be the ACPI PM Timer. This event should not even be enabled if there is not handler. Moreover, somehow the event does fire, since there is not handler, it should be immediately disabled. Please check the syslog/dmesg for the string "Enabled fixed event". Created attachment 91861 [details]
syslog from ubuntu 10.04 LTS live cd
old ubuntu version tested to see if issue also occurs in older kernels.
Hi Robert, I've been testing an older kernel version also and attached a syslog. From the log the only thing i can find that is close to your message is the following Jan 26 20:19:58 ubuntu kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) regards, Rob. Created attachment 92091 [details]
3.8 upstream log
Jan 28 23:43:51 home kernel: [ 7.914428] ACPI Error: Could not disable RealTimeClock events (20121018/evxfevnt-255)
there is plenty more acpi logging in this kernel, the most interesting being
the one above.
/R.
(In reply to Robert Yates from comment #8) > Created attachment 92091 [details] > 3.8 upstream log > > Jan 28 23:43:51 home kernel: [ 7.914428] ACPI Error: Could not disable > RealTimeClock events (20121018/evxfevnt-255) > this is an error message about RTC instead. > there is plenty more acpi logging in this kernel, the most interesting being > the one above. > does the pmtimer errors still exists? please attach the full dmesg output after boot. Created attachment 117901 [details]
dmesg from kernel 3.13
The errors still appear, however they have a label of PM_Timer and i have noticed they also come when i press my laptops "FN" key. Could you provide the output of "grep . /sys/firmware/acpi/interrupts/*"? ping ... /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled /sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled /sys/firmware/acpi/interrupts/ff_rt_clk: 1 enabled /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid /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: 1338 enabled /sys/firmware/acpi/interrupts/gpe04: 0 disabled /sys/firmware/acpi/interrupts/gpe05: 0 invalid /sys/firmware/acpi/interrupts/gpe06: 0 enabled /sys/firmware/acpi/interrupts/gpe07: 0 invalid /sys/firmware/acpi/interrupts/gpe08: 0 invalid /sys/firmware/acpi/interrupts/gpe09: 0 invalid /sys/firmware/acpi/interrupts/gpe0A: 0 invalid /sys/firmware/acpi/interrupts/gpe0B: 0 disabled /sys/firmware/acpi/interrupts/gpe0C: 0 invalid /sys/firmware/acpi/interrupts/gpe0D: 0 invalid /sys/firmware/acpi/interrupts/gpe0E: 0 invalid /sys/firmware/acpi/interrupts/gpe0F: 0 invalid /sys/firmware/acpi/interrupts/gpe10: 0 invalid /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: 0 invalid /sys/firmware/acpi/interrupts/gpe15: 0 invalid /sys/firmware/acpi/interrupts/gpe16: 0 invalid /sys/firmware/acpi/interrupts/gpe17: 0 enabled /sys/firmware/acpi/interrupts/gpe18: 0 disabled /sys/firmware/acpi/interrupts/gpe19: 0 invalid /sys/firmware/acpi/interrupts/gpe1A: 0 enabled /sys/firmware/acpi/interrupts/gpe1B: 0 disabled /sys/firmware/acpi/interrupts/gpe1C: 0 enabled /sys/firmware/acpi/interrupts/gpe1D: 0 invalid /sys/firmware/acpi/interrupts/gpe1E: 0 invalid /sys/firmware/acpi/interrupts/gpe1F: 0 invalid /sys/firmware/acpi/interrupts/gpe_all: 1338 /sys/firmware/acpi/interrupts/sci: 1338 /sys/firmware/acpi/interrupts/sci_not: 0 and after running the laptop for a while longer /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled /sys/firmware/acpi/interrupts/ff_pmtimer: 813 invalid /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled /sys/firmware/acpi/interrupts/ff_rt_clk: 1 enabled /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid /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: 2298 enabled /sys/firmware/acpi/interrupts/gpe04: 0 disabled /sys/firmware/acpi/interrupts/gpe05: 0 invalid /sys/firmware/acpi/interrupts/gpe06: 0 enabled /sys/firmware/acpi/interrupts/gpe07: 0 invalid /sys/firmware/acpi/interrupts/gpe08: 0 invalid /sys/firmware/acpi/interrupts/gpe09: 0 invalid /sys/firmware/acpi/interrupts/gpe0A: 0 invalid /sys/firmware/acpi/interrupts/gpe0B: 0 disabled /sys/firmware/acpi/interrupts/gpe0C: 0 invalid /sys/firmware/acpi/interrupts/gpe0D: 0 invalid /sys/firmware/acpi/interrupts/gpe0E: 0 invalid /sys/firmware/acpi/interrupts/gpe0F: 0 invalid /sys/firmware/acpi/interrupts/gpe10: 0 invalid /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: 0 invalid /sys/firmware/acpi/interrupts/gpe15: 0 invalid /sys/firmware/acpi/interrupts/gpe16: 0 invalid /sys/firmware/acpi/interrupts/gpe17: 0 enabled /sys/firmware/acpi/interrupts/gpe18: 0 disabled /sys/firmware/acpi/interrupts/gpe19: 0 invalid /sys/firmware/acpi/interrupts/gpe1A: 0 enabled /sys/firmware/acpi/interrupts/gpe1B: 0 disabled /sys/firmware/acpi/interrupts/gpe1C: 0 enabled /sys/firmware/acpi/interrupts/gpe1D: 0 invalid /sys/firmware/acpi/interrupts/gpe1E: 0 invalid /sys/firmware/acpi/interrupts/gpe1F: 0 invalid /sys/firmware/acpi/interrupts/gpe_all: 2298 /sys/firmware/acpi/interrupts/sci: 2298 /sys/firmware/acpi/interrupts/sci_not: 1 Created attachment 123551 [details]
fix_event.patch
Sorry for later response. Please try this debug patch and attach the output of dmesg.
I've never made any patches to the kernel before so it took me a while to figure out how to apply this fix. In the end it seemed to make no difference but perhaps i did something wrong. I downloaded the latest stable 3.13 kernel then i edited the line in the source file from the patch, i then used make-kpkg to create my kernel on a fast machine. I installed the kernel on my laptop, it booted fine but i didnt notice any acpi difference. Jan 30 00:51:58 yates-Satellite-L550D kernel: [ 334.286596] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20131115/evevent-286) etc. i noticed the patch was made to a 'driver' called acpi, i presume this is a loadable module?, however my system doesnt load this module. yates@yates-Satellite-L550D:~$ lsmod | grep acpi toshiba_acpi 22950 0 sparse_keymap 13890 1 toshiba_acpi wmi 19363 1 toshiba_acpi let me know if ive made some mistake somehow, thanks for your time. /Rob. Created attachment 123971 [details]
dmesg after Lan Tianyu patch
Any updates in this bug? I am also experiencing this. I am using Ubuntu 13.10 with kernel version 3.11.0-18-generic. I meant the continuous PM Timer error. I am also using a toshiba laptop. please make sure your kernel is built with CONFIG_ACPI_DEBUG=y, and then boot with boot option "log_buf_len=1M, acpi.debug_layer=0x04, acpi.debug_level=0x08000107", and then attach the full dmesg output after the problem happens again. Created attachment 142811 [details]
new logs with debug kernel
Created attachment 142821 [details]
new logs with debug kernel
i didnt have the debug switch in my kernel so i recompeiled and i have now attached 2 log files, 1 is with your exact boot option and a second is with your boot option but without the commas in it, i wasnt sure if it makes a difference. /Rob. From the log, the Real TimeClock GPE can't be disabled via clear associated GPE register. After writing 0 to the register, the enable bit wasn't cleared. [ 16.488107] ACPI Error: Could not disable RealTimeClock events (20131115/evxfevnt-267) How about not loading rtc driver? How do i disable that driver? btw that message is also in logs i posted over a year ago. Please comment CONFIG_RTC_DRV_CMOS line in your kernel configure file to disable RTC driver. Thanks. ping... it made no difference Created attachment 157311 [details]
CONFIG_RTC_DRV_CMOS disabled
|