Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753247AbbF2Kqy (ORCPT ); Mon, 29 Jun 2015 06:46:54 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:33150 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753319AbbF2Kp5 (ORCPT ); Mon, 29 Jun 2015 06:45:57 -0400 Date: Mon, 29 Jun 2015 12:45:53 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Pavel Machek Cc: sre@debian.org, sre@ring0.de, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com Subject: Re: n900 in 4.2-rc0: repeating oopses Message-ID: <20150629104553.GD16230@pali> References: <20150416093234.GA17423@amd> <20150629091146.GA5103@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150629091146.GA5103@amd> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 36 Hi! On Monday 29 June 2015 11:11:46 Pavel Machek wrote: > Hi! > > Just tried booting 4.2-rc0 on n900 (commit > 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous > -rc0 version worked. This time, there's some output on console, but > too fast for me to read. > What happen after errors are reported? Maybe you can enable R&D mode and disable HW watchdogs to prevent device reboots... > It seems oopses happen before mounting root. If you have serial > console, they should be easy to see. > > I tried booting same kernel in qemu, but it seems to work ok there. > Hm... Maybe problem with HS code? By chance, can you try to disable (omap) sham node in n900 DT file? (same way like omap aes is disabled) > Any ideas? Thanks, > Pavel -- Pali Rohár pali.rohar@gmail.com -- 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/