Bug 27792
| Summary: | Fan speed freezes, and hotkeys stop working. Lenovo Thinkpad L512 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | amnesia |
| Component: | Platform_x86 | Assignee: | drivers_platform_x86 (drivers_platform_x86) |
| Status: | ASSIGNED --- | ||
| Severity: | blocking | CC: | aaron.lu, acpi-bugzilla, alan, amnesia, evol.ig, jdelvare, jp-bug-report, jrnieder, lenb, mjg59-kernel, rjw, rostedt, rui.zhang, szg00000 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.6.2 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 16444 | ||
| Attachments: |
2.6.36-4 while everything's still working normally
2.6.39-rc9 while everything's still working normally acpidump of 2.6.39-rc6 when the bug is occuring acpidump of 2.6.36-4 when the bug is occuring acpidump of 3.0-rc5 when the bug is occuring acpidump 3.2.0-2-amd64 when the bug is occuring dmesg output after the problem occurs on 3.3.0 dmesg dmesg2 acpidump bios 1.37 acpidump bios 1.37 |
||
|
Description
amnesia
2011-01-29 11:24:01 UTC
Aren't having this issue on 2.6.35-22, so I will try the latest git tree tomorrow. Problem also exists in 2.6.38-rc3 We need to figure out how the fan is really controlled. Please see what's under /sys/class/thermal/ on your system (preferably with the current mainline kernel). please attach the output from acpidump, available here: http://userweb.kernel.org/~lenb/acpi/utils/pmtools/acpidump/ Created attachment 56832 [details]
2.6.36-4 while everything's still working normally
Rafael J. Wysocki: /sys/class/thermal/: total 0 lrwxrwxrwx 1 root root 0 May 6 14:04 cooling_device0 -> ../../devices/virtual/thermal/cooling_device0 lrwxrwxrwx 1 root root 0 May 6 14:04 cooling_device1 -> ../../devices/virtual/thermal/cooling_device1 lrwxrwxrwx 1 root root 0 May 6 14:04 cooling_device2 -> ../../devices/virtual/thermal/cooling_device2 lrwxrwxrwx 1 root root 0 May 6 14:04 cooling_device3 -> ../../devices/virtual/thermal/cooling_device3 lrwxrwxrwx 1 root root 0 May 6 14:04 cooling_device4 -> ../../devices/virtual/thermal/cooling_device4 lrwxrwxrwx 1 root root 0 May 6 14:04 thermal_zone0 -> ../../devices/virtual/thermal/thermal_zone0 That's on 2.6.36-4, compiling the current mainline at the moment, will post the output of that later. Len Brown: I've attached the acpidump made on 2.6.36-4, and soon will give an acpidump made on the current mainline. I must notice I took acpidump from the debian repositories since I couldnt get the source compiled due to wrong header files, not sure whether that an issue? NOTE: In upper comments I mentioned the problem didnt occur in 2.6.35-22, but that wasnt true, it just takes longer for the problem to occur on that kernel. So basically the problem exists in all latests kernels, but it occurs after a longer amount of time in 2.6.35* and 2.6.36* Rafael J. Wysocki: /sys/class/thermal/: total 0 lrwxrwxrwx 1 root root 0 May 6 14:59 cooling_device0 -> ../../devices/virtual/thermal/cooling_device0 lrwxrwxrwx 1 root root 0 May 6 14:59 cooling_device1 -> ../../devices/virtual/thermal/cooling_device1 lrwxrwxrwx 1 root root 0 May 6 14:59 cooling_device2 -> ../../devices/virtual/thermal/cooling_device2 lrwxrwxrwx 1 root root 0 May 6 14:59 cooling_device3 -> ../../devices/virtual/thermal/cooling_device3 lrwxrwxrwx 1 root root 0 May 6 14:59 cooling_device4 -> ../../devices/virtual/thermal/cooling_device4 lrwxrwxrwx 1 root root 0 May 6 14:59 thermal_zone0 -> ../../devices/virtual/thermal/thermal_zone0 That's on 2.6.39-rc6. Created attachment 56842 [details]
2.6.39-rc9 while everything's still working normally
Acpidump seems to be 3 times faster on *36-4 than on 39-rc6 don't know how that's possible? Created attachment 56872 [details]
acpidump of 2.6.39-rc6 when the bug is occuring
the contents of /sys/class/thermal/ are the same when the bug is occuring and when everything is fine.
Created attachment 57382 [details]
acpidump of 2.6.36-4 when the bug is occuring
Created attachment 63892 [details]
acpidump of 3.0-rc5 when the bug is occuring
So the problem also persists in 3.0-rc5. Exactly the same behavior.
It's great that kernel bugzilla is back. can you please verify if the problem still exists in the latest upstream kernel? The problem also occurs in 3.1.0 3.2.0 and 3.3.0. Still running 2.6.35.14, but I'd like to upgrade. ( the reason I changed email adresses, is because I lost my previous emailaddress/password ) Could by any change anyone look at this ticket? ThinkPad L512 (2597AB2) Debian GNU/Linux kernel 3.2.0-2-amd64 similar problem. Created attachment 72801 [details]
acpidump 3.2.0-2-amd64 when the bug is occuring
Is there some way to increase the severity of this ticket? (now that someone else also experienced it). also want to know it so this is a regression, right? please attach the dmesg output after the problem occurs. Yes that's right. Created attachment 72829 [details]
dmesg output after the problem occurs on 3.3.0
Note: when the problem occurs xev also doesn't pick up any keystrokes, the following is given when the problem does NOT occur:
Volume up:
KeymapNotify event, serial 27, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Volume down:
KeymapNotify event, serial 27, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeymapNotify event, serial 27, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeymapNotify event, serial 27, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Some other issue: It might not be related to this, but when I the problem does not yet occur, and I press the mute button, everything's fine. But when I press volume up/down after using the mute button twice (so I turned it off and on..) the sound also mutes, this can be disabled by pressing the mute button again.
Created attachment 72847 [details]
dmesg
Often off key after hibernate, but it happens that after a simple turn off.
from the keypad only works always fn + f10 = numlk; fn + insert = prtsc; fn + down; up; left; right = play; stop; ....
Also, bad fan reacts to the temperature necessary to use thinkfan.
3.2.0-2-amd64
Created attachment 72850 [details]
dmesg2
Here dmesg after 2 hours of normal operation, and then press again, disconnected
Zhang Rui: Is there anything else I can do to aid the recovery of this bug? also help than I can.! lenovo.com on a new version of BIOS 81ET61WW (1.37) 03/28/2012. renewed. we'll see what happens. unchanged Same over here, same behavior on 1.37. Would you by any chance want a acpidump on 1.37? Created attachment 73098 [details]
acpidump
bios 1.37
All keys are
Created attachment 73099 [details]
acpidump bios 1.37
keys do not work
tell me the problem kontognibut do? evol what did you mean with the above? What does "kontognibut" stand for? Excuse my bad english =) (google.translate) I wanted to say. tell that someone is engaged in the problem? whether or not to wait at all? Is there some way to draw more attention towards this case? I really need to upgrade my kernel but aren't able to because of this bug. bugzilla is not a support forum., it's a bug tracking system. If you need to get something fixed to a timescale then talk to your distribution or whoever your provider is. Hi!
A few quick questions:
1. You mentioned that everything works fine on Windows. When you
experience this problem, does rebooting into Windows and then
back to Linux help?
2. I think you mentioned that some Ubuntu versions do not have
this problem. Which ones? Ideally a list summarizing the kernel
versions you have tried and what happened with each would be useful.
3. Have you tried a 3.5.y or newer kernel (like the one from Debian
experimental)? If so, how did it behave?
That should do for now.
------------------------------------------------------------------------
1. You mentioned that everything works fine on Windows. When you
experience this problem, does rebooting into Windows and then
back to Linux help?
No it does not, a reboot is needed to resolve the problem.
2. I think you mentioned that some Ubuntu versions do not have
this problem. Which ones? Ideally a list summarizing the kernel
versions you have tried and what happened with each would be useful.
2.6.35-22: "The problem" occurs incidentally.
2.6.36-4: "The problem" occurs often.
2.6.38-rc3: "The problem" occurs often.
2.6.39-rc6: "The problem" occurs often.
2.6.39-rc9: "The problem" occurs often.
3.0-rc5: "The problem" occurs often.
3.1.0: "The problem" occurs often.
3.2.0: "The problem" occurs often.
3.3.0: "The problem" occurs often.
3. Have you tried a 3.5.y or newer kernel (like the one from Debian
experimental)? If so, how did it behave?
Yes I did, I tried 3.6, and it had exactly the same behaviour.
------------------------------------------------------------------------
Is there any more information I can gather for you in order to debug the problem?
(In reply to comment #39)
> Hi!
>
> A few quick questions:
>
> 1. You mentioned that everything works fine on Windows. When you
> experience this problem, does rebooting into Windows and then
> back to Linux help?
>
> 2. I think you mentioned that some Ubuntu versions do not have
> this problem. Which ones? Ideally a list summarizing the kernel
> versions you have tried and what happened with each would be useful.
>
> 3. Have you tried a 3.5.y or newer kernel (like the one from Debian
> experimental)? If so, how did it behave?
>
> That should do for now.
Sorry I answered to quick.
1. You mentioned that everything works fine on Windows. When you
experience this problem, does rebooting into Windows and then
back to Linux help?
Rebooting does not solve this problem. The only thing that solves this is shutting down completely.
I have the same issue. For me, just shutting down and restarting does not help. I also have to disconnect the AC and remove the Battery for a few seconds. Then the FN keys and Fan work again until the problem reappears after a while. Everything works fine on Windows. Same over here, I don't need to remove the battery cause I never use it. So the problem only gets fixed when it's disconnected from any power source. > 1. You mentioned that everything works fine on Windows. When you > experience this problem, does rebooting into Windows and then > back to Linux help? Rebooting does not solve this problem. The problem disappears only after food and accumulator shutdown. > 2. I think you mentioned that some Ubuntu versions do not have > this problem. Which ones? Ideally a list summarizing the kernel > versions you have tried and what happened with each would be useful. 3 days of uptime. the problem isn't revealed evol@evol-ThinkPad-L512:~$ lsb_release -d Description: Ubuntu 12.04.1 LTS evol@evol-ThinkPad-L512:~$ uname -a Linux evol-ThinkPad-L512 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux evol@evol-ThinkPad-L512:~$ lsmod Module Size Used by nfsd 277809 2 nfs 356410 1 lockd 86161 2 nfsd,nfs fscache 61529 1 nfs auth_rpcgss 53380 2 nfsd,nfs nfs_acl 12883 2 nfsd,nfs sunrpc 245464 17 nfsd,nfs,lockd,auth_rpcgss,nfs_acl snd_hrtimer 12744 1 nls_utf8 12557 0 isofs 40257 0 nls_iso8859_1 12713 0 nls_cp437 16991 0 vfat 17585 0 fat 61512 1 vfat uas 18180 0 usb_storage 49198 2 snd_usb_audio 122982 2 snd_usbmidi_lib 25395 1 snd_usb_audio joydev 17693 0 snd_hda_codec_hdmi 32474 1 parport_pc 32866 0 bnep 18281 2 rfcomm 47604 0 ppdev 17113 0 bluetooth 180104 10 bnep,rfcomm arc4 12529 2 snd_hda_codec_realtek 224173 1 rtl8192se 99989 0 psmouse 97362 0 serio_raw 13211 0 rtlwifi 111202 1 rtl8192se mac80211 506816 2 rtl8192se,rtlwifi uvcvideo 72627 0 videodev 98259 1 uvcvideo v4l2_compat_ioctl32 17128 1 videodev cfg80211 205544 2 rtlwifi,mac80211 jmb38x_ms 17646 0 memstick 16569 1 jmb38x_ms snd_hda_intel 33773 5 snd_hda_codec 127706 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 13668 2 snd_usb_audio,snd_hda_codec thinkpad_acpi 81819 0 snd_pcm 97188 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_seq_midi 13324 0 radeon 804426 3 snd_rawmidi 30748 2 snd_usbmidi_lib,snd_seq_midi mei 41616 0 snd_page_alloc 18529 2 snd_hda_intel,snd_pcm ttm 76949 1 radeon drm_kms_helper 46978 1 radeon drm 242038 5 radeon,ttm,drm_kms_helper i2c_algo_bit 13423 1 radeon snd_seq_midi_event 14899 1 snd_seq_midi wmi 19256 0 snd_seq 61896 3 snd_seq_midi,snd_seq_midi_event snd_timer 29990 4 snd_hrtimer,snd_pcm,snd_seq snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq snd 78855 26 snd_usb_audio,snd_usbmidi_lib,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,thinkpad_acpi,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 15091 1 snd nvram 14413 1 thinkpad_acpi video 19596 0 coretemp 13525 0 mac_hid 13253 0 lp 17799 0 parport 46562 3 parport_pc,ppdev,lp usbhid 47199 0 hid 99559 1 usbhid r8169 62099 0 sdhci_pci 18826 0 sdhci 33205 1 sdhci_pci > 3. Have you tried a 3.5.y or newer kernel (like the one from Debian > experimental)? If so, how did it behave? I will try > 3. Have you tried a 3.5.y or newer kernel (like the one from Debian
> experimental)? If so, how did it behave?
evol@evolaptop:~$ uname -a
Linux evolaptop 3.5-trunk-amd64 #1 SMP Debian 3.5.5-1~experimental.1 x86_64 GNU/Linux
same problem
collected a kernel 3.6.2. same problem Just found the following references to this case: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687853 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1048544 Is there anyway to raise attention towards this case, I really need to upgrade but am unable to due to this bug. (In reply to comment #47) > Is there anyway to raise attention towards this case, I really need to > upgrade > but am unable to due to this bug. Can you bisect? (In reply to comment #6) > In upper comments I mentioned the problem didnt occur in 2.6.35-22, but that > wasnt true, it just takes longer for the problem to occur on that kernel. So > basically the problem exists in all latests kernels, but it occurs after a > longer amount of time in 2.6.35* and 2.6.36* Can you be more precise about this? E.g. does it happen within one week 80% of the time on 2.6.36 but within one hour 80% of the time on 3.6.2? (Completely made up examples of what a concrete description would look like.) Another way to help would be to clean up the attachments by marking some as obsolete, so the signal is easier to find amid the noise. Most of them are the same --- the output of "acpidump" on a given machine does not change from one kernel version to another. Thanks for your response. > Can you bisect? No but I'm going to try. I'll keep you up to date. It's going to take a while since the bug occurs sporadically. > Can you be more precise about this? E.g. does it happen within one week 80% > of the time on 2.6.36 but within one hour 80% of the time on 3.6.2? > (Completely > made up examples of what a concrete description would look like.) From 2.6.36 -> * it happens in 100% of the time, the duration until it appears is variable though, that's why it's this hard to troubleshoot. > Another way to help would be to clean up the attachments by marking some as > obsolete, so the signal is easier to find amid the noise. Most of them are > the same --- the output of "acpidump" on a given machine does not change from > one kernel version to another. Done. (In reply to comment #50) > From 2.6.36 -> * it happens in 100% of the time, the duration until it > appears > is variable though, that's why it's this hard to troubleshoot. What's a typical duration? Most often does it happen within a week? What happens with 2.6.35.14? Do I understand correctly that that's the kernel you have been stuck on for everyday use? It happens withing hours at > 2.6.36. That's correct 2.6.35.14 is the kernel I'm stuc on for everyday use. It almost never happens on that. So to summarize:
2.6.35.14 -> once in a week/month
> 2.6.37 -> once every half an hour ish.
I'm trying to bisect atm.
I've tried bisecting, but since the problem occurs randomly, it's almost impossible to get useful data. There is quite a lot of improvement since 3.6.4. Is anything remarkable changed in the ACPI codebase of 3.6.4 compared to 3.6.0 ? (unloading thinkpad_acpi doesn't have any effect btw) The problem seems to occur more frequently when there's a high CPU utilization. (In reply to comment #54) > The problem seems to occur more frequently when there's a high CPU > utilization. too noticed such regularity Jonathan, is there any other way how I can debug this? Perhaps turn on some debugging output for a specific kernel element? exact same problem ubuntu 12.10 according to the acpidump attached, as there is no ACPI fan in this machine, I assume it is the thinkpad_acpi driver that control the fan&hotkey. Matthew, can you help look at this issue? We had a related report on the lm-sensors list: http://lists.lm-sensors.org/pipermail/lm-sensors/2013-June/039143.html Anyone working on this bug? exact same problem ubuntu 13.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1048544 |