Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757122AbbLWUBx (ORCPT ); Wed, 23 Dec 2015 15:01:53 -0500 Received: from pandora.arm.linux.org.uk ([78.32.30.218]:46080 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757062AbbLWUBu (ORCPT ); Wed, 23 Dec 2015 15:01:50 -0500 Date: Wed, 23 Dec 2015 20:01:32 +0000 From: Russell King - ARM Linux To: Tony Lindgren Cc: Kees Cook , Laura Abbott , Arnd Bergmann , Ard Biesheuvel , Catalin Marinas , Nicolas Pitre , Will Deacon , LKML , Linux-MM , kernel-hardening@lists.openwall.com, linux-arm-kernel@lists.infradead.org, Laura Abbott Subject: Re: [PATCH v2] ARM: mm: flip priority of CONFIG_DEBUG_RODATA Message-ID: <20151223200132.GW8644@n2100.arm.linux.org.uk> References: <20151202202725.GA794@www.outflux.net> <20151223195129.GP2793@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151223195129.GP2793@atomide.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 927 Lines: 20 On Wed, Dec 23, 2015 at 11:51:29AM -0800, Tony Lindgren wrote: > Also all omap3 boards are now oopsing in Linux next if PM is enabled: I'm not sure that's entirely true. My LDP3430 works fine with this change in place, and that has CONFIG_PM=y. See my nightly build/boot results, which includes an attempt to enter hibernation. Remember that last night's results are from my tree plus arm-soc's for-next. Maybe there's some other change in linux-next which, when combined with this change, is provoking it? -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/