[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090930102037.55db07ed@hammerfall>
Date: Wed, 30 Sep 2009 10:20:37 +0200
From: Michal Schmidt <mschmidt@...hat.com>
To: Yong Zhang <yong.zhang0@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Maciej Rutecki <maciej.rutecki@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, clemens@...isch.de,
venkatesh.pallipadi@...el.com, gregkh@...e.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()
Dne Wed, 30 Sep 2009 16:01:40 +0800
Yong Zhang <yong.zhang0@...il.com> napsal(a):
> From my previous mail, I have ask Maciej to test the blow patch:
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index fb0f46f..4a00a1a 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -569,6 +569,9 @@ static int timekeeping_resume(struct sys_device
> *dev) unsigned long flags;
> struct timespec ts;
>
> + WARN_ONCE(!irqs_disabled(),
> + KERN_INFO "timekeeping_resume() called with IRQs
> enabled!"); +
> read_persistent_clock(&ts);
>
> clocksource_resume();
>
> And indeed, the warning is showed.
Is it? After Maciej tested it, he said:
> no "timekeeping_resume() called with IRQs enabled!".
which I read as: no such message was shown.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists