linux-kernel - Re: [patch 0/6] hwmon/coretemp: Hotplug fixes, cleanups and state machine conversion

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1705090914100.1798@nanos>
Date:   Tue, 9 May 2017 09:16:15 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Tommi Rantala <tt.rantala@...il.com>
cc:     Guenter Roeck <linux@...ck-us.net>,
        LKML <linux-kernel@...r.kernel.org>,
        Fenghua Yu <fenghua.yu@...el.com>,
        Jean Delvare <jdelvare@...e.com>, linux-hwmon@...r.kernel.org,
        Sebastian Siewior <bigeasy@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>, x86@...nel.org
Subject: Re: [patch 0/6] hwmon/coretemp: Hotplug fixes, cleanups and state
 machine conversion

On Thu, 4 May 2017, Tommi Rantala wrote:
> 2017-04-23 18:01 GMT+03:00 Thomas Gleixner <tglx@...utronix.de>:
> > On Sat, 15 Apr 2017, Tommi Rantala wrote:
> >
> >> Testing with 4.10.8-200.fc25.x86_64: freezer, devices and platform are
> >> OK, it breaks at "processors".
> >> The screen stays off, and the machine no longer answers to ping.
> >>
> >> (Without coretemp loaded, the machine survives all the states. There
> >> are some graphics glitches and radeon error messages)
> >
> > That's odd. I tried on a similar machine (w/o a radeon card) and it just
> > works with the coretemp module loaded.
> >
> > Can you please do a CPU hotplug cycle (just one CPU) with the cpuhp events
> > in the tracer enabled. Send me the trace output so I might be able to spot
> > whats different and what interdependencies between other callbacks might be
> > there.
> 
> Hi,
> 
> Here's the trace output, does it help?

Not much. Can you please try the following:

1) Offline all CPUs except CPU0 before suspend/resume

2) Offline all CPUs except CPU0 and CPU1 before suspend/resume

3) Offline all CPUs except CPU0 and CPU2 before suspend/resume

Thanks,

	tglx