Bug 148497 - kernel stops getting ACPI ac/battery events after some time without ec_intr=0
Summary: kernel stops getting ACPI ac/battery events after some time without ec_intr=0
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Thomas Renninger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 140732
  Show dependency tree / graph
 
Reported: 2006-02-06 20:16 UTC by Forgotten User ZhJd0F0L3x
Modified: 2006-03-08 14:40 UTC (History)
2 users (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
dmesg from debug-kernel boot. (14.33 KB, text/plain)
2006-02-06 20:20 UTC, Forgotten User ZhJd0F0L3x 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User ZhJd0F0L3x 2006-02-06 20:16:25 UTC 
The recent KOTD 2.6.16-rc2-20060205230007-default stops getting AC adapter and battery events after some events have arrived, thus powersave and hal do no longer notice changes in the battery constellation and ac adapter state. Also, the ac_adapter/*/state-file is no longer updated.
The acpi interrupt stops increasing on ac-adapter plug/unplug. Reloading the ac or battery module does not help.
If i boot with ec_intr=0, everything is fine.
The beta3 kernel 2.6.16-rc1-git3-7-default did not show this behaviour.

I'll attach a dmesg from a debug-kernel boot into init=/bin/bash.
Comment 1 Forgotten User ZhJd0F0L3x 2006-02-06 20:20:31 UTC 
Created attachment 66600 [details]
dmesg from debug-kernel boot.
Comment 2 Danny Al-Gaaf 2006-02-06 20:38:23 UTC 
I have the same problem on a IBM T21 with the SUSE 10.1 Beta3 kernel
Comment 3 Thomas Renninger 2006-02-07 22:09:10 UTC 
With beta3 kernel? That's strange, the new ACPI changes shouldn't be in there.
Are you sure that ever worked?
Comment 4 Thomas Renninger 2006-03-08 14:40:32 UTC 
This probably is another sideeffect of the latest lapic/apic default changes...
Could you retest with the latest kotd and reopen if you should still see this.