On Wed, Jun 27, 2018 at 11:06:14AM -0400, Pavel Tatashin wrote:
> On Wed, Jun 27, 2018 at 10:15 AM Herton R. Krzesinski
> wrote:
> > Thanks, I'll try it. It'll probably work since I tried memory_reserve
> > but "hacking" it at e820__register_nosave_regions, anyway I'll confirm
> > it here.
>
>
On Wed, Jun 27, 2018 at 11:06:14AM -0400, Pavel Tatashin wrote:
> On Wed, Jun 27, 2018 at 10:15 AM Herton R. Krzesinski
> wrote:
> > Thanks, I'll try it. It'll probably work since I tried memory_reserve
> > but "hacking" it at e820__register_nosave_regions, anyway I'll confirm
> > it here.
>
>
On Wed, Jun 27, 2018 at 10:15 AM Herton R. Krzesinski wrote:
> Thanks, I'll try it. It'll probably work since I tried memory_reserve
> but "hacking" it at e820__register_nosave_regions, anyway I'll confirm
> it here.
If it works, please send the new "Reserved but unavailable" value from dmesg:
[
On Wed, Jun 27, 2018 at 10:15 AM Herton R. Krzesinski wrote:
> Thanks, I'll try it. It'll probably work since I tried memory_reserve
> but "hacking" it at e820__register_nosave_regions, anyway I'll confirm
> it here.
If it works, please send the new "Reserved but unavailable" value from dmesg:
[
On Wed, Jun 27, 2018 at 09:14:21AM -0400, Pavel Tatashin wrote:
> It does look similar to what Naoya was seeing. Herton, have you tried
> applying:
>
> http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thanks, I'll try it. It'll probably
On Wed, Jun 27, 2018 at 09:14:21AM -0400, Pavel Tatashin wrote:
> It does look similar to what Naoya was seeing. Herton, have you tried
> applying:
>
> http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thanks, I'll try it. It'll probably
It does look similar to what Naoya was seeing. Herton, have you tried applying:
http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thank you,
Pavel
On Wed, Jun 27, 2018 at 3:35 AM Michal Hocko wrote:
>
> This smells like an issue Naoya was
It does look similar to what Naoya was seeing. Herton, have you tried applying:
http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thank you,
Pavel
On Wed, Jun 27, 2018 at 3:35 AM Michal Hocko wrote:
>
> This smells like an issue Naoya was
This smells like an issue Naoya was seeing I guess (Cced)
On Tue 26-06-18 17:41:52, Herton R. Krzesinski wrote:
> Hi,
>
> While running proc01 test from ltp, or as I later found out if you just read
> kpagecount ("cat /proc/kpagecount > /dev/null"), I started to get the
> following
> oops on
This smells like an issue Naoya was seeing I guess (Cced)
On Tue 26-06-18 17:41:52, Herton R. Krzesinski wrote:
> Hi,
>
> While running proc01 test from ltp, or as I later found out if you just read
> kpagecount ("cat /proc/kpagecount > /dev/null"), I started to get the
> following
> oops on
On Tue, Jun 26, 2018 at 04:50:27PM -0400, Pavel Tatashin wrote:
> Herton,
>
> Thank you for analysis, could you please attach the config that you are using.
Sure, the config file is attached.
>
> Thank you,
> Pavel
> On Tue, Jun 26, 2018 at 4:42 PM Herton R. Krzesinski
> wrote:
> >
> > Hi,
>
On Tue, Jun 26, 2018 at 04:50:27PM -0400, Pavel Tatashin wrote:
> Herton,
>
> Thank you for analysis, could you please attach the config that you are using.
Sure, the config file is attached.
>
> Thank you,
> Pavel
> On Tue, Jun 26, 2018 at 4:42 PM Herton R. Krzesinski
> wrote:
> >
> > Hi,
>
Herton,
Thank you for analysis, could you please attach the config that you are using.
Thank you,
Pavel
On Tue, Jun 26, 2018 at 4:42 PM Herton R. Krzesinski wrote:
>
> Hi,
>
> While running proc01 test from ltp, or as I later found out if you just read
> kpagecount ("cat /proc/kpagecount >
Herton,
Thank you for analysis, could you please attach the config that you are using.
Thank you,
Pavel
On Tue, Jun 26, 2018 at 4:42 PM Herton R. Krzesinski wrote:
>
> Hi,
>
> While running proc01 test from ltp, or as I later found out if you just read
> kpagecount ("cat /proc/kpagecount >
Hi,
While running proc01 test from ltp, or as I later found out if you just read
kpagecount ("cat /proc/kpagecount > /dev/null"), I started to get the following
oops on latest kernels (4.17+) in a specific system:
[ 112.926100] general protection fault: [#1] SMP PTI
[ 112.926691] CPU: 1
Hi,
While running proc01 test from ltp, or as I later found out if you just read
kpagecount ("cat /proc/kpagecount > /dev/null"), I started to get the following
oops on latest kernels (4.17+) in a specific system:
[ 112.926100] general protection fault: [#1] SMP PTI
[ 112.926691] CPU: 1
16 matches
Mail list logo
