[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2674af740909271854v191d9768mc3d96f30998f8c01@mail.gmail.com>
Date: Mon, 28 Sep 2009 09:54:54 +0800
From: Yong Zhang <yong.zhang0@...il.com>
To: Maciej Rutecki <maciej.rutecki@...il.com>
Cc: 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,
zambrano@...adcom.com, davem@...emloft.net, netdev@...r.kernel.org
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()
On Mon, Sep 28, 2009 at 12:16 AM, Maciej Rutecki
<maciej.rutecki@...il.com> wrote:
> 2009/9/27 Yong Zhang <yong.zhang0@...il.com>:
>>
>> It seem this is cause by b44 dirver. Can you give a try?
>>
>> From 05ee2f22a7ea065e05bf8b5294d222a3700d2cc8 Mon Sep 17 00:00:00 2001
>> From: Yong Zhang <yong.zhang0@...il.com>
>> Date: Sun, 27 Sep 2009 22:42:41 +0800
>> Subject: [PATCH] net/b44: keep irq state at suspend_resume
>>
>> suspend() and resume() assume irq is disabled. So keep the irq
>> state when do this.
>
> Remove previous patch, add it to clean 2.6.31-git17. It doesn't help.
>
>> --
>> 1.6.0.4
>>
>>> So can you test the follow patch. And show the dmesg info(DEBUG
>>> level) after WARNING is triggered?
>>>
>>> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
>>> index fb0f46f..4a00a1a 100644
>
> Still test it?
>
If you could, then please do it. It can give us some helpful information.
Thanks,
Yong
> Regards
> --
> Maciej Rutecki
> http://www.maciek.unixy.pl
>
--
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