Your message dated Thu, 01 May 2025 14:40:11 +0200 (CEST)
with message-id <20250501124011.77328be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #960935,
regarding linux: please enable CONFIG_NUMA on sparc64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
960935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: wishlist
Hi!
While discussing porting one of my packages to sparc64 (I wanted to
run its tests, requiring the NUMA API, at least on a single machine)
I was told that a lot of sparc64 machines in the wild have multiple
sockets. Sparc architecture in general tends to have a lot of slow
CPUs, using many-way SMT and NUMA nodes.
As cross-socket accesses are in general a same-week service, it would
be a good idea to enable this API so programs can be aware of NUMA
setups.
Thus: could you please set CONFIG_NUMA=y on linux-image-sparc64-smp?
Meow!
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
