From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: Tree for Aug 30
Date: Mon, 2 Sep 2019 09:55:20 +0200 [thread overview]
Message-ID: <20190902075520.GB28967@lst.de> (raw)
In-Reply-To: <20190901182226.GA20315@roeck-us.net>
On Sun, Sep 01, 2019 at 11:22:26AM -0700, Guenter Roeck wrote:
> On Sat, Aug 31, 2019 at 12:36:13AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190829:
> >
> > The compiler-attributes tree gained a build failure for which I reverted
> > a commit.
> >
> > The arm-soc tree gained a conflict against the arm tree.
> >
> > The csky tree gained a conflict against the dma-mapping tree.
> >
> > The fuse tree gained a conflict against the fsverity tree.
> >
> > The vfs tree gained conflicts against the fuse tree.
> >
> > The pci tree gained a build failure for which I revereted a commit.
> >
> > The net-next tree still had its build failure for which I applied a patch.
> > It also gained a conflict against the net tree.
> >
> > The regulator tree still has its build failure for which I reverted
> > a commit.
> >
> > The keys tree still has its build failure so I used the version from
> > next-20190828.
> >
> > The driver-core tree lost its build failure.
> >
> > The staging tree got conflicts against the net-next and usb trees.
> >
> > The akpm-current tree gained a build failure due to an interaction with
> > the hmm tree for which I applied a patch.
> >
>
> Something in the fixup patch seems to be wrong. I get the following
> error with sh4 boot tests when booting from usb.
>
> sm501-usb sm501-usb: OHCI Unrecoverable Error, disabled
> sm501-usb sm501-usb: HC died; cleaning up
>
> Unfortunately, bisect doesn't help much (see below). Reverting the fixup
> patch as well as the offending patch (plus a context patch) alone does
> not help either. Further analysis shows that the problem exists since
> at least next-20190823. Another round of bisect on next-20190827 suggests
> another culprit (see second bisect below). Reverting all the offending
> patches doesn't help either, though, only result in a different error.
>
> usb 1-1: new full-speed USB device number 2 using sm501-usb
> sm501-usb sm501-usb: DMA map on device without dma_mask
>
> With that, I am giving up. Copying Christoph as he appears to be heavily
> involved in the patch series causing the problems.
What was the last tree you tested that works perfectly?
next prev parent reply other threads:[~2019-09-02 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 14:36 linux-next: Tree for Aug 30 Stephen Rothwell
2019-08-30 16:52 ` linux-next: Tree for Aug 30 (exfat) Randy Dunlap
2019-08-31 0:43 ` Valdis Klētnieks
2019-09-01 18:22 ` linux-next: Tree for Aug 30 Guenter Roeck
2019-09-02 7:55 ` Christoph Hellwig [this message]
2019-09-02 13:11 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 3:16 Stephen Rothwell
2022-08-30 7:01 Stephen Rothwell
2021-08-30 10:09 Stephen Rothwell
2018-08-30 3:01 Stephen Rothwell
2013-08-31 0:48 Stephen Rothwell
2011-08-30 7:16 Stephen Rothwell
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=20190902075520.GB28967@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).