From: Domenico Andreoli <domenico.andreoli@linux.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Bockholdt Arne <a.bockholdt@precitec-optronik.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression due to "Workaround for uPD72020x USB3 chips"
Date: Wed, 2 May 2018 11:18:51 +0200 [thread overview]
Message-ID: <20180502091851.vr64q7atvd2tovpy@localhost> (raw)
In-Reply-To: <CAKv+Gu_rgLs2CP4Lpx=CwgmCsEm01sbn9vPzZ4z4JqVaFBtC+g@mail.gmail.com>
On Wed, May 02, 2018 at 10:22:05AM +0200, Ard Biesheuvel wrote:
> On 2 May 2018 at 10:06, Domenico Andreoli <domenico.andreoli@linux.com> wrote:
> > Dear all,
> >
> > my home machine stopped to boot starting from kernel version 4.12.7.
> >
> > The last message I read is about resetting some USB3 bus. It's 100%
> > reproducible also with any recent kernel up to 4.17.0-rc3.
> >
> > I bisected down to the following commit:
> >
> > commit 0e1f0eaed6c20db41ff61e024b361ee3ec9d686c (tag: my_broken_xhci)
> > Author: Marc Zyngier <marc.zyngier@arm.com>
> > Date: Tue Aug 1 20:11:08 2017 -0500
> >
> > xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
> >
>
> Hello Domenico,
Sir..
>
> Long time no see :-)
Instead I see you pretty much everywhere :P
>
> Please refer to the following thread
>
> https://marc.info/?l=linux-usb&m=151872295419486
>
> for some discussion on this topic, and a possible workaround.
Interesting, thanks for the pointer!
I'm happy to learn I've this nice piece of HW in my machine. It might
have at least some other issue while trying to hibernate (there is a
fair chance for it to abort the process because of some "business").
I tried the usb/uPD720202-reset branch from Marc (with some massaging
due to quirks now being >32) and my system boots again. I think it's
more because of the PCI reset is removed, I am not affected by the
original issue it was meant to fix.
>
> Regards,
> Ard.
thanks,
Dom
--
3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
next prev parent reply other threads:[~2018-05-02 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 8:06 Regression due to "Workaround for uPD72020x USB3 chips" Domenico Andreoli
2018-05-02 8:22 ` Ard Biesheuvel
2018-05-02 9:18 ` Domenico Andreoli [this message]
2018-05-02 9:41 ` Ard Biesheuvel
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=20180502091851.vr64q7atvd2tovpy@localhost \
--to=domenico.andreoli@linux.com \
--cc=a.bockholdt@precitec-optronik.de \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mathias.nyman@intel.com \
/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