From: Nishanth Menon <nm@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Kevin Hilman <khilman@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>
Subject: Re: Fwd: next boot: 101 boots: 89 pass, 12 fail (next-20141216)
Date: Thu, 18 Dec 2014 16:37:28 -0600 [thread overview]
Message-ID: <54935728.9010405@ti.com> (raw)
In-Reply-To: <CAKohpokWe+MGNM7N8recCsV7O6pFDdJ89QKnqyj9TK_WRtW7yQ@mail.gmail.com>
On 12/17/2014 08:01 PM, Viresh Kumar wrote:
> On 17 December 2014 at 22:46, Kevin Hilman <khilman@kernel.org> wrote:
>> So this looks like a bug that has been hiding, but just exposed
>> because cpufreq-cpu0 (now cpufreq-dt) was not getting built-in since
>> before v3.18.
>>
>> On omap4-panda-es, v3.18 with multi_v7_defconfig + CPUFREQ_DT enabled,
>> I see this:
>>
>> [ 2.062103] cpufreq: __cpufreq_add_dev: CPU0: Running at unlisted
>> freq: 699977 KHz
>> [ 2.070404] cpufreq: __cpufreq_add_dev: CPU0: Unlisted initial
>> frequency changed to: 700000 KHz
>>
>> No BUG. But, in next-20141216,
>>
>> [ 2.083953] cpufreq: __cpufreq_add_dev: CPU0: Running at unlisted
>> freq: 699977 KHz
>> [ 2.091949] cpu cpu0: failed to set clock rate: -22
>> [ 2.097045] cpufreq: __target_index: Failed to change cpu frequency: -22
>>
>> And then the BUG.
>>
>> So the BUG() itself isn't the problem with this regression. There's
>> been a fair amount of changes in the OMAP clk driver (including some
>> other regressions), so I suspect the culprit to be lying somewhere in
>> the recent OMAP clock changes.
>
> Yeah. I agree..
>
https://git.linaro.org/people/mike.turquette/linux.git/commit/6f8e853d18a98ee95832ffebfaa288d42ae28cd5
Finally makes it work.
build warnings actually did give an indication of the issue at hand..
> next-20141216
> arch/arm/mach-omap2/cclock3xxx_data.c:262:2: warning: initialization from incompatible pointer type [enabled by default]
> arch/arm/mach-omap2/cclock3xxx_data.c:262:2: warning: (near initialization for ‘dpll1_ck_ops.determine_rate’) [enabled by default]
> arch/arm/mach-omap2/cclock3xxx_data.c:375:2: warning: initialization from incompatible pointer type [enabled by default]
> arch/arm/mach-omap2/cclock3xxx_data.c:375:2: warning: (near initialization for ‘dpll4_ck_ops.determine_rate’) [enabled by default]
> drivers/clk/ti/dpll.c:38:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/clk/ti/dpll.c:38:2: warning: (near initialization for ‘dpll_m4xen_ck_ops.determine_rate’) [enabled by default]
> drivers/clk/ti/dpll.c:61:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/clk/ti/dpll.c:61:2: warning: (near initialization for ‘dpll_ck_ops.determine_rate’) [enabled by default]
> drivers/clk/ti/dpll.c:72:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/clk/ti/dpll.c:72:2: warning: (near initialization for ‘dpll_no_gate_ck_ops.determine_rate’) [enabled by default]
> drivers/clk/ti/dpll.c:111:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/clk/ti/dpll.c:111:2: warning: (near initialization for ‘omap3_dpll_ck_ops.determine_rate’) [enabled by default]
> drivers/clk/ti/dpll.c:123:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/clk/ti/dpll.c:123:2: warning: (near initialization for ‘omap3_dpll_per_ck_ops.determine_rate’) [enabled by default]
As of next-20141218 things seem to have settled down a bit.
next-20141218 + https://patchwork.kernel.org/patch/5484401/
Various platforms I have access to looks like the following: it is a
pretty simple script, and I am still getting my remote farm to work
properly when scripts are downloaded over serial port.. but anyways..
> next-20141218
> 1: am335x-evm: BOOT: PASS: err=10 warn=25, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s2BvPhDIrP
> 2: am335x-sk: BOOT: PASS: err=9 warn=26, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s21kzAb5L3
> 3: am3517-evm: BOOT: FAIL: http://slexy.org/raw/s202ZptHTS (script download failed + a warning has popped up for OPP)
> 4: am37x-evm: BOOT: FAIL: http://slexy.org/raw/s20pvU2Nl2 (script download fail)
> 5: am437x-sk: BOOT: PASS: crit=2 err=13 warn=57, CPUFreq: N/A, CPUIdle: N/A: http://slexy.org/raw/s2hKPxe9YG
> 6: am43xx-epos: BOOT: PASS: crit=2 err=16 warn=58, CPUFreq: N/A, CPUIdle: N/A: http://slexy.org/raw/s2R6OoHCBj
> 7: am43xx-gpevm: BOOT: PASS: crit=2 err=13 warn=57, CPUFreq: N/A, CPUIdle: N/A: http://slexy.org/raw/s20fG9U1ZL
> 8: BeagleBoard-X15(am57xx-evm): BOOT: PASS: err=20 warn=24, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s2qzlorZWB
> 9: BeagleBoard-XM: BOOT: PASS: err=9 warn=19, CPUFreq: PASS, CPUIdle: FAIL: http://slexy.org/raw/s2OzLVwqPy
> 10: beagleboard-vanilla: BOOT: PASS: err=9 warn=25, CPUFreq: PASS, CPUIdle: FAIL: http://slexy.org/raw/s21EMHNZVl
> 11: beaglebone-black: BOOT: PASS: err=8 warn=25, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s2quawv4Qe
> 12: beaglebone: BOOT: PASS: err=9 warn=20, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s2iCPBeBSA
> 13: craneboard: BOOT: PASS: err=21 warn=93, CPUFreq: N/A, CPUIdle: N/A: http://slexy.org/raw/s21Mshl31r
> 14: dra72x-evm: BOOT: PASS: crit=2 err=14 warn=27, CPUFreq: N/A, CPUIdle: N/A: http://slexy.org/raw/s2JiZnJlRL
> 15: dra7xx-evm: BOOT: PASS: err=11 warn=31, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s20g14WWfL
> 16: OMAP3430-Labrador(LDP): BOOT: PASS: err=7 warn=25, CPUFreq: PASS, CPUIdle: FAIL: http://slexy.org/raw/s2PZR2j1Kw
> 17: n900: BOOT: FAIL: http://slexy.org/raw/s2lHkDllfG (I have been seeing this for a while - not reproducible on Tony's setup.. not a regression)
> 18: omap5-evm: BOOT: PASS: err=15 warn=24, CPUFreq: PASS, CPUIdle: N/A: http://slexy.org/raw/s21GJKUu8d
> 19: pandaboard-es: BOOT: PASS: err=20 warn=33, CPUFreq: PASS, CPUIdle: PASS: http://slexy.org/raw/s21X5eWQnW
> 20: pandaboard-vanilla: BOOT: PASS: err=20 warn=31, CPUFreq: PASS, CPUIdle: PASS: http://slexy.org/raw/s21HadWaKr
> 21: sdp2430: BOOT: FAIL: http://slexy.org/raw/s284xHOf52 (script download fail)
> 22: sdp3430: BOOT: PASS: err=22 warn=28, CPUFreq: PASS, CPUIdle: FAIL: http://slexy.org/raw/s2GJpDG16e
> 23: sdp4430: BOOT: PASS: err=21 warn=33, CPUFreq: PASS, CPUIdle: PASS: http://slexy.org/raw/s21ChfWSXs
> TOTAL = 23 boards, Booted Boards = 19, No Boot boards = 4
script download fail does imply my farm has still issues to resolve..
but anyways.. more or less we are back operational again since it was
broken by next-20141216
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-12-18 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Y0lcK-00026B-7I@ip-10-35-177-41.ec2.internal>
[not found] ` <CAMAWPa98kyaUJpt=GLw4cH7fkg+8BkrA0kds=H-2-4fWXy_tqw@mail.gmail.com>
2014-12-16 21:03 ` Fwd: next boot: 101 boots: 89 pass, 12 fail (next-20141216) Nishanth Menon
2014-12-17 4:07 ` Viresh Kumar
2014-12-17 15:28 ` Nishanth Menon
2014-12-17 16:27 ` Viresh Kumar
2014-12-17 16:43 ` Nishanth Menon
2014-12-18 1:54 ` Viresh Kumar
2014-12-17 17:16 ` Kevin Hilman
2014-12-17 19:11 ` Kevin Hilman
2014-12-18 2:01 ` Viresh Kumar
2014-12-18 22:37 ` Nishanth Menon [this message]
2014-12-18 22:51 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54935728.9010405@ti.com \
--to=nm@ti.com \
--cc=khilman@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).