From: "Theodore Ts'o" <tytso@mit.edu>
To: Chris Rankin <rankincj@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Does Linux still support UP?
Date: Fri, 29 Dec 2023 11:28:23 -0600 [thread overview]
Message-ID: <20231229172823.GC148343@mit.edu> (raw)
In-Reply-To: <CAK2bqVLBZvU2fVfY4bkFrU=4X+W4O3f5pbTdeQjMW=W2sGWpeQ@mail.gmail.com>
On Fri, Dec 29, 2023 at 04:03:56PM +0000, Chris Rankin wrote:
>
> I have already attached as much information as I am *ever* likely to
> be able to extract about this problem to the Bugzilla ticket.
In addition to doing a bisection, something else you might want to
try, since in the bugzilla you have hypothesized that it might be a
bug in the e100 driver, is to try building a kernel without the driver
configured, and see if that makes the kernel not hang. If it does,
then it's likely that the problem is either in the e100 driver, or
maybe somewhere in the networking stack --- although in that case it's
more likely someone else would have noticed.
Something else you might try is to connect up a serial console, so you
can get the full output from sysrq output. The other advantage of
using a serial console is people are much more likely to scan a text
file with the consoles, as opposed to downloading and trying to make
sense of the screen snapshots. (BTW, was the flash enabled on your
cell phone? The bright white spot in the middle of the screen makes
it very hard to read.)
I'd also try sysrq-l (show backtrace for all active CPU's), so you can
see where the kernel is actually hanging.
For better or for worse, support for old hardware is a volunteer
effort, so owners of the said old hardware need to do a bunch of the
leg work. Or if you can have a paid support contract, maybe you can
pay someone to gather the detail, but when you say "is feature X
supported" in an open source project, that has a different meaning
from a commercial software product.
- Ted
next prev parent reply other threads:[~2023-12-29 17:28 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
2023-12-29 15:41 ` Pavel Machek
2023-12-29 16:03 ` Chris Rankin
2023-12-29 17:28 ` Theodore Ts'o [this message]
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=20231229172823.GC148343@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rankincj@gmail.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).