linux-kernel - Re: [PATCH v8 00/14] Tegra114 clockframework

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: <5150D33F.1000206@wwwdotorg.org>
Date:	Mon, 25 Mar 2013 16:44:15 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Peter De Schrijver <pdeschrijver@...dia.com>
CC:	linux-arm-kernel@...ts.infradead.org,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Rob Landley <rob@...dley.net>,
	Russell King <linux@....linux.org.uk>,
	Prashant Gaikwad <pgaikwad@...dia.com>,
	Simon Glass <sjg@...omium.org>,
	Rhyland Klein <rklein@...dia.com>,
	Pritesh Raithatha <praithatha@...dia.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Hiroshi Doyu <hdoyu@...dia.com>,
	Laxman Dewangan <ldewangan@...dia.com>,
	Andrew Chew <achew@...dia.com>,
	Mike Turquette <mturquette@...aro.org>,
	Thierry Reding <thierry.reding@...onic-design.de>,
	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 00/14] Tegra114 clockframework

On 03/22/2013 01:05 PM, Stephen Warren wrote:
> On 03/22/2013 06:39 AM, Peter De Schrijver wrote:
>> This is the eight version of the Tegra114 clockframework. It is based on the
>> next-20130320-fixed branch of
>> git://nv-tegra.nvidia.com/user/swarren/linux-2.6.git,
> 
> Hmmm. Basing this on v3.9-rcX would be better, since when I apply it to
> the Tegra tree, that's what it will be based on. Luckily, it applies
> there with trivial conflicts.
> 
>> http://patchwork.ozlabs.org/patch/229972/ and
>> http://patchwork.ozlabs.org/patch/229978/
> 
> The series,
> 
> Tested-by: Stephen Warren <swarren@...dia.com>
> 
> (based on my personal next-20130318-fixed branch, without
> http://patchwork.ozlabs.org/patch/229972/ applied, but instead with the
> audio clocks initialized per the patch I posted yesterday to do this).
> 
> I tested: serial console, eMMC for the root filesystem, audio playback
> using different pll_a rates, reboot, and shutdown.
> 
> This version also solves the hard hang I was seeing with V7 during
> shutdown or reboot. Now I don't have to rely on my filesystem journal:-)

Hmm. I retract that Tested-by now.

If I apply the series on top of Tegra's for-next branch (which is
currently entirely based on v3.9-rc1) then it works fine. (Similarly, it
works fine on top of next-20130318, as I reported above).

If I merge in v3.9-rc3, it's still fine. If I merge in v3.9-rc4, I see a
hard hang during boot. I believe that "hard hang" here means that some
module's registers are being touched with the clock turned off, which
locks up the CPU/bus. Certainly, sysrq doesn't work once it's hung.

I tracked this down to some interaction with commit f7db706 "ARM:
7674/1: smp: Avoid dummy clockevent being preferred over real hardware
clock-event". So says a "git bisect" between v3.9-rc3 and v3.9-rc4,
applying this CCF V8 series at each point.

If I revert that commit, the problem is solved/hidden. I tested this in
my local dev branch that's based on next-20130325 plus this CCF V8
series, plus a bunch of other cruft.

Can you please investigate what the problem is? Thanks.
--
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/