From: Steven King <sfking@fdwdc.com>
To: linux-kernel@vger.kernel.org
Cc: john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.33-rc1: hrtimers and tickless broken on m68knommu.
Date: Fri, 18 Dec 2009 19:20:12 -0800 [thread overview]
Message-ID: <200912181920.12905.sfking@fdwdc.com> (raw)
In-Reply-To: <1f1b08da0912181844u4f7e66a7ue30287208d075327@mail.gmail.com>
On Friday 18 December 2009 06:44:44 john stultz wrote:
> On Fri, Dec 18, 2009 at 6:13 PM, Steven King <sfking@fdwdc.com> wrote:
> > Attach is the .config; it works on v2.6.32 but fails to boot on .33-rc1;
> > but if I deselect hrtimers && tickless then it works.
>
> Sorry for the dup, forgot to cc lkml on my reply.
>
> Fails to boot all together? Or does it hang at some point in the dmesg
> that you can point out?
fails to boot all together; nothing on the serial console.
>
> Could you run the following so we can narrow down which clocksource your
> using? cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> cat /sys/devices/system/clocksource/clocksource0/available_clocksource
>
> Then with the kernel that doesn't boot, go through the clocksources
> listed in available_clocksources and try booting w/
> "clocksource=<clock name>" and see if the behavior changes.
on the working .32 kernel:
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
pit
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
pit
just to be sure, I tried clocksource=pit on the .33-rc1 kernel. It didnt make
any difference.
--
Steven King -- sfking at fdwdc dot com
next prev parent reply other threads:[~2009-12-19 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 2:13 2.6.33-rc1: hrtimers and tickless broken on m68knommu Steven King
2009-12-19 2:44 ` john stultz
2009-12-19 3:20 ` Steven King [this message]
2009-12-19 4:04 ` john stultz
2009-12-19 5:06 ` Steven King
2010-01-11 3:38 ` Greg Ungerer
2009-12-22 0:39 ` [PATCH] m68knommu: Fix invalid flags on coldfire pit clocksource john stultz
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=200912181920.12905.sfking@fdwdc.com \
--to=sfking@fdwdc.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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