All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.5-rc7
Date: Mon, 16 Jul 2012 19:01:06 +0200	[thread overview]
Message-ID: <201207161901.06959.Martin@lichtvoll.de> (raw)
In-Reply-To: <CA+55aFzWEJGTRi_a1JM433_Kp5NU4nkSYEGj7+ecH7d2Mt_2kA@mail.gmail.com>

Am Montag, 16. Juli 2012 schrieb Linus Torvalds:
> On Mon, Jul 16, 2012 at 9:28 AM, Martin Steigerwald 
<Martin@lichtvoll.de> wrote:
> > Regresses badly on resume from in-kernel hibernation. I.e. hangs with
> > some red graphics artifacts on the tty. The same artifacts appear
> > for a short time with rc6 + some commits as well, but there then
> > X.org is available again.
> 
> There's a one-liner fix for this bouncing around.
> 
> Appended is a white-space damaged cut-and-paste version of the fix, so
> you'll need to either find the original patch (search the kernel
> mailing list for "Excessive delay or hang during resume from system
> suspend due to a hrtimer commit"), or just edit in the one-liner by
> hand.
> 
> This should fix it (there's apparently a question on whether the
> "false" should be "true", but that's an independent detail, it's worth
> verifying in this form regardless).
> 
>                Linus
> ---
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 269b1fe..3447cfa 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -717,6 +717,7 @@ static void timekeeping_resume(void)
>         timekeeper.clock->cycle_last =
> timekeeper.clock->read(timekeeper.clock); timekeeper.ntp_error = 0;
>         timekeeping_suspended = 0;
> +       timekeeping_update(false);
>         write_sequnlock_irqrestore(&timekeeper.lock, flags);
> 
>         touch_softlockup_watchdog();

That fixes it.

Tested three cycles.

Tested-By: Martin Steigerwald <martin@lichtvoll.de>



Compiling TuxOnIce 3.5-rc7 with that patch now to verify if that fix work 
there, too. TuxOnIce is still so much faster than in-kernel-suspend ;).


I still get:

Message from syslogd@merkaba at Jul 16 18:53:53 ...
 kernel:[   42.442466] Uhhuh. NMI received for unknown reason 3c on CPU 0.

Message from syslogd@merkaba at Jul 16 18:53:53 ...
 kernel:[   42.442470] Do you have a strange power saving mode enabled?

Message from syslogd@merkaba at Jul 16 18:53:53 ...
 kernel:[   42.442472] Dazed and confused, but trying to continue

but I keep getting these since quite some time and did not take the time 
to follow up on it.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2012-07-16 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15  0:59 Linux 3.5-rc7 Linus Torvalds
2012-07-16 14:36 ` Alan Cox
2012-07-16 16:28 ` Martin Steigerwald
2012-07-16 16:37   ` Linus Torvalds
2012-07-16 17:01     ` Martin Steigerwald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-17 19:07 Paweł Sikora
2012-07-17 19:40 ` Borislav Petkov
2012-09-30 12:54 Uwaysi Bin Kareem
2012-10-05 21:29 ` Valdis.Kletnieks
2012-10-06 13:12   ` Uwaysi Bin Kareem

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=201207161901.06959.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.