From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Chris Rankin <rankincj@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Networking <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Yue Haibing <yuehaibing@huawei.com>,
Leon Romanovsky <leon@kernel.org>,
Qingfang DENG <qingfang.deng@siflower.com.cn>
Subject: Re: Does Linux still support UP?
Date: Fri, 22 Dec 2023 16:35:04 +0700 [thread overview]
Message-ID: <ZYVYSBKhc-uvO8_o@archie.me> (raw)
In-Reply-To: <CAK2bqVKCdaD6-PZi6gXhf=9CiKGhxQM_UHyKV_onzDPnhbAmvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
[also Cc: netdev folks and get_maintainer output for include/net/neighbour.h]
On Thu, Dec 21, 2023 at 11:12:34PM +0000, Chris Rankin wrote:
> Hi,
>
> I have an ancient i586 UP machine that happily runs vanilla Linux
> 6.4.16, but which locks up shortly after booting vanilla 6.5.0. The
> kernel *seems* to run into trouble as soon as the networking layer
> becomes busy. However, its SysRq-S/U/B sequence still seems to work as
> expected and so obviously *something* is still responding somewhere.
>
> This problem still exists in vanilla 6.6.8.
>
> FWIW I have raised this bug in bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=218296
>
To be honest, you need to bisect. For reference, see
Documentation/admin-guide/bug-bisect.rst in the kernel sources.
Since you have problem with your old machine, you may want to compile
the kernel (which is a prerequisite for bisection) on faster machine,
then transfer the kernel image + modules into your old machine to
be installed there. Without bisection, no one will look into this
regression.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-22 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 23:12 Does Linux still support UP? Chris Rankin
2023-12-22 9:35 ` Bagas Sanjaya [this message]
2023-12-29 15:41 ` Pavel Machek
2023-12-29 16:03 ` Chris Rankin
2023-12-29 17:28 ` Theodore Ts'o
2023-12-30 14:14 ` 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=ZYVYSBKhc-uvO8_o@archie.me \
--to=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@siflower.com.cn \
--cc=rankincj@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=yuehaibing@huawei.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).