Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #66473 > unrolled thread

Bug#953349: linux: unknown input when fan stops working

Started bytreaki <treaki@treaki.tk>
First post2020-03-08 11:10 +0100
Last post2020-03-09 02:00 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#953349: linux: unknown input when fan stops working treaki <treaki@treaki.tk> - 2020-03-08 11:10 +0100
    Bug#953349: marked as done (linux: unknown input when fan stops  working) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-03-09 02:00 +0100

#66473 — Bug#953349: linux: unknown input when fan stops working

Fromtreaki <treaki@treaki.tk>
Date2020-03-08 11:10 +0100
SubjectBug#953349: linux: unknown input when fan stops working
Message-ID<zI12F-t7-1@gated-at.bofh.it>
Source: linux

Version: [13428.169827] atkbd serio0: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
Severity: normal

Dear Maintainer,


    * What led up to the situation?
the fan of my thinkpad X230 got some mechanical failure (maybe called bearing failure in english). It sometimes workes grate if the thinkpad i well levelded, but when moving it around it starts making noises, then the EC (embedded controller) seams to try to switch the current on and off and on and off again and so on. Acording to the sound the fan tryes to ramp up, stops and tryes again... After some time it stops completely, i first thought its because its working again but then my tp got hot and cpu got throtteled. Its still working stable but with decreased speed/cpu power. From time to time i do a bit of manually cooling using a little vacuum cleaner... The Fan RPM value is stuck to highest value (idecating a failour):

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        65535 RPM


    * What exactly did you do (or not do) that was effective (or
      ineffective)?
I tryed to force the fan to run even if it is not behaving right (options thinkpad_acpi fan_control=1 and so on), but the EC dosent react on it anymore after it detected fan failour to often, so lenovo please let your ECs continue using the fan even if the RPM counter dosent get correct readings ;).
    * What was the outcome of this action?
After watching my system again and again using watch cat cat /proc/acpi/ibm/fan, watch sensors and dmesg -w i found out that another error seams to coresponde with the ECs giving up on the fan. So i thought you might check this with the EC-Firmware documentation and implement it so that it is not an unknown thing. Maybe even send a special warning like the one that follows after the cpu is getting to hot.
    * What outcome did you expect instead?
not apllaiable


here are the relevant dmesg lines:

[13428.169827] atkbd serio0: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
[13428.169833] atkbd serio0: Use 'setkeycodes e059 <keycode>' to make it known.
[13428.170203] atkbd serio0: Unknown key released (translated set 2, code 0xd9 on isa0060/serio0).
[13428.170207] atkbd serio0: Use 'setkeycodes e059 <keycode>' to make it known.
[15504.703639] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
[15504.703645] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[15504.703990] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
[15504.703995] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[20403.990939] atkbd serio0: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
[20403.990945] atkbd serio0: Use 'setkeycodes e059 <keycode>' to make it known.
[20403.991306] atkbd serio0: Unknown key released (translated set 2, code 0xd9 on isa0060/serio0).
[20403.991310] atkbd serio0: Use 'setkeycodes e059 <keycode>' to make it known.
[22547.406134] CPU0: Package temperature above threshold, cpu clock throttled (total events = 138528)
[22547.406136] CPU1: Package temperature above threshold, cpu clock throttled (total events = 138528)
[22547.406139] CPU3: Package temperature above threshold, cpu clock throttled (total events = 138528)
[22547.406140] CPU2: Package temperature above threshold, cpu clock throttled (total events = 138528)
[22547.407093] CPU3: Package temperature/speed normal
[22547.407095] CPU0: Package temperature/speed normal
[22547.407096] CPU2: Package temperature/speed normal
[22547.407097] CPU1: Package temperature/speed normal
[22847.430659] CPU1: Package temperature above threshold, cpu clock throttled (total events = 139347)
[22847.430660] CPU0: Package temperature above threshold, cpu clock throttled (total events = 139347)
[22847.430688] CPU2: Package temperature above threshold, cpu clock throttled (total events = 139347)
[22847.430689] CPU3: Package temperature above threshold, cpu clock throttled (total events = 139347)
[22847.432642] CPU0: Package temperature/speed normal
[22847.432643] CPU1: Package temperature/speed normal
[22847.432665] CPU2: Package temperature/speed normal
[22847.432666] CPU3: Package temperature/speed normal



thanks and keep up the good work, it would be grate if you could contact lenovo and ask them for EC-specifications and to implement a force power the fan controll mode that would be supportet by next linux acpi drivers ;).

Tim

-- System Information:
Debian Release: buster/sid
   APT prefers oldoldstable
   APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]


#66480 — Bug#953349: marked as done (linux: unknown input when fan stops working)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-03-09 02:00 +0100
SubjectBug#953349: marked as done (linux: unknown input when fan stops working)
Message-ID<zIeVX-uH-1@gated-at.bofh.it>
In reply to#66473

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 09 Mar 2020 00:51:01 +0000
with message-id <229ee134389f073cca6a7334f7cf9e2cc5d39afb.camel@decadent.org.uk>
and subject line Re: Bug#953349: linux: unknown input when fan stops working
has caused the Debian Bug report #953349,
regarding linux: unknown input when fan stops working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
953349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953349
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web