From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "regressions@leemhuis.info" <regressions@leemhuis.info>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 4.11 - PowerPC crashes on boot, bisected to commit 5657933dbb6e
Date: Thu, 2 Mar 2017 05:22:14 +0000 [thread overview]
Message-ID: <1488432118.3505.4.camel@sandisk.com> (raw)
In-Reply-To: <1488431644.2870.64.camel@kernel.crashing.org>
On Thu, 2017-03-02 at 16:14 +1100, Benjamin Herrenschmidt wrote:
> 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.
Hello Ben,
Thanks. I will try to reproduce what has been reported with qemu-ppc on Friday to
double check that it's really commit 5657933dbb6e that is causing this. I reread it
but couldn't find any reason why it works on x86-64 but not on powerpc. BTW, the
following patch is needed on at least s390 but probably also on powerpc to restore
InfiniBand support: http://marc.info/?l=linux-rdma&m=148823342415501&w=2. This is
why I asked for the kernel config.
Bart.
next prev parent reply other threads:[~2017-03-02 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 3:26 Larry Finger
2017-03-02 4:07 ` Bart Van Assche
2017-03-02 12:26 ` Larry Finger
2017-03-02 5:14 ` Benjamin Herrenschmidt
2017-03-02 5:22 ` Bart Van Assche [this message]
2017-03-02 12:40 ` Larry Finger
2017-03-06 18:02 ` Bart Van Assche
2017-03-06 19:46 ` Larry Finger
2017-03-06 21:48 ` Benjamin Herrenschmidt
2017-03-07 0:43 ` Larry Finger
2017-03-09 22:22 ` Larry Finger
2017-03-10 1:45 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1488432118.3505.4.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=Larry.Finger@lwfinger.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome