All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Kees Cook <keescook@chromium.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: Sphinx parallel build errors
Date: Sun, 27 Oct 2019 12:17:29 -0600	[thread overview]
Message-ID: <20191027121729.59c1d539@lwn.net> (raw)
In-Reply-To: <8305ffe2-51ba-eb4b-4d44-2defe45aa68f@infradead.org>

On Sun, 27 Oct 2019 11:11:57 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> > Yes, I see oom-kills when building docs for 5.4-rc2.
> > But only after I ran 'gimp *.jpg' for 22 photos.
> > 
> > I can see anywhere from 1 to 4 sphinx-build processes running.  
> 
> I continue to have oom-kills when building docs.
> At least 2 times I also had system freezes where I had to power
> cycle to reboot.
> 
> I suppose I can only hope that other people start running into this
> issue.  :(

Are you still running gimp at the same time?

Also, are you doing a straight "make htmldocs" or something else?

Thanks,

jon

  reply	other threads:[~2019-10-27 18:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 21:37 Sphinx parallel build errors Randy Dunlap
2019-10-09 21:40 ` Jonathan Corbet
2019-10-09 22:18   ` Randy Dunlap
2019-10-10  2:30 ` Kees Cook
2019-10-10  3:00   ` Bhaskar Chowdhury
2019-10-10 18:48   ` Jonathan Corbet
2019-10-10 20:15     ` Randy Dunlap
2019-10-27 18:11       ` Randy Dunlap
2019-10-27 18:17         ` Jonathan Corbet [this message]
2019-10-27 18:30           ` Randy Dunlap
2019-10-27 19:05             ` Mauro Carvalho Chehab
2019-10-27 19:36               ` Randy Dunlap
2019-10-28 19:07               ` Kees Cook
2019-10-29  8:16                 ` Markus Heiser
2019-10-29 16:09                   ` Kees Cook
2019-10-29 19:41                   ` Randy Dunlap
2019-10-29 19:57                     ` Markus Heiser
2019-10-29 20:10                       ` Randy Dunlap

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=20191027121729.59c1d539@lwn.net \
    --to=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.