From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753209AbbJONaY (ORCPT ); Thu, 15 Oct 2015 09:30:24 -0400 Received: from mx-guillaumet.finsecur.com ([91.217.234.131]:50132 "EHLO guillaumet.finsecur.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752703AbbJONaV (ORCPT ); Thu, 15 Oct 2015 09:30:21 -0400 Date: Thu, 15 Oct 2015 15:30:16 +0200 From: Sylvain Rochet To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Alexandre Belloni , Jean-Christophe Plagniol-Villard , Nicolas Ferre , Boris Brezillon , Wenyou Yang , Ludovic Desroches , Wonhong Kwon Message-ID: <20151015133015.GA28863@gradator.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 172.16.8.13 X-SA-Exim-Mail-From: sylvain.rochet@finsecur.com Subject: Atmel sama5d3 boot regression, today's linux-next X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on guillaumet.finsecur.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Atmel SAMA5D31 boards no longer boot on today's linux-next. Bisected to: commit 7d24068e144adc03b805806645d732cf79488717 Author: Wonhong Kwon Date: Tue Oct 6 10:10:20 2015 +0900 PM / hibernate: Move pm_init/pm_disk_init to late_initcall_sync pm_init is being invoked by core_initcall and hibernate_image_size_init calculates preferred image size (image_size) based on total pages (totalram_pages). This totalram_pages can be modified during various initcall-s phase and this can cause miscalculated image_size. For example, when CMA is being used, init_cma_reserved_pageblock tries to change the totalram_pages and this job is done during core_initcall. In order words, the totalram_pages doesn't take CMA reserved pages into account when image_size is calculated and it can be too small. Move pm_init and pm_disk_init to late_initcall_sync so that it happens after all other initcall-s change the totalram_pages. Reported-by: Sangseok Lee Signed-off-by: Wonhong Kwon Signed-off-by: Rafael J. Wysocki Reverting it fixes the issue. Sylvain