All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: sparclinux@vger.kernel.org
Subject: Re: RTC problem on Netra X1?
Date: Tue, 14 Jun 2011 16:14:35 +0000	[thread overview]
Message-ID: <1308068075.2893.26.camel@work-vm> (raw)
In-Reply-To: <alpine.SOC.1.00.1106081454240.8911@math.ut.ee>

On Tue, 2011-06-14 at 07:55 +0300, Meelis Roos wrote:
> > On Sat, 2011-06-11 at 19:51 +0300, Meelis Roos wrote:
> > > > > > # hwclock --systohc
> > > > > > Timed out waiting for time change.
> > > > 
> > > > The hwclock problem seems to have apperaed between 2.6.37 and 2.6.38 and 
> > > > I will bisect it later.
> > > 
> > > Done bisecting. Found the following patch. Reverting this patch in 
> > > 3.0.0-rc2 fixes hwclock --systohc on my Sun Fire V100 (sparc64).
> > 
> > I believe the following recently upstreamed fix should resolve this:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;há7fd4ba2a81f1d29875b20464e4899185a3c946;hp\x1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c
> 
> Yes, current git has it fixed, thanks.
> 
> However, another RTC problem I found on Netra X1 and Fire V100 is still 
> there:
> 
> No RTC device found, ALARM timers will not wake from suspend

This is on a system that does have an RTC with alarm functionality?

thanks
-john






      parent reply	other threads:[~2011-06-14 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 12:02 RTC problem on Netra X1? Meelis Roos
2011-06-08 21:56 ` David Miller
2011-06-09  9:54 ` Meelis Roos
2011-06-11 16:51 ` Meelis Roos
2011-06-13 17:28 ` Meelis Roos
2011-06-13 20:52 ` John Stultz
2011-06-14  4:55 ` Meelis Roos
2011-06-14  9:06 ` 3.0-rc3: No RTC device found Meelis Roos
2011-06-14 17:54   ` John Stultz
2011-06-23 17:32   ` Maciej Rutecki
2011-06-14 16:14 ` John Stultz [this message]

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=1308068075.2893.26.camel@work-vm \
    --to=john.stultz@linaro.org \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.