All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@huawei.com>
To: <maciej.rutecki@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, <wujianguo@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jiang Liu <liuj97@gmail.com>
Subject: Re: [REGRESSION] 3.7-rc2 kernel BUG at kernel/power/snapshot.c:517!
Date: Thu, 1 Nov 2012 20:48:56 +0800	[thread overview]
Message-ID: <50926FB8.8060903@huawei.com> (raw)
In-Reply-To: <201210302135.48585.maciej.rutecki@gmail.com>

Hi Maciej,
	Thanks for bisect, we will investigate this issue soon.
	Gerry
On 2012-10-31 4:35, Maciej Rutecki wrote:
> On niedziela, 28 października 2012 o 22:45:26 Rafael J. Wysocki wrote:
>> On Sunday, October 28, 2012 10:12:49 PM Maciej Rutecki wrote:
>>> On niedziela, 21 października 2012 o 17:12:28 Maciej Rutecki wrote:
>>>> Error: kernel BUG at kernel/power/snapshot.c:517!
>>>>
>>>> Last known good: 3.6.1
>>>> Bad: 3.7-rc2
>>>>
>>>> Steps to reproduce:
>>>> 1. Boot system with 3.7-rc2 kernel
>>>> 2. Try suspend to disk (s2ram works OK)
>>>>
>>>> System dies on message:
>>>> http://mrutecki.pl/download/kernel/3.7-rc2/swinka/DSCN0280.jpg
>>>>
>>>> lspci:
>>>> http://mrutecki.pl/download/kernel/3.7-rc2/swinka/lspci.txt
>>>>
>>>> dmesg:
>>>> http://mrutecki.pl/download/kernel/3.7-rc2/swinka/dmesg-3.7-rc2.txt
>>>
>>> Still present in -rc3
>>
>> This appears to be a memory allocation error and I have no idea what
>> the reason of it is.
>>
>> Any chance to bisect?
> 
> 7f1290f2f2a4d2c3f1b7ce8e87256e052ca23125 is the first bad commit
> commit 7f1290f2f2a4d2c3f1b7ce8e87256e052ca23125
> Author: Jianguo Wu <wujianguo@huawei.com>
> Date:   Mon Oct 8 16:33:06 2012 -0700
> 
>     mm: fix-up zone present pages
> Signed-off-by: Jianguo Wu <wujianguo@huawei.com>
>     Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
>     Reported-by: Petr Tesarik <ptesarik@suse.cz>
>     Tested-by: Petr Tesarik <ptesarik@suse.cz>
>     Cc: "Luck, Tony" <tony.luck@intel.com>
>     Cc: Mel Gorman <mel@csn.ul.ie>
>     Cc: Yinghai Lu <yinghai@kernel.org>
>     Cc: Minchan Kim <minchan.kim@gmail.com>
>     Cc: Johannes Weiner <hannes@cmpxchg.org>
>     Cc: David Rientjes <rientjes@google.com>
>     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> 
> 
> Description says:
> "This patch intends to fix-up zone->present_pages when memory are freed to
>     buddy system on x86_64 and IA64 platforms."
> 
> but I use 32 bit kernel
> 
> Revert this commit solves problem.
> 
> 
> Regards
> 
> PS. Between Oct. 31-Nov. 4 I'm offline. 



      parent reply	other threads:[~2012-11-01 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21 15:12 [REGRESSION] 3.7-rc2 kernel BUG at kernel/power/snapshot.c:517! Maciej Rutecki
2012-10-28 21:12 ` Maciej Rutecki
2012-10-28 21:12   ` Maciej Rutecki
2012-10-28 21:45   ` Rafael J. Wysocki
2012-10-28 21:45     ` Rafael J. Wysocki
2012-10-28 21:55     ` Rafael J. Wysocki
2012-10-30 20:35     ` Maciej Rutecki
2012-10-30 23:44       ` Rafael J. Wysocki
2012-11-01 12:48       ` Jiang Liu [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=50926FB8.8060903@huawei.com \
    --to=jiang.liu@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=maciej.rutecki@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=wujianguo@huawei.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.