Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Paul Thompson <set48035@gmail.com>
To: regressions@lists.linux.dev
Cc: stable@vger.kernel.org
Subject: [REGRESSION] 6.6.10+ and 6.7+ kernels lock up early in init.
Date: Mon, 22 Jan 2024 23:40:49 -0500	[thread overview]
Message-ID: <Za9DUZoJbV0PYGN2@squish.home.loc> (raw)

	Hi;

	With my longstanding configuration, kernels upto 6.6.9 work fine.
Kernels 6.6.1[0123] and 6.7.[01] all lock up in early (open-rc) init,
before even the virtual filesystems are mounted.

	The last thing visible on the console is the nfsclient service
being started and:

Call to flock failed: Funtion not implemented. (twice)

	Then the machine is unresponsive, numlock doesnt toggle the keyboard led,
and the alt-sysrq chords appear to do nothing.

	The problem is solved by changing my 6.6.9 config option:

# CONFIG_FILE_LOCKING is not set
to
CONFIG_FILE_LOCKING=y

(This option is under File Systems > Enable POSIX file locking API)

	I do not recall why I unset that, but it was working for I think the
entire 6.6 series until 6.6.10. Anyway thought I would mention it in case
anyone else hits it.

Paul


             reply	other threads:[~2024-01-23  4:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  4:40 Paul Thompson [this message]
2024-01-23  5:37 ` [REGRESSION] 6.6.10+ and 6.7+ kernels lock up early in init Linux regression tracking (Thorsten Leemhuis)
2024-01-23  6:39   ` Linux regression tracking (Thorsten Leemhuis)
2024-01-23 11:16     ` Jeff Layton
2024-01-23 11:46       ` Sedat Dilek
2024-01-23 13:19         ` Jeff Layton
2024-01-23 13:57           ` Jeff Layton
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23  5:48 Paul Thompson

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=Za9DUZoJbV0PYGN2@squish.home.loc \
    --to=set48035@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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