[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171114070634.zoh75rakg57uhd3j@dhcp22.suse.cz>
Date: Tue, 14 Nov 2017 08:06:34 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Ran Wang <ran.wang_1@....com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
Michael Ellerman <mpe@...erman.id.au>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Reza Arbab <arbab@...ux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@...il.com>,
"qiuxishi@...wei.com" <qiuxishi@...wei.com>,
Igor Mammedov <imammedo@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, Leo Li <leoyang.li@....com>,
Xiaobo Xie <xiaobo.xie@....com>
Subject: Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages
On Tue 14-11-17 06:10:00, Ran Wang wrote:
[...]
> > > This drop cause DWC3 USB controller fail on initialization with
> > > Layerscaper processors (such as LS1043A) as below:
> > >
> > > [ 2.701437] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned
> > bus number 1
> > > [ 2.710949] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -16
> > > [ 2.717411] xhci-hcd xhci-hcd.0.auto: can't setup: -12
> > > [ 2.727940] xhci-hcd xhci-hcd.0.auto: USB bus 1 deregistered
> > > [ 2.733607] xhci-hcd: probe of xhci-hcd.0.auto failed with error -12
> > > [ 2.739978] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
> > >
> > > And I notice that someone also reported to you that DWC2 got affected
> > > recently, so do you have the solution now?
> >
> > Yes. It should be in linux-next. Have a look at the following email
> > thread:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flkml.
> > kernel.org%2Fr%2F20171104082500.qvzbb2kw4suo6cgy%40dhcp22.suse.cz&
> > data=02%7C01%7Cran.wang_1%40nxp.com%7C5e73c6a941fc4f1c10e708d52
> > a860c5b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636461677
> > 583607877&sdata=zlRxJ4LZwOBsit5qRx9yFT5qfP54wZ0z6G1z%2Bcywf5g%3D
> > &reserved=0
I really have no idea where the above link came from because my email
had a reference to http://lkml.kernel.org/r/20171104082500.qvzbb2kw4suo6cgy@dhcp22.suse.cz
Has your email client modified the original email?
> Thanks for your info, although I fail to open the link you shared, but I got patch
> from my colleague and the issue got fix on my side, let you know, thanks.
Thanks for your testing anyway. Can I assume your Tested-by?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists