From: Paul Grandperrin <paul.grandperrin@gmail.com>
To: rankincj@gmail.com
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [BUG] Linux 6.8.10 NPE
Date: Sun, 19 May 2024 13:28:58 +0200 [thread overview]
Message-ID: <A8DQDS.ZXN0FMYZ3DIM1@gmail.com> (raw)
> I am using vanilla Linux 6.8.10, and I've just noticed this BUG in my
dmesg log. I have no idea what triggered it, and especially since I
have not even mounted any NFS filesystems?!
Hi all,
I have the exact same bug. I'm using the NixOS kernel but as soon as it
was updated to 6.8.10 my server has gone in a crash-reboot-loop.
The server is hosting an NFS deamon and it crashes about 10 seconds
after the tty login prompt is displayed.
Dowgrading to 6.8.9 fixes the issue.
Regards,
Paul Grandperrin
next reply other threads:[~2024-05-19 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 11:28 Paul Grandperrin [this message]
2024-05-22 15:11 ` [BUG] Linux 6.8.10 NPE Greg KH
2024-05-22 15:12 ` Greg KH
2024-05-24 11:28 ` Linux regression tracking (Thorsten Leemhuis)
-- strict thread matches above, loose matches on Subject: below --
2024-05-18 12:53 Chris Rankin
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=A8DQDS.ZXN0FMYZ3DIM1@gmail.com \
--to=paul.grandperrin@gmail.com \
--cc=CAK2bqVJoT3yy2m0OmTnqH9EAKkj6O1iTk42EyyMtvvxKh6YDKg@mail.gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@gmail.com \
--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