From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Klimov <klimov.linux@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [warn_once] warning: at kernel/hrtimer.c:625 hres_timers_resume+0x24/0x38()
Date: Wed, 29 Apr 2009 21:47:01 +0200 [thread overview]
Message-ID: <200904292147.02441.rjw@sisk.pl> (raw)
In-Reply-To: <208cbae30904290621m1fbf7bc5x27fa410a23ada3dc@mail.gmail.com>
On Wednesday 29 April 2009, Alexey Klimov wrote:
> Hello,
>
> On Tue, Apr 28, 2009 at 1:35 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Sunday 19 April 2009, Alexey Klimov wrote:
> >> Hello all
> >> When testing behaviour of radio-mr800 drvier when doing suspend/resume
> >> to disk, using echo disk > /sys/power/state i have such warning in
> >> dmesg(see below please).
> >> Kernel is 30-rc2, up-to-date. If you need more information, feel free to ask.
> >
> > Can you please retest with the appended patch applied and report back?
>
> Of course. I applied your patch against up-to-date sources (30-rc3),
> and have more messages after resume:
Thanks!
> ACPI: Preparing to enter system sleep state S4
> PM: Saving platform NVS memory
> ------------[ cut here ]------------
> WARNING: at drivers/base/sys.c:405 sysdev_suspend+0xb6/0x21c()
> Hardware name: TravelMate 2350
> Interrupts enabled after cpufreq_suspend+0x0/0x113
Well, it looks like cpufreq_suspend() left us with interrupts enabled and
that caused the other warnings to be printed. Not nice.
What CPU is there in your box?
Rafael
next prev parent reply other threads:[~2009-04-29 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 16:53 [warn_once] warning: at kernel/hrtimer.c:625 hres_timers_resume+0x24/0x38() Alexey Klimov
2009-04-27 21:35 ` Rafael J. Wysocki
2009-04-29 13:21 ` Alexey Klimov
2009-04-29 19:47 ` Rafael J. Wysocki [this message]
2009-04-30 8:54 ` Alexey Klimov
2009-05-04 12:10 ` Fabio Comolli
2009-06-03 16:43 ` Alexey Klimov
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=200904292147.02441.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=klimov.linux@gmail.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