[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b637ec0b0905040510m5035d6bbgc98573d782b8d623@mail.gmail.com>
Date: Mon, 4 May 2009 14:10:27 +0200
From: Fabio Comolli <fabio.comolli@...il.com>
To: Alexey Klimov <klimov.linux@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [warn_once] warning: at kernel/hrtimer.c:625 hres_timers_resume+0x24/0x38()
I see the same message with 2.6.29.2 on a laptop with the same CPU
model also with cpufreq_ondemand.
In my case the first hibernate attempt gives the message and succeeds.
The system resumes ok.
A further hibernation/resume cycle results in a hang (power cycle required).
It' probably a regression wrt 2.6.28.7 (I'm not sure because with the
version upgrade I also changed my DRI driver from fglrx to radeon and
also the X.org userspace).
Regards,
Fabio
On Thu, Apr 30, 2009 at 10:54 AM, Alexey Klimov <klimov.linux@...il.com> wrote:
> Hello, Rafael
>
> On Wed, Apr 29, 2009 at 11:47 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>> On Wednesday 29 April 2009, Alexey Klimov wrote:
>>> Hello,
>>>
>>> On Tue, Apr 28, 2009 at 1:35 AM, Rafael J. Wysocki <rjw@...k.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
>
> Yes, cpufreq_ondemand enabled. It's 1.7 GHz pentium-m. The lowest
> frequency is 600 MHz.
> Here is my /proc/cpuinfo:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 13
> model name : Intel(R) Pentium(R) M processor 1.70GHz
> stepping : 6
> cpu MHz : 600.000
> cache size : 2048 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca
> cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts est tm2
> bogomips : 1198.79
> clflush size : 64
> power management:
>
>
> --
> Best regards, Klimov Alexey
> --
> 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/
>
--
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