From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 7B5E71A0547 for ; Wed, 28 May 2014 09:15:10 +1000 (EST) Message-ID: <53851AFA.5040504@xenosoft.de> Date: Wed, 28 May 2014 01:08:42 +0200 From: Christian Zigotzky MIME-Version: 1.0 To: Michael Ellerman , linuxppc-dev@lists.ozlabs.org Subject: Kernel 3.15: Boot problems with a PA6T board References: <5366649E.4030102@xenosoft.de> <1399268891.4600.3.camel@concordia> <53720AAC.1000100@xenosoft.de> <1401107166.23096.1.camel@concordia> In-Reply-To: <1401107166.23096.1.camel@concordia> Content-Type: text/plain; charset=UTF-8; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Michael, Thanks a lot for your answer. On 26.05.2014 14:26, Michael Ellerman wrote: > > Hi Christian, > > I'm almost certain that is not the commit which breaks your machine. Or if it > is, something *really* weird is going on. > > The code changed in that commit should never run on a PA6T. You're right. I think this patch is for Power 8. >> Experimental protocol: >> >> git checkout -f 01d8885785a60ae8f4c37b0ed75bdc96d0fc6a44; git clean -fdx >> (from 02/04/14) -> Kernel boots >> git checkout -f f1553174a207f68a4ec19d436003097e0a4dc405; git clean -fdx >> (from 03/04/14) -> Kernel boots >> git checkout -f d40326f4b9f9617cdfd30f83a2db57d47e9c5bac; git clean -fdx >> (from 04/04/14) -> Kernel boots >> git checkout -f 930b440cd8256f3861bdb0a59d26efaadac7941a; git clean -fdx >> (from 05/04/14) -> doesn't boot (rtc error) >> git checkout -f 2b3a8fd735f86ebeb2b9d061054003000c36b654; git clean -fdx >> (from 06/04/14) -> doesn't boot (rtc error) >> git checkout -f 26c12d93348f0bda0756aff83f4867d9ae58a5a6; git clean -fdx >> (from 07/04/14) -> doesn't boot (rtc error) >> git checkout -f a6c8aff022d4d06e4b41455ae9b2a5d3d503bf76; git clean -fdx >> (from 08/04/14) -> Kernel boots >> git checkout -f 035328c202d26a824b8632fd3b00635db5aee5a2; git clean -fdx >> (from 08/04/14) -> Kernel boots >> git checkout -f 9000c17dc0f9c910267d2661225c9d33a227b27e; git clean -fdx >> (from 08/04/14) powerpc/powernv: Fix endian issues with sensor code >> One OPAL call and one device tree property needed byte swapping. -> >> doesn't boot (prom_init) >> git checkout -f d3d35d957a9d0733dc51f14b5abc0bff5d3c5f3a; git clean -fdx >> (from 08/04/14) -> doesn't boot (prom_init) >> git checkout -f c4586256f0c440bc2bdb29d2cbb915f0ca785d26; git clean -fdx >> (from 09/04/14) -> doesn't boot (prom_init) > So it looks like you manually picked commits based on the date? Yes, it is. > That's a good start, but if you want to find the actual problem commit you need > to do a proper bisect. > >> I'm not a programmer but what can I do to solve this boot problem? > To start with you can probably narrow it down a bit by testing the following > commits: > > 18a1a7a1d862ae0794a0179473d08a414dd49234 <- It doesn't boot. Error messages: Oops: Machine check, sig: 7 [#1] CPU: 1 PID: 1 Comm: swapper/0 not tainted > d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b <- It boots. :-) > 0f5a869600141a0d5575e3190af01a050c081b07 <- It boots. :-) > c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac <- It boots. :-) > d3e144532703fe2454b56eddb56f30d2d620187b <- It boots. :-) I think the machine check is the problem. Cheers, Christian