netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricardo Nabinger Sanchez <rnsanchez@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: panic in udp_init() when using FORCE_NR_CPUS
Date: Tue, 13 Jun 2023 18:41:46 -0300	[thread overview]
Message-ID: <20230613184146.66d89282@espresso.lan.box> (raw)
In-Reply-To: <CANn89iKzZsyT-C-Ge6nPzC9Oo0f+gf5HZXbmXnePvSi+v4vuUg@mail.gmail.com>

On Tue, 13 Jun 2023 23:05:34 +0200
Eric Dumazet <edumazet@google.com> wrote:

> I suspect you run with LOCKDEP enabled (CONFIG_PROVE_LOCKING=y)
> and a very big NR_CPUS ?
> 
> LOCKDEP makes spinlock_t 16 times bigger :/
> 
> If so, please try the following fix.

CONFIG_LOCKDEP_SUPPORT=y

Now I'm using only 12 CPUs, per my other message where I disabled MAXSMP
and really set NR_CPUS, resulting in a successful boot.

It may be true that earlier it was architectures's max (8192).  Maybe
that was the real issue, then?

Best regards,

-- 
Ricardo Nabinger Sanchez

    Dedique-se a melhorar seus esforços.
    Todas as suas conquistas evolutivas não foram resultado dos
    deuses, das outras consciências, ou do acaso, mas unicamente
    da sua transpiração. ---Waldo Vieira, Léxico de Ortopensatas

  reply	other threads:[~2023-06-13 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 19:56 panic in udp_init() when using FORCE_NR_CPUS Ricardo Nabinger Sanchez
2023-06-13 20:19 ` Eric Dumazet
2023-06-13 21:05   ` Eric Dumazet
2023-06-13 21:41     ` Ricardo Nabinger Sanchez [this message]
2023-06-13 21:22   ` Ricardo Nabinger Sanchez

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=20230613184146.66d89282@espresso.lan.box \
    --to=rnsanchez@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemdebruijn.kernel@gmail.com \
    /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).