mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niklas Cassel <niklas.cassel@axis.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: [REGRESSION] boot regression in next-20170428
Date: Fri, 28 Apr 2017 17:08:17 +0200	[thread overview]
Message-ID: <8138a4bf-30b6-944d-083d-dcee05ce68ba@axis.com> (raw)

Hello


Since next-20170428
the ARTPEC-6 SoC (MACH_ARTPEC6) does no longer boot.

It works fine with next-20170427.


I've bisected it to the following commit:

6d684e54690caef45cf14051ddeb7c71beeb681b is the first bad commit
commit 6d684e54690caef45cf14051ddeb7c71beeb681b
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date:   Thu Apr 27 13:44:51 2017 +0800

    rhashtable: Cap total number of entries to 2^31
    
    When max_size is not set or if it set to a sufficiently large
    value, the nelems counter can overflow.  This would cause havoc
    with the automatic shrinking as it would then attempt to fit a
    huge number of entries into a tiny hash table.
    
    This patch fixes this by adding max_elems to struct rhashtable
    to cap the number of elements.  This is set to 2^31 as nelems is
    not a precise count.  This is sufficiently smaller than UINT_MAX
    that it should be safe.
    
    When max_size is set max_elems will be lowered to at most twice
    max_size as is the status quo.
    
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: David S. Miller <davem@davemloft.net>




Enabling earlyprintk does not give any more info,
it simply hangs after:

JUMP dest=0x2000000 dtb=0x2900000 machine=0x1399 initrd=0x02a00000/0x0021b193 cmdline="earlyprintk debug initcall_debug=1"
Uncompressing Linux... done, booting the kernel.



Regards,
Niklas

             reply	other threads:[~2017-04-28 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 15:08 Niklas Cassel [this message]
2017-04-28 16:06 ` David Miller

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=8138a4bf-30b6-944d-083d-dcee05ce68ba@axis.com \
    --to=niklas.cassel@axis.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®