Jani Nikula:
> On Thu, 15 Jun 2017, "J. R. Okajima" wrote:
> > How about v4.11.x series?
> > I got v4.11.5, but it doesn't contain the fix.
> > Do you have a plan?
>
> The upstream commit has the proper Cc: stable and Fixes: tags in place,
> it just takes a while for the
Jani Nikula:
> On Thu, 15 Jun 2017, "J. R. Okajima" wrote:
> > How about v4.11.x series?
> > I got v4.11.5, but it doesn't contain the fix.
> > Do you have a plan?
>
> The upstream commit has the proper Cc: stable and Fixes: tags in place,
> it just takes a while for the patches to trickle to
On Thu, 15 Jun 2017, "J. R. Okajima" wrote:
> Thanx, I got linux-v4.12-rc4 and it contains
> 4681ee2 2017-05-18 drm/i915: Do not sync RCU during shrinking
>
> How about v4.11.x series?
> I got v4.11.5, but it doesn't contain the fix.
> Do you have a plan?
The upstream
On Thu, 15 Jun 2017, "J. R. Okajima" wrote:
> Thanx, I got linux-v4.12-rc4 and it contains
> 4681ee2 2017-05-18 drm/i915: Do not sync RCU during shrinking
>
> How about v4.11.x series?
> I got v4.11.5, but it doesn't contain the fix.
> Do you have a plan?
The upstream commit has the proper
Joonas Lahtinen:
> Don't worry, it's not lost. It was merged to drm-intel-fixes and thus is in
> the pipeline.
>
> There were some unexpected delays getting fixes in, sorry for that.
Thanx, I got linux-v4.12-rc4 and it contains
4681ee2 2017-05-18 drm/i915: Do not sync RCU during
Joonas Lahtinen:
> Don't worry, it's not lost. It was merged to drm-intel-fixes and thus is in
> the pipeline.
>
> There were some unexpected delays getting fixes in, sorry for that.
Thanx, I got linux-v4.12-rc4 and it contains
4681ee2 2017-05-18 drm/i915: Do not sync RCU during
On ti, 2017-05-30 at 13:00 -0700, Hugh Dickins wrote:
> On Mon, 22 May 2017, Joonas Lahtinen wrote:
> > On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> > > "J. R. Okajima":
> > > >
> > > > I don't know whether the fix is good to me or not yet. I will test your
> > > > fix, but I am busy
On ti, 2017-05-30 at 13:00 -0700, Hugh Dickins wrote:
> On Mon, 22 May 2017, Joonas Lahtinen wrote:
> > On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> > > "J. R. Okajima":
> > > >
> > > > I don't know whether the fix is good to me or not yet. I will test your
> > > > fix, but I am busy
On Tue, 30 May 2017, Hugh Dickins wrote:
> On Mon, 22 May 2017, Joonas Lahtinen wrote:
>> On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
>> > "J. R. Okajima":
>> > >
>> > > I don't know whether the fix is good to me or not yet. I will test your
>> > > fix, but I am busy
On Tue, 30 May 2017, Hugh Dickins wrote:
> On Mon, 22 May 2017, Joonas Lahtinen wrote:
>> On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
>> > "J. R. Okajima":
>> > >
>> > > I don't know whether the fix is good to me or not yet. I will test your
>> > > fix, but I am busy now and my test
On Mon, 22 May 2017, Joonas Lahtinen wrote:
> On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> > "J. R. Okajima":
> > >
> > > I don't know whether the fix is good to me or not yet. I will test your
> > > fix, but I am busy now and my test will be a few weeks later. Other
> > > people may
On Mon, 22 May 2017, Joonas Lahtinen wrote:
> On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> > "J. R. Okajima":
> > >
> > > I don't know whether the fix is good to me or not yet. I will test your
> > > fix, but I am busy now and my test will be a few weeks later. Other
> > > people may
On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> "J. R. Okajima":
> >
> > I don't know whether the fix is good to me or not yet. I will test your
> > fix, but I am busy now and my test will be a few weeks later. Other
> > people may want the fix soon. So I'd suggest you to reproduce the
>
On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote:
> "J. R. Okajima":
> >
> > I don't know whether the fix is good to me or not yet. I will test your
> > fix, but I am busy now and my test will be a few weeks later. Other
> > people may want the fix soon. So I'd suggest you to reproduce the
>
"J. R. Okajima":
> I don't know whether the fix is good to me or not yet. I will test your
> fix, but I am busy now and my test will be a few weeks later. Other
> people may want the fix soon. So I'd suggest you to reproduce the
> problem on your side. I guess "mem=1G" or "mem=512M" will make it
"J. R. Okajima":
> I don't know whether the fix is good to me or not yet. I will test your
> fix, but I am busy now and my test will be a few weeks later. Other
> people may want the fix soon. So I'd suggest you to reproduce the
> problem on your side. I guess "mem=1G" or "mem=512M" will make it
On ke, 2017-05-10 at 12:43 +0200, Andrea Arcangeli wrote:
> It works for me too. I'm running my workstation also with
> synchronize_rcu removed from i915_gem_shrink_all in addition to the
> above. Isn't the oom method invoked from reclaim context too? As far
> as I can tell synchronize_rcu can end
On ke, 2017-05-10 at 12:43 +0200, Andrea Arcangeli wrote:
> It works for me too. I'm running my workstation also with
> synchronize_rcu removed from i915_gem_shrink_all in addition to the
> above. Isn't the oom method invoked from reclaim context too? As far
> as I can tell synchronize_rcu can end
Hello,
On Tue, May 09, 2017 at 08:04:24PM -0700, Hugh Dickins wrote:
> On Mon, 8 May 2017, Joonas Lahtinen wrote:
> > On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > >
Hello,
On Tue, May 09, 2017 at 08:04:24PM -0700, Hugh Dickins wrote:
> On Mon, 8 May 2017, Joonas Lahtinen wrote:
> > On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > >
On ti, 2017-05-09 at 20:04 -0700, Hugh Dickins wrote:
> On Mon, 8 May 2017, Joonas Lahtinen wrote:
> > On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > > Thanx for the
On ti, 2017-05-09 at 20:04 -0700, Hugh Dickins wrote:
> On Mon, 8 May 2017, Joonas Lahtinen wrote:
> > On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > > Thanx for the
On Mon, 8 May 2017, Joonas Lahtinen wrote:
> On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > Thanx for the reply.
> > > >
> > > > Andrea Arcangeli:
> > > > >
> > > > > Yes I
On Mon, 8 May 2017, Joonas Lahtinen wrote:
> On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > Thanx for the reply.
> > > >
> > > > Andrea Arcangeli:
> > > > >
> > > > > Yes I
On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > Thanx for the reply.
> > >
> > > Andrea Arcangeli:
> > > >
> > > > Yes I already reported this, my original fix was way more
On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > Thanx for the reply.
> > >
> > > Andrea Arcangeli:
> > > >
> > > > Yes I already reported this, my original fix was way more
Joonas Lahtinen:
> Filing a bug in freedesktop.org with all the details is the fastest way
> of getting help. Without the bug (and with such little information as
> the previous e-mail) it's hard to estimate the extent and nature of the
> bug.
My original report was
Joonas Lahtinen:
> Filing a bug in freedesktop.org with all the details is the fastest way
> of getting help. Without the bug (and with such little information as
> the previous e-mail) it's hard to estimate the extent and nature of the
> bug.
My original report was
On Fri, 5 May 2017, Joonas Lahtinen wrote:
> On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > Thanx for the reply.
> >
> > Andrea Arcangeli:
> > >
> > > Yes I already reported this, my original fix was way more efficient
> > > (and also safer considering the above) than what landed
On Fri, 5 May 2017, Joonas Lahtinen wrote:
> On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > Thanx for the reply.
> >
> > Andrea Arcangeli:
> > >
> > > Yes I already reported this, my original fix was way more efficient
> > > (and also safer considering the above) than what landed
On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> Thanx for the reply.
>
> Andrea Arcangeli:
> >
> > Yes I already reported this, my original fix was way more efficient
> > (and also safer considering the above) than what landed upstream. My
> > feedback was ignored though.
> >
> >
On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> Thanx for the reply.
>
> Andrea Arcangeli:
> >
> > Yes I already reported this, my original fix was way more efficient
> > (and also safer considering the above) than what landed upstream. My
> > feedback was ignored though.
> >
> >
Thanx for the reply.
Andrea Arcangeli:
> Yes I already reported this, my original fix was way more efficient
> (and also safer considering the above) than what landed upstream. My
> feedback was ignored though.
>
> https://lists.freedesktop.org/archives/intel-gfx/2017-April/125414.html
I see.
Thanx for the reply.
Andrea Arcangeli:
> Yes I already reported this, my original fix was way more efficient
> (and also safer considering the above) than what landed upstream. My
> feedback was ignored though.
>
> https://lists.freedesktop.org/archives/intel-gfx/2017-April/125414.html
I see.
On Sun, Apr 30, 2017 at 03:07:58PM +0900, J. R. Okajima wrote:
> Hello,
>
> Since v4.11-rc7 I can see the workqueue stops on my development/test system.
> Git-bisecting tells me the suspicious commit is
> c053b5a 2017-04-11 drm/i915: Don't call synchronize_rcu_expedited under
>
On Sun, Apr 30, 2017 at 03:07:58PM +0900, J. R. Okajima wrote:
> Hello,
>
> Since v4.11-rc7 I can see the workqueue stops on my development/test system.
> Git-bisecting tells me the suspicious commit is
> c053b5a 2017-04-11 drm/i915: Don't call synchronize_rcu_expedited under
>
Hello,
Since v4.11-rc7 I can see the workqueue stops on my development/test system.
Git-bisecting tells me the suspicious commit is
c053b5a 2017-04-11 drm/i915: Don't call synchronize_rcu_expedited under
struct_mutex
I am not sure whether this is the real cause or not of my problem, but
Hello,
Since v4.11-rc7 I can see the workqueue stops on my development/test system.
Git-bisecting tells me the suspicious commit is
c053b5a 2017-04-11 drm/i915: Don't call synchronize_rcu_expedited under
struct_mutex
I am not sure whether this is the real cause or not of my problem, but
38 matches
Mail list logo