Message-ID: <1488431644.2870.64.camel@kernel.crashing.org>
Subject: Re: Regression in 4.11 - PowerPC crashes on boot, bisected to
 commit 5657933dbb6e
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>,
        Bart Van Assche <bart.vanassche@sandisk.com>,
        Thorsten Leemhuis <regressions@leemhuis.info>
Cc: LKML <linux-kernel@vger.kernel.org>
Date: Thu, 02 Mar 2017 16:14:04 +1100
In-Reply-To: <5bc9c08f-58aa-ef26-8891-4837e2d4184b@lwfinger.net>
References: <5bc9c08f-58aa-ef26-8891-4837e2d4184b@lwfinger.net>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 842
Lines: 18

On Wed, 2017-03-01 at 21:26 -0600, Larry Finger wrote:
> My Powerbook G4 Aluminum generates a fatal splat early in the boot process, just 
> after identifying the driver for the disk. Unfortunately, it turns off almost 
> immediately, thus I cannot report the message. After this bug has been 
> triggered, the system clock has been reset to Dec. 31, 1969. I assume this is a 
> side effect of an uncontrolled DMA operation.
> 
> This problem has been bisected to commit 5657933dbb6e ("treewide: Move dma_ops 
> from struct dev_archdata into struct device").

Side effect of a crash during boot... the PMU gets upset when we crash while
there's a request in flight, that's probably what is happening.

As to why that commit is broken, I don't have time to look into it right  now,
maybe next week of nobody beats me to it.

Cheers,
Ben.