From: Stephen Warren <swarren@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Russell King <linux@arm.linux.org.uk>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v1 0/3] Tegra30 clockframework
Date: Fri, 6 Jan 2012 13:13:08 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF177EE39F6B@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1325517486-22458-1-git-send-email-pdeschrijver@nvidia.com>
Peter De Schrijver wrote at Monday, January 02, 2012 8:18 AM:
> This patchset introduces the tegra30 clockframework. Clocks which require
> voltage scaling are not included in this version. The implementation doesn't
> use the generic clock code yet. It's the intention to move to it, once the
> semantics are fully clarified.
I tried testing this, and the kernel crashes/hangs as shown below:
[ 0.088340] CPU: Testing write buffer coherency: ok
[ 0.093638] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.099573] Division by zero in kernel.
[ 0.103643] [<c001396c>] (unwind_backtrace+0x0/0x11c) from [<c013c1cc>] (Ldiv0_64+0x8/0x18)
[ 0.112332] [<c013c1cc>] (Ldiv0_64+0x8/0x18) from [<c0056754>] (clockevents_config.part.0+0x1c/0x64)
[ 0.121810] [<c0056754>] (clockevents_config.part.0+0x1c/0x64) from [<c00569ac>] (clockevents_config_and_register+0x20/0x2c)
[ 0.133433] [<c00569ac>] (clockevents_config_and_register+0x20/0x2c) from [<c0280fec>] (twd_timer_setup+0x144/0x190)
[ 0.144335] [<c0280fec>] (twd_timer_setup+0x144/0x190) from [<c0281334>] (local_timer_setup+0x10/0x18)
[ 0.153986] [<c0281334>] (local_timer_setup+0x10/0x18) from [<c0280c00>] (percpu_timer_setup+0x54/0xa8)
[ 0.163727] [<c0280c00>] (percpu_timer_setup+0x54/0xa8) from [<c03904e0>] (smp_prepare_cpus+0x6c/0x90)
[ 0.173391] [<c03904e0>] (smp_prepare_cpus+0x6c/0x90) from [<c038d844>] (kernel_init+0x48/0x12c)
[ 0.182520] [<c038d844>] (kernel_init+0x48/0x12c) from [<c000ebf4>] (kernel_thread_exit+0x0/0x8)
[ 0.191628] ------------[ cut here ]------------
[ 0.196454] WARNING: at kernel/time/clockevents.c:46 clockevent_delta2ns+0x3c/0x84()
[ 0.204490] Modules linked in:
[ 0.207735] [<c001396c>] (unwind_backtrace+0x0/0x11c) from [<c0022284>] (warn_slowpath_common+0x4c/0x64)
[ 0.217568] [<c0022284>] (warn_slowpath_common+0x4c/0x64) from [<c00222b4>] (warn_slowpath_null+0x18/0x1c)
[ 0.227577] [<c00222b4>] (warn_slowpath_null+0x18/0x1c) from [<c005668c>] (clockevent_delta2ns+0x3c/0x84)
[ 0.237497] [<c005668c>] (clockevent_delta2ns+0x3c/0x84) from [<c0056780>] (clockevents_config.part.0+0x48/0x64)
[ 0.248040] [<c0056780>] (clockevents_config.part.0+0x48/0x64) from [<c00569ac>] (clockevents_config_and_register+0x20/0x2c)
[ 0.259654] [<c00569ac>] (clockevents_config_and_register+0x20/0x2c) from [<c0280fec>] (twd_timer_setup+0x144/0x190)
[ 0.270553] [<c0280fec>] (twd_timer_setup+0x144/0x190) from [<c0281334>] (local_timer_setup+0x10/0x18)
[ 0.280202] [<c0281334>] (local_timer_setup+0x10/0x18) from [<c0280c00>] (percpu_timer_setup+0x54/0xa8)
[ 0.289934] [<c0280c00>] (percpu_timer_setup+0x54/0xa8) from [<c03904e0>] (smp_prepare_cpus+0x6c/0x90)
[ 0.299582] [<c03904e0>] (smp_prepare_cpus+0x6c/0x90) from [<c038d844>] (kernel_init+0x48/0x12c)
[ 0.308699] [<c038d844>] (kernel_init+0x48/0x12c) from [<c000ebf4>] (kernel_thread_exit+0x0/0x8)
[ 0.317830] ---[ end trace 1b75b31a2719ed1c ]---
[ 0.322697] Setting up static identity map for 0x8028cf98 - 0x8028cff0
<<no more output>>
Without these patches, the same tree gets all the way to waiting for the
root filesystem:
[ 0.088329] CPU: Testing write buffer coherency: ok
[ 0.093631] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.099545] smp_twd: clock not found: -2
[ 0.103667] Calibrating local timer... 500.06MHz.
[ 0.161249] Setting up static identity map for 0x8028a918 - 0x8028a970
[ 2.261492] CPU1: failed to come online
[ 2.265684] Brought up 1 CPUs
[ 2.268813] SMP: Total of 1 processors activated (1987.37 BogoMIPS).
...
[ 2.704845] Registering SWP/SWPB emulation handler
[ 2.710558] Waiting for root device /dev/mmcblk1p1...
I tested using commit e4421e71fa89bee67d2b67079041ca346ae49ea3 in my
per-user repo on nv-tegra.nvidia.com.
--
nvpublic
next prev parent reply other threads:[~2012-01-06 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:18 Peter De Schrijver
2012-01-02 15:18 ` [PATCH v1 1/3] arm/tegra: add support for new clock framework features Peter De Schrijver
2012-01-02 15:18 ` [PATCH v1 2/3] arm/tegra: implement basic tegra30 clock framework Peter De Schrijver
2012-01-02 15:18 ` [PATCH v1 3/3] arm/tegra: enable " Peter De Schrijver
2012-01-03 23:03 ` [PATCH v1 0/3] Tegra30 clockframework Stephen Warren
2012-01-04 12:28 ` Peter De Schrijver
2012-01-06 21:13 ` Stephen Warren [this message]
2012-01-09 12:53 ` Peter De Schrijver
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=74CDBE0F657A3D45AFBB94109FB122FF177EE39F6B@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.com \
/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
all inboxes | Powered by JetHome®