Re: [REGRESSION] 6.6.10+ and 6.7+ kernels lock up early in init.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 23, 2024 at 12:16 PM Jeff Layton <jlayton@xxxxxxxxxx> wrote:
>
> On Tue, 2024-01-23 at 07:39 +0100, Linux regression tracking (Thorsten
> Leemhuis) wrote:
> > [a quick follow up with an important correction from the reporter for
> > those I added to the list of recipients]
> >
> > On 23.01.24 06:37, Linux regression tracking (Thorsten Leemhuis) wrote:
> > > On 23.01.24 05:40, Paul Thompson wrote:
> > > >
> > > >   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)
> >
> > The reporter replied out-of-thread:
> > https://lore.kernel.org/all/Za9TRtSjubbX0bVu@xxxxxxxxxxxxxxx/
> >
> > """
> >       Now I feel stupid or like Im losing it, but I went back and grepped for
> > the CONFIG_FILE_LOCKING in my old Configs, and it was turned on in all
> > but 6.6.9. So, somehow I turned that off *after I built 6.6.9? Argh. I
> > just built 6.6.4 with it unset and that locked up too.
> >       Sorry if this is just noise, though one would have hoped the failure
> > was less severe...
> > """
> >
>
> Ok, so not necessarily a regression? It might be helpful to know the
> earliest kernel you can boot with CONFIG_FILE_LOCKING turned off.
>
> > >
> I'll give a try reproducing this later though.

Quote from Paul:
"
Now I feel stupid or like Im losing it, but I went back and grepped
for the CONFIG_FILE_LOCKING in my old Configs, and it was turned on in all
but 6.6.9. So, somehow I turned that off *after I built 6.6.9? Argh. I just
built 6.6.4 with it unset and that locked up too.
Sorry if this is just noise, though one would have hoped the failure
was less severe...
"

-Sedat-

https://lore.kernel.org/all/Za9TRtSjubbX0bVu@xxxxxxxxxxxxxxx/#t

> --
> Jeff Layton <jlayton@xxxxxxxxxx>
>





[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux