From: Frank Scheiner <frank.scheiner@web.de>
To: linux-ia64@vger.kernel.org
Cc: debian-ia64 <debian-ia64@lists.debian.org>,
ia64@gentoo.org, "Tomáš Glozar" <tglozar@gmail.com>
Subject: Linux/ia64: Kernel testing effort
Date: Wed, 4 Oct 2023 14:17:32 +0200 [thread overview]
Message-ID: <cb4faf4f-1efc-5ae7-c8f7-7aad9c2a4d73@web.de> (raw)
Hi there,
as I usually only write to this list to report problems for ia64, I
thought it might be a good idea to also report a success story here.
Also in order to drive away any doubts about ia64 being a working
architecture for Linux.
This also goes CC to Debian's and Gentoo's respective ia64 lists.
In the past quarter or so (v6.4-rc7 to v6.6-rc4) I
"Build-n-Boot-to-login" tested nearly every RC and release version of
Linux (13 versions tested in total) on my Itanium zoo of machines, which
includes:
* rx2620 (w/2 x Montecito)
* rx4640 (w/2 x Madison)
* 2 x rx2660 (w/2 x Montecito, w/1 x Montvale)
* rx6600 (w/4 x Montvale)
* rx2800 i2 (w/1 x Tukwila)
...spanning multiple generations of Itanium hardware. And during that
timeframe I didn't face any major problems that affected all machines
and broke ia64 as a whole for Linux.
In short: Linux for ia64 continues to work on real machines.
I expect to continue this testing effort for the time being. It should
uncover all breakages that affect the mentioned hardware and my used
configuration.
This testing effort for example uncovered a boot problem for the rx6600
(not reproducible on any of the other machines, happens with SMT on and
off), which is now bisected and worked upon. Expect to hear about that
sometime in the future. I don't consider it a showstopper, as it only
affects this one machine, though I assume it might also affect a rx3600
(Gentoo has one) as this one is pretty similar to the rx6600 hardware-wise.
All information gathered during testing is documented on a private
website for now. If you're interested, please contact me directly off-list.
Cheers,
Frank
reply other threads:[~2023-10-04 12:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cb4faf4f-1efc-5ae7-c8f7-7aad9c2a4d73@web.de \
--to=frank.scheiner@web.de \
--cc=debian-ia64@lists.debian.org \
--cc=ia64@gentoo.org \
--cc=linux-ia64@vger.kernel.org \
--cc=tglozar@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 read-only IMAP folder(s) and NNTP newsgroup(s).