-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Michal,
Am Mi den 4. Jan 2017 um 9:31 schrieb Michal Hocko:
> On Wed 04-01-17 09:15:27, Klaus Ethgen wrote:
> > Hi Michal,
> >
> > Am Mi den 4. Jan 2017 um 9:06 schrieb Michal Hocko:
> >
> > > > Just try to run with the patch and do what yo
On Wed 04-01-17 09:15:27, Klaus Ethgen wrote:
> Hi Michal,
>
> Am Mi den 4. Jan 2017 um 9:06 schrieb Michal Hocko:
>
> > > Just try to run with the patch and do what you do normally. If you do
> > > not see any OOMs in few days it should be sufficient evidence. From your
> > > previous logs it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Michal,
Am Mi den 4. Jan 2017 um 9:06 schrieb Michal Hocko:
> > Just try to run with the patch and do what you do normally. If you do
> > not see any OOMs in few days it should be sufficient evidence. From your
> > previous logs it seems you h
On Fri 30-12-16 18:23:58, Michal Hocko wrote:
> On Fri 30-12-16 17:52:30, Klaus Ethgen wrote:
> > Sorry, did reply only you..
> >
> > Am Fr den 30. Dez 2016 um 12:11 schrieb Michal Hocko:
> > > > If this turns out to be memory cgroup related then the patch from
> > > > http://lkml.kernel.org/r/201
On Fri 30-12-16 17:52:30, Klaus Ethgen wrote:
> Sorry, did reply only you..
>
> Am Fr den 30. Dez 2016 um 12:11 schrieb Michal Hocko:
> > > If this turns out to be memory cgroup related then the patch from
> > > http://lkml.kernel.org/r/20161226124839.gb20...@dhcp22.suse.cz might
> > > help.
> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sorry, did reply only you..
Am Fr den 30. Dez 2016 um 12:11 schrieb Michal Hocko:
> > If this turns out to be memory cgroup related then the patch from
> > http://lkml.kernel.org/r/20161226124839.gb20...@dhcp22.suse.cz might
> > help.
>
> Did you ge
On Tue 27-12-16 12:28:44, Michal Hocko wrote:
> On Mon 26-12-16 12:00:53, Michal Hocko wrote:
> > [CCing linux-mm]
> >
> > On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> > > Hello,
> > >
> > > The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
> >
> > Do you have memory cgro
On Tue 27-12-16 12:48:24, Klaus Ethgen wrote:
[...]
> By the way, I find the following two messages often. Maybe they are
> unrelated, maybe not.
>[31633.189121] Purging GPU memory, 144 pages freed, 5692 pages still
> pinned.
>[31638.530025] Unable to lock GPU to purge memory.
I do not th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I was just to fast mentioning that my new 4.9 compile did well. Just
after I wrote the mail, I got the same issue again. Now being back to
4.7.
OOM:
[34629.315415] Unable to lock GPU to purge memory.
[34629.315542] wicd invoked oom-killer:
gf
On Mon 26-12-16 12:00:53, Michal Hocko wrote:
> [CCing linux-mm]
>
> On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> > Hello,
> >
> > The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
>
> Do you have memory cgroups enabled in runtime (aka does the same happen
> with cgroup_d
[CCing linux-mm]
On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> Hello,
>
> The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
Do you have memory cgroups enabled in runtime (aka does the same happen
with cgroup_disable=memory)?
> First, everything seems to be sane but after
Hello,
The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
First, everything seems to be sane but after some sleep and awake
(suspend to ram) cycles I seen some really weird behaviour ending in OOM
or even complete freeze of the laptop.
What I was able to see is that it went t
12 matches
Mail list logo
