linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Angel Shtilianov <angel.shtilianov@siteground.com>
To: linux-mm@kvack.org
Cc: dennis@kernel.org, tj@kernel.org, cl@linux.com, jeyu@kernel.org
Subject: Ipmi modules and linux-4.19.1
Date: Thu, 20 Dec 2018 09:55:10 +0200	[thread overview]
Message-ID: <CAJM9R-JWO1P_qJzw2JboMH2dgPX7K1tF49nO5ojvf=iwGddXRQ@mail.gmail.com> (raw)

Hi everybody.
A couple of days I've decided to migrate several servers on
linux-4.19. What I've observed is that I have no /dev/ipmi. After
taking a look into the boot log I've found that ipmi modules are
complaining about percpu memory allocation failures:
https://pastebin.com/MCDssZzV
However, I've fixed my ipmi settings using older kernel, but I did
some research about the issue.
I had to increase the PERCPU_MODULE_RESERVE and PCPU_MIN_UNIT_SIZE in
order to get the ipmi modules loaded.
include/linux/percpu.h

-#define PERCPU_MODULE_RESERVE          (8 << 10)
+#define PERCPU_MODULE_RESERVE          (8 << 11)

-#define PCPU_MIN_UNIT_SIZE             PFN_ALIGN(32 << 10)
+#define PCPU_MIN_UNIT_SIZE             PFN_ALIGN(32 << 11)

-#define PERCPU_DYNAMIC_EARLY_SIZE      (12 << 10)
+#define PERCPU_DYNAMIC_EARLY_SIZE      (12 << 11)

-#define PERCPU_DYNAMIC_RESERVE         (28 << 10)
+#define PERCPU_DYNAMIC_RESERVE         (28 << 11)

Any suggestions ?
Is it a mm issue or this is a module subsystem issue ?
Shouldn't it fall back?

Best regards,
Angel Shtilianov

             reply	other threads:[~2018-12-20  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  7:55 Angel Shtilianov [this message]
2018-12-20 15:42 ` Ipmi modules and linux-4.19.1 Tejun Heo
2018-12-20 16:00   ` Tejun Heo
2018-12-20 16:03   ` Paul E. McKenney
2018-12-20 16:04     ` Paul E. McKenney
2018-12-20 16:05       ` Tejun Heo
2018-12-20 16:22         ` Paul E. McKenney
2018-12-20 21:59           ` Corey Minyard

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='CAJM9R-JWO1P_qJzw2JboMH2dgPX7K1tF49nO5ojvf=iwGddXRQ@mail.gmail.com' \
    --to=angel.shtilianov@siteground.com \
    --cc=cl@linux.com \
    --cc=dennis@kernel.org \
    --cc=jeyu@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).