linux-kernel - intel_soc_dts_thermal binding issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Mar 2015 09:04:42 -0500
From:	Josh Boyer <jwboyer@...oraproject.org>
To:	Zhang Rui <rui.zhang@...el.com>,
	Eduardo Valentin <edubezval@...il.com>
Cc:	Linux PM list <linux-pm@...r.kernel.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: intel_soc_dts_thermal binding issues

Hi All,

We've seen a number of reports where people see:

[   20.499427] intel_soc_dts_thermal: request_threaded_irq ret -22
[   20.519160] intel_soc_dts_thermal: request_threaded_irq ret -22
[   20.532660] intel_soc_dts_thermal: request_threaded_irq ret -22

in their boot logs.  They view this as a kernel bug and report is as
such.  The above log came from an ASUS x200ma machine, which has a
quad core Baytrail-M Pentium CPU (N3530).

I can't tell if the issue is because the driver is trying to bind to
all 4 cores and only CPU0 works, or what other issue would cause this.
I personally have a Celeron based NUC with a N2820 that gets the error
above for both cores and the driver doesn't load at all.

Is there something else the driver should be doing to bind to the
various CPUs?  If there's nothing else it can key off of, can we drop
the pr_err so it stops showing up in dmesg?

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/