Re: SMP on Sun4m / Sun4c on Etch
On Tue, Dec 05, 2006 at 01:43:27AM +0100, Peter Rohrer wrote:
> Last weekend I installed Debian Etch on a Sun Sparcstation 10 with 2x
> Texas Instruments, Inc. - SuperSparc-(II) (50MHz) CPUs.
> I found no SMP-Kernel for 32bit, the installation manual suggests to
> compile one myself.
Right, we are not going to support SMP on sparc32 for etch.
> I tried this (following
> http://d-i.alioth.debian.org/manual/en.sparc/ch08s05.html), but it
> failed now twice during compilation with a Segmentation fault (Output
> can be found at the end of this mail).
> I found an old statement from Rob Radez saying that Linux 2.6 and SMP on
> sparc32 are not working at all. Is this still true, or is the problem
> located between keyboard and chair?
There have been some improvements on the SMP front, but it is still
not ready for showtime (one of the latest examples is bug #400372 [0]).
If you are interested in the progress, you can check out the archives
of sparclinux mailing list [1], this question pops up periodically
there.
> The manual also states that sun4c is supported on Etch (it was at least
> not on
> sarge). I just tried to netboot the installer on my Sparcstation 2, it
> starts to load, and after some time (I think when the download is
> finished), the screen turns off. I don't think this is a hardware
> problem, the system was running Debian Woody in the past.
>
> More general asked, am I wrong, or is the manual wrong/outdated?
Yes, the manual is outdated (bug #389516 [2]). sun4c is not
going to be supported by etch either.
> peter@ss10:~$ gcc --version
> gcc (GCC) 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)
>
>
> output from "fakeroot make-kpkg --initrd --revision=custom.1.0
> kernel_image"
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> CC crypto/digest.o
> CC crypto/compress.o
> crypto/compress.c: In function âcrypto_init_compress_flagsâ:
> crypto/compress.c:42: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> For Debian GNU/Linux specific bug reporting instructions,
> see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
> The bug is not reproducible, so it is likely a hardware or OS problem.
> make[2]: *** [crypto/compress.o] Error 1
> make[1]: *** [crypto] Error 2
> make[1]: Leaving directory `/usr/src/linux-source-2.6.17'
> make: *** [debian/stamp-build-kernel] Error 2
> peter@ss10:/usr/src/linux-source-2.6.17$
Ouch. Just to confirm, what kernel was this machine running when this
compilation was attempted? Is it reproducible? We definitely need to
sort this out, if it's not a hardware problem.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400372
[1] http://marc.theaimsgroup.com/?l=linux-sparc&r=1&w=2
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389516
Best regards,
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
Reply to: