Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18116 - [kernel26] Laptop ACPI events stop being triggered after standby

Attached to Project: Arch Linux
Opened by Nathaniel Nelson (CronLogic) - Tuesday, 02 February 2010, 04:17 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 10 August 2010, 07:34 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When I first boot this laptop, all of the ACPI buttons, bells and whistles work perfectly. I have my /etc/acpi/handler.sh script set up to run 'sudo pm-suspend' on a 'lid' event and it suspends to ram with no problem. All hell breaks loose though when I resume from suspend, whether it is triggered from pm-suspend or /sys/power/state. My biggest concern is that the CPU fan does not come back on, and so the CPU temp will climb to unsafe levels. I've tried all sorts of trickery with the /proc/acpi/fan and /proc/acpi/thermal_zone IOs, as well as module unloading/reloading, to try and trigger the fan to come back on but I eventually just have to reboot. But in addition to the missing 'thermal' events, the 'lid' events stop firing after returning from standby, as well as events from my touchpad enable/disable button and lcd contrast buttons. Additional environment/hardware info follows:

Additional info:
Toshiba A505

Arch Linux x86_64 2009.08
Kernel Package Version 2.6.32.6-1

lspci
==============
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
04:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
04:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
04:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01)
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 10 August 2010, 07:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should be fixed in 2.6.34. Please reopen if necessary.
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 February 2010, 05:34 GMT
  • Field changed: Category (Kernel → Upstream Bugs)
My suggestion: ACPI problems are the most common issue with hardware. Buggy DSDT acpi table provided by BIOS, causes many many problems like this. Since there is much nothing to do here, check is your BIOS is the latest, try to boot with kernel parameter * acpi_osi="Linux" *, see if there are ACPI warnings on kernel log * dmesg | grep "ACPI Warning". Others solutions can be replacing the DSDT table in memory at runtime. Contact with linux kernel acpi devs.

Some similar an relevant info can be found here: http://thread.gmane.org/gmane.linux.acpi.devel/37612
Comment by Federico Chiacchiaretta (baghera) - Tuesday, 02 February 2010, 08:27 GMT
I reported this to kernel bugzilla a while ago, here http://bugzilla.kernel.org/show_bug.cgi?id=14667 . This problem occurs since kernel 2.6.32rc1 .
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 February 2010, 14:14 GMT
OK, now there are more info, please post all info next time in the original bugreport. Then this is a know bug in upstream kernel (+2 months). You should wait for the upstream fix. Upstream are waiting for your response about reverting one commit.
Anyway as you can see[#1], in Arch Linux the kernel is not patched like in other distros to fix upstream issues or adding some features (the only exception a small patch for aufs2)

[#1] http://projects.archlinux.org/linux-2.6-ARCH.git
Comment by Nathaniel Nelson (CronLogic) - Thursday, 04 February 2010, 00:02 GMT
Ok thanks for the info guys. Sorry I didn't know about the upstream bug report. I'll keep my eyes on it.
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 04 February 2010, 03:29 GMT
@CronLogic: Oops, my apologies, I confused you with baghera,
Comment by Nathaniel Nelson (CronLogic) - Friday, 05 February 2010, 06:02 GMT
Ah, hehe...now this conversation makes more sense. No worries :)
Comment by Nathaniel Nelson (CronLogic) - Tuesday, 09 February 2010, 06:23 GMT
I was instructed in kernel bugzilla to file another bug report since I guess the origins of my problem are apparently different than Federico's. Here is the link:

http://bugzilla.kernel.org/show_bug.cgi?id=15260
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 03 July 2010, 20:46 GMT
any news on this issue?
Comment by Alois Nespor (anespor) - Wednesday, 04 August 2010, 21:21 GMT
bug should be fixed in kernel 2.6.34

Loading...