From: Chris Rankin <rankincj@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Does 6.5 kernel require different userspace to 6.4 kernel?
Date: Sun, 10 Dec 2023 19:07:50 +0000 [thread overview]
Message-ID: <CAK2bqVLVfBOGcj326grzz2b2PMcTmuj44a5yhWh1H1Z9ch3JCA@mail.gmail.com> (raw)
Hi,
I have a truly ancient i586/UP/32 bit PC (for historical reasons) that
happily runs Linux 6.4.16. However, when I tried to upgrade it today
to run Linux 6.5.13, I discovered that both its console and its
networking froze almost immediately after it had booted. There is no
sign of any oops in any of the logs. My first thought was that memory
corruption had crashed the kernel, except that the SysRq interface
still works correctly.
The PC's userspace has not changed at all; I have only upgraded its
kernel from 6.4.16 to 6.5.13. And restoring the 6.4.16 kernel restores
correct operation. However, I cannot identify any clue as to what
could be wrong with my 6.5.13 kernel. Can anyone suggest anything that
may have changed between 6.4 and 6.5 that could be causing this
please?
Thanks for any assistance,
Cheers,
Chris
next reply other threads:[~2023-12-10 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 19:07 Chris Rankin [this message]
2023-12-13 16:31 ` Does 6.5 kernel require different userspace to 6.4 kernel? David Laight
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=CAK2bqVLVfBOGcj326grzz2b2PMcTmuj44a5yhWh1H1Z9ch3JCA@mail.gmail.com \
--to=rankincj@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).