All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	clemens@ladisch.de, venkatesh.pallipadi@intel.com,
	gregkh@suse.de
Subject: Re: [2.6.31-git17] WARNING: at kernel/hrtimer.c:648  hres_timers_resume+0x40/0x50()/WARNING: at drivers/base/sys.c:353  __sysdev_resume+0xc3/0xe0()
Date: Tue, 29 Sep 2009 16:38:32 +0200	[thread overview]
Message-ID: <8db1092f0909290738o217fc231t8b6d0d698ff0844c@mail.gmail.com> (raw)
In-Reply-To: <20090929072454.GA11414@elte.hu>

2009/9/29 Ingo Molnar <mingo@elte.hu>:
>
> * Yong Zhang <yong.zhang0@gmail.com> wrote:
>
>> On Sun, Sep 27, 2009 at 4:05 PM, Maciej Rutecki
>> <maciej.rutecki@gmail.com> wrote:
>> > Kernel: 2.6.31-git17
>> >
>> > During suspend to disk & resume I got it in dmesg:
>> >
>> > [  587.940010] ------------[ cut here ]------------
>> > [  587.940010] WARNING: at kernel/hrtimer.c:648 hres_timers_resume+0x40/0x50()
>> > [  587.940010] Hardware name: HP Compaq nx6310 (EY501ES#AKD)
>> > [  587.940010] hres_timers_resume() called with IRQs enabled!
>> > [  587.940010] Modules linked in: btusb i915 drm_kms_helper drm
>
> Could you try this with .32-rc1? This commit should have fixed the
> message above:
>
> 89133f9: clocksource: Resume clocksource without taking the clocksource mutex
>
>        Ingo
>

Dmesg:
http://unixy.pl/maciek/download/kernel/2.6.31-git17/gumis/dmesg-2.6.32-rc1.txt
(s2disk and resume)
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

      parent reply	other threads:[~2009-09-29 14:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27  8:05 [2.6.31-git17] WARNING: at kernel/hrtimer.c:648 hres_timers_resume+0x40/0x50()/WARNING: at drivers/base/sys.c:353 __sysdev_resume+0xc3/0xe0() Maciej Rutecki
2009-09-27  8:27 ` Yong Zhang
2009-09-27  8:30   ` Yong Zhang
2009-09-27 10:25     ` Maciej Rutecki
2009-09-27 14:01       ` Yong Zhang
2009-09-27 14:49         ` Yong Zhang
2009-09-27 14:49           ` Yong Zhang
2009-09-27 15:40           ` Rafael J. Wysocki
2009-09-27 16:16           ` Maciej Rutecki
2009-09-27 16:16             ` Maciej Rutecki
2009-09-27 18:17             ` Rafael J. Wysocki
2009-09-28  1:54             ` Yong Zhang
2009-09-28  1:54               ` Yong Zhang
2009-09-28 18:38               ` Maciej Rutecki
2009-09-28 18:38                 ` Maciej Rutecki
2009-09-28 20:08                 ` Maciej Rutecki
2009-09-28 20:08                   ` Maciej Rutecki
2009-09-28 21:13                   ` Rafael J. Wysocki
2009-09-29  5:44                 ` Yong Zhang
2009-09-29  5:44                   ` Yong Zhang
2009-09-27 15:46         ` Rafael J. Wysocki
2009-09-28  1:53           ` Yong Zhang
2009-09-29  7:24   ` Ingo Molnar
2009-09-29  9:31     ` Yong Zhang
2009-09-30  7:50       ` Michal Schmidt
2009-09-30  8:01         ` Yong Zhang
2009-09-30  8:20           ` Michal Schmidt
2009-09-30  8:27             ` Yong Zhang
2009-09-29 14:38     ` Maciej Rutecki [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=8db1092f0909290738o217fc231t8b6d0d698ff0844c@mail.gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=yong.zhang0@gmail.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 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.