Re: New test kernel - second attempt
Hi Adrian,
John Paul Adrian Glaubitz wrote:
There is something wrong with the Debian kernel that breaks it on sparc64.
Building an upstream kernel works, but any of the around 80 patches in the
Debian kernel is causing problems.
I don't really have the capacity at the moment to find out what's wrong which
is why I'm using upstream kernels on all of the buildds at the moment.
You already do an amazing work in our Big Endian world.
I have in the many trials of the past years a quite stable working
kernel, but I am unsure if it comes from our repositories or one of the
many tests.
The one which keeps my T1000 reasonably stable (even if I get a couple
of complaints at boot and some errors here and there) for hard disk,
network (apt-get upgrade, big repo GIT updates are my typical tests) as
well as compilation on about 20 cores (for full 32cores I cannot with
only 16GB of RAM)
Linux narya 6.12.38+deb13-sparc64-smp #1 SMP Debian 6.12.38-1
(2025-07-16) sparc64
In apt I have the kernel package on hold:
linux-image-sparc64-smp 6.8.12-1 6.16.3-1
So Ia little bit confused of what I am running, but it works!
Should I upgrade the system kernel and try?
Are these apt provided kernel the one you mention that have debian
config but no debian patches?
It could be worth to help understanding which debian patch(es) cause the
issue. I can do some building, but both my attempts to build kernels in
the past were a disaster and even more trying to build a deb package (if
you remember from PPC mailing list, I gave up trying to rebuild python 2.7).
Someone less busy than you on this ML is building deb kernels locally
and can guide me? I am also tempted for this work to install linux on my
Ultra Sparc Station 2.
If I find a spare hard disk and sledge, I think "temporary" multi boot
from solaris could be as easy as swapping disks!
Cheers,
Riccardo
PS: I think I found out my issue with the LOM console on this system. It
responds only if serial is attached since the beginning, or it "time
outs". I often open terminal. with "#." (without quotes) one activates
end enters ALOM which needs authentication (!). Luckily I had the
foresight years ago to reset it to something trivial....
However one needs to switch then back to "console" or one waits forever
fro the prompt because ALOM is parallel. On older system the switch is
automatic.
Reply to: