Re: New Debian sparc installation images
It's a completely fresh install on formatted disks. Just to double check I was able to reinstall the previous install build (2016-11-5) so there is some sort of regression here. Yeah I was trying to determine why it was throwing that error at line 607 but it appears to just be a closing fi statement. On Sun, Nov 27, 2016 at 1:38 PM, James Clarke wrote: > > On 27 Nov 2016, at 18:29, John Paul Adrian Glaubitz < > glaub...@physik.fu-berlin.de> wrote: > > > > Hi Kieron! > > > >> On 11/27/2016 04:10 PM, Kieron Gillespie wrote: > >> Nov 27 14:59:50 debootstrap: sh: apt_dest: unknown operand > >> Nov 27 14:59:50 debootstrap: /usr/sbin/debootstrap: line 607: : > Permission denied > > > > This look like a general issue in debian-installer, i.e. not specific to > sparc64. > > > > Looking at the source of debootstrap:607 [1], there is just a closing > "if" statement > > at this line, so I don't really see where the "Permission denied" should > come from. > > > > My first guess was that it's related with the usr-merge which was by > enabled by default > > on debootstrap recently, but I currently have no idea really. > > Is this to a freshly-formatted partition, or one with > a pre-existing /bin etc? I've seen issues running > debootstrap on the latter before. > > Regards, > James >
Re: New Debian sparc installation images
So I just gave this a shot on my SunBlade 2500 and ran into a small issue when the installer gets to the point for Installing the base system. "The debootstrap program exited with an error (return value 127)." With in my syslog I see the following, Nov 27 14:59:43 cdrom-detect: Detected CD with 'unstable' (sid) distribution Nov 27 14:59:43 anna-install: Installing eject-udeb Nov 27 14:59:46 anna-install: Installing apt-mirror-setup Nov 27 14:59:46 anna-install: Installing apt-cdrom-setup Nov 27 14:59:46 anna-install: Installing sid-support Nov 27 14:59:46 cdrom-checker[12528]: (process:14134): unknown udeb sid-support Nov 27 14:59:47 main-menu[232]: DEBUG: resolver (libgcc1): package doesn't exist (ignored) Nov 27 14:59:47 main-menu[232]: INFO: Falling back to the package description for brltty-udeb Nov 27 14:59:49 main-menu[232]: INFO: Falling back to the package description for brltty-udeb Nov 27 14:59:49 main-menu[232]: INFO: Menu item 'bootstrap-base' selected Nov 27 14:59:50 debootstrap: sh: apt_dest: unknown operand Nov 27 14:59:50 debootstrap: /usr/sbin/debootstrap: line 607: : Permission denied I can attached the complete log for the syslog but I think that the above is the important section. Let me know what you think. -Kieron Gillespie On Tue, Nov 22, 2016 at 3:43 AM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > Hi! > > After a half year break, I have finally created new installer images for > Debian sparc64. These are currently being uploaded to my Debian webspace > and should be completely uploaded within the next minutes, see [1]. > > A quick and rough installation guide can be found in [2], please let > us know if you encounter any issues or want to give feedback. These > images have not been tested so far as I just generated them this > night. > > Thanks, > Adrian > > > [1] https://people.debian.org/~glaubitz/debian-cd/2016-11-22/ > > [2] https://lists.debian.org/debian-sparc/2016/06/msg00126.html > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: Debian-9.0-sparc64-netinst-1 2016-05-04 on Sunblade 2500 Success
So currently the instructions are identical to those used by Adrian in his Please upgrade your machine thread, https://lists.debian.org/debian-sparc/2016/06/msg00126.html Except if you have a graphics card that is producing a working framebuffer you don't need to add the addtional serial tty configuration. You can then simply run "apt-get install xfce4" you will then have XFCE installed, lightdm should get installed along side the xfce4 package. Now the real problem is if your graphics card will work well enough with Xorg. I have a couple of old Sun graphics cards but didn't really get a good experiance with any of them. Currently I am going off the beaten path again as I am trying to get an old GeForce I have (NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1)) working on this system again. At one point I had my SunBlade 2500 running at 1080p and able to play Quake 3 with this graphics card. I have gotten the nouveau to load the basic modesetting terminal, which is pretty good, but am now running into CACH_ERRORs when I try to force Xorg to run which is locking up CPU0 at 100%. So still working out those problems. (Maybe I should try Wayland instead?) -Kieron GIllespie On Wed, Jul 6, 2016 at 9:08 PM, Dr. Wolfgang Daum wrote: > Kieron, > > would you please publish detailed installation instructions? I have a 1500 > and want to put XFCE on it as well. > > Thanks > > Wolf. Daum > > *From:* Kieron Gillespie > *Sent:* Wednesday, July 06, 2016 7:08 PM > *To:* debian-sparc > *Subject:* Debian-9.0-sparc64-netinst-1 2016-05-04 on Sunblade 2500 > Success > > Hello everyone, > > I just wanted everyone to know I just tested the installation of Debian > 9.0 Sparc64 on a Sunblade 2500. > > Looks like it's working well going to run some more hardware tests on it > later. See if I can't get the Nouveau driver working on it again and maybe > bring up and test XFCE on it. > > -Kieron Gillespie >
Debian-9.0-sparc64-netinst-1 2016-05-04 on Sunblade 2500 Success
Hello everyone, I just wanted everyone to know I just tested the installation of Debian 9.0 Sparc64 on a Sunblade 2500. Looks like it's working well going to run some more hardware tests on it later. See if I can't get the Nouveau driver working on it again and maybe bring up and test XFCE on it. -Kieron Gillespie
Re: New working sparc64 netinst image
Any chance that we are about ready to write some instructions on how other can setup there own instance of SPARC64 yet? Feeling like my instructions right now would require a bit too much hacking at this point but maybe with the next release of the install iso? On Fri, Jan 1, 2016 at 5:55 PM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > On 01/01/2016 11:48 PM, Ulrich Teichert wrote: > > No harm done, though, installed the rest by hand for now and got a > booting > > system with kernel 4.3.3. That's more than I could say last year ;-) > > Almost done. It seems I simply did not built the new base-installer and > partman-ext3 packages. Will be right back with a new image. > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: New working sparc64 netinst image
Was wondering if there is any way to install the SILO bootloader with this installed? I was pretty much able to get everything installed, with all the work arounds listed here, except for SILO which appears to no longer be available in the repros. On Fri, Jan 1, 2016 at 2:20 PM, Ulrich Teichert wrote: > Hi, > > >On 01/01/2016 07:45 PM, Ulrich Teichert wrote: > >> Jan 1 18:15:11 base-installer: error: Unable to execute > /usr/lib/post-base-installer.d/60partman-zfs > >> Jan 1 18:15:20 base-installer: info: could not determine kernel flavour > >> Jan 1 18:15:20 base-installer: info: could not determine kernel flavour > >> Jan 1 18:15:20 base-installer: info: could not determine kernel flavour > >> Jan 1 18:15:20 base-installer: info: could not determine kernel flavour > >> Jan 1 18:15:20 base-installer: info: Found kernels '' > > > >Aha, base-installer it is. Looking at the code: > > > >root@test-adrian1 > :/srv/sid-sparc64-sbuild/debian/DEBIAN_INSTALLER/debian-installer# > >cd packages/base-installer/kernel/ > >root@test-adrian1 > :/srv/sid-sparc64-sbuild/debian/DEBIAN_INSTALLER/debian-installer/packages/base-installer/kernel# > >ls > >alpha.sh arm64.sh armel.sh hppa.sh i386.sh kfreebsd-amd64.sh > >m68k.sh mipsel.sh powerpc.sh READMEsh4.shtests > >amd64.sh armeb.sh armhf.sh hurd-i386.sh ia64.sh kfreebsd-i386.sh > >Makefile mips.shppc64el.sh s390x.sh sparc.sh > >root@test-adrian1 > :/srv/sid-sparc64-sbuild/debian/DEBIAN_INSTALLER/debian-installer/packages/base-installer/kernel# > > > >There is apparently no sparc64 support in the base-installer package. > > > >Will fix that and upload a new ISO image :). > > That's cool, prio to that, there was: > > [del] > Jan 1 17:58:04 main-menu[150]: INFO: Menu item 'bootstrap-base' selected > Jan 1 17:58:04 base-installer: warning: Unknown architecture 'sparc64'. > [del] > > So that's probably the root cause? > > HTH, > Uli > -- > Dipl. Inf. Ulrich Teichert|e-mail: ulrich.teich...@gmx.de | Listening to: > Stormweg 24 |Imperial State Electric, The Estranged, > 24539 Neumuenster, Germany|The About Blanks, Cyanide Pills, Fu Manchu. > >
Re: New working sparc64 netinst image
So I was able to get past the 33% error on the partition by setting the -F flag for mkfs.ext4 in the debian install scripts. Guidance to the issue was found here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767682 Modified /lib/partman/commit.d/50format_ext3 and changed the line mkfs.$filesystem $device $usage >/dev/null; then to mkfs.$filesystem -F $device $usage >/dev/null; then Not sure if this is the best way to handle this issue but it did allow me to proceed further in testing the install process on my Sun Blade 2500. On Fri, Jan 1, 2016 at 9:16 AM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > On 01/01/2016 03:13 PM, Ulrich Teichert wrote: > > - the installer went ahead downloading, but failed to find a kernel for > > installation. Manually installing it in the target via chroot works. > > Can I get the exact error message, preferably from the log files under > /var/log? My suspicion is that debian-installer tries to install the > wrong kernel version and therefore fails. > > Apparently, being able to install the proper kernel version is a bit > tricky and according to Helge Deller (CC) is the main reason why he > uses snapshotted debian-ports.org mirrors for the installation. > > I have the suspicion that debian-installer looks for a particular > kernel version which was determined at build time. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: New working sparc64 netinst image
I have a server sitting in the cloud currently not doing anything useful. It has a fairly good Internet connection. If I am pointed to some instructions I could set up a dedicated mirror for SPARC64. On Tue, Dec 29, 2015 at 11:53 AM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > On 12/29/2015 03:15 PM, John Paul Adrian Glaubitz wrote: > > On 12/29/2015 03:07 PM, Knut Petter Ølberg wrote: > >> Started installing in an LDOM, seems to be working fine. Came as far as > >> specifying the mirror, where I'm a bit lost as to what I should specify > >> to make reprepo create a local repo for stretch. > > > > Normally you should be able to just use a regular Debian mirror, but > > when you use ftp.debian-ports.org/debian, it's not recognized as > > a mirror. > > I'm working on a quick mini-howto for reprepro with apt-cacher-ng and > it seems I have to rebuild the netinst image to have debian-installer > set the default suite to "unstable" (currently points to "stretch"). > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: the future of sparc in unstable
Well it is a good start. =D There are still complaints, though haven't seen the bug reports, that modern kernel's are unstable on certain peices of hardware. Personally I can't reproduce any of these issues, I have rolled out the latest kernel for a while now on some of my sparc systems, my T2000 has an uptime of about 80days and it's running wheezy but using a vanilla 3.13.9 build. There is also some problems with the kernel hanging in the early stages of the boot process, though once again I have not seen this. What the sparc port needs are a couple of people to become familiar with the Debian build process and to find major bugs report and fix them. I haven't checked but I think that SILO is currently a version or two ahead of what debian is using for it's installs. That might be the issue. Wish I had more time to invest in this. -Kieron On Thu, May 1, 2014 at 6:21 PM, Patrick Baggett wrote: > BTW, the sparc buildd looks like gcc 4-8.2-21 is successful and so is > gcc-4.9.0-1. I've installed them from sid. Crisis averted? > > Patrick > > > On Wed, Apr 30, 2014 at 4:04 PM, Sébastien Bernard wrote: > >> Le 30/04/2014 20:36, Patrick Baggett a écrit : >> >> >> >> >> On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote: >> >>> Hi, >>> >>> On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote: >>> > Indeed, the last good build seems to be gcc-4.8-4.8.2-19. >>> > Look at the changelog for the -20 they seems to have done something on >>> the sparc >>> > that blocks the generation of the libraries. >>> >>> A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As >>> there is >>> no build of gcc-4.9 on sparc, these binaries are missing. >>> >>> https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc >>> >>> So if you want to fix the sparc issue, you probably need to get gcc-4.9 >>> to >>> build there. When doing that, you need to start from a gcc-4.8 version >>> from >>> before the change, as newer version are not functional without the >>> packages >>> from gcc-4.9. >>> >>> ??? >> I thought jessie was using gcc-4.8 and not gcc-4.9 >> >> OK, so we additionally need to look into why gcc-4.9 is not installable? >> >> Patrick >> >> >> No, we don't. Period. >> >> I built the gcc-4.8-4.8-19, and all the binaries are there. >> I'm going to involve the gcc maintainer cause what they did broke >> completely the build be it jessie or sid. >> >> We have libgcc1, lib64gcc1, libstdc++6, and libstdc++6 available from >> the repositories in version 4.8.2-19. >> But, the new builds -20 and -21 have overriden all the other packages >> from -19 since they have been build ok. >> So, now, we have nothing to install because gcc-base-4.8_4.8.2-20 depends >> on libgcc1-4.8.2_4.8.2-20 which isn't build (this is the message from >> apt-get). >> >> And this is not solvable, we're halfway through, with partial -19 >> packages and missing packages -20. >> >> And if you think it has zero impact, think twice. The debootstrap is not >> able to build a sid install because of this. >> So, meanwhile, I'll setup a mini directory with the packages availables >> (I need to remember how to setup a debian repository again). >> >> All in all, this broken package has blocked the complete buildd, since >> there is no more libgcc1 and no more libstdc++ installable. >> >> Did I say there is no gcc-4.9 ? >> >> Here is the recipe for disaster for sparc. >> >> Seb >> > >
Re: the future of sparc in unstable
What is also weird is you have the debug package for it. So I am sure it compiled I think there might be something wrong with the packaging for it. On Wed, Apr 30, 2014 at 9:39 AM, Patrick Baggett wrote: > >>> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. >> libstdc++ and lib64stdc++ are not build, neither are build libgcc1. >> The last good build (with the missing libraries) is 4.8.2-16. >> Something broken on -20 and -21. >> >> > Oh, I see what you're saying. I get lib64stdc++-dev / libstdc++-dev, but > not the base lib64stdc++/libstdc++ > > And yeah, libgcc1 just isn't built, which is a major problem. Maybe we > need to look at diffs in the "debian" directory. > > Patrick >
Re: the future of sparc in unstable
I have also been able to build the gcc 4.8.2-21 packages as well. I am not sure what is causing the build systems so much grief when it comes to building these packages. Cheers, Kieron On Wed, Apr 30, 2014 at 9:27 AM, Patrick Baggett wrote: > I kicked off a gcc build (gcc-4.8_4.8.2-21) last night. It didn't have an > errors for me. I now have a bunch of *.deb files: > > figgles@ghost:~/src$ ls -1 *.deb > cpp-4.8_4.8.2-21_sparc.deb > g++-4.8-multilib_4.8.2-21_sparc.deb > g++-4.8_4.8.2-21_sparc.deb > gcc-4.8-base_4.8.2-21_sparc.deb > gcc-4.8-locales_4.8.2-21_all.deb > gcc-4.8-multilib_4.8.2-21_sparc.deb > gcc-4.8-plugin-dev_4.8.2-21_sparc.deb > gcc-4.8-source_4.8.2-21_all.deb > gcc-4.8_4.8.2-21_sparc.deb > gcj-4.8-jdk_4.8.2-21_sparc.deb > gcj-4.8-jre-headless_4.8.2-21_sparc.deb > gcj-4.8-jre-lib_4.8.2-21_all.deb > gcj-4.8-jre_4.8.2-21_sparc.deb > gcj-4.8-source_4.8.2-21_all.deb > gcj-4.8_4.8.2-21_sparc.deb > gdc-4.8_4.8.2-21_sparc.deb > gfortran-4.8-multilib_4.8.2-21_sparc.deb > gfortran-4.8_4.8.2-21_sparc.deb > gobjc++-4.8-multilib_4.8.2-21_sparc.deb > gobjc++-4.8_4.8.2-21_sparc.deb > gobjc-4.8-multilib_4.8.2-21_sparc.deb > gobjc-4.8_4.8.2-21_sparc.deb > lib64asan0-dbg_4.8.2-21_sparc.deb > lib64asan0_4.8.2-21_sparc.deb > lib64gcc-4.8-dev_4.8.2-21_sparc.deb > lib64gfortran-4.8-dev_4.8.2-21_sparc.deb > lib64objc-4.8-dev_4.8.2-21_sparc.deb > lib64stdc++-4.8-dev_4.8.2-21_sparc.deb > lib64stdc++6-4.8-dbg_4.8.2-21_sparc.deb > libasan0-dbg_4.8.2-21_sparc.deb > libasan0_4.8.2-21_sparc.deb > libgcc-4.8-dev_4.8.2-21_sparc.deb > libgcj14-awt_4.8.2-21_sparc.deb > libgcj14-dbg_4.8.2-21_sparc.deb > libgcj14-dev_4.8.2-21_sparc.deb > libgcj14_4.8.2-21_sparc.deb > libgfortran-4.8-dev_4.8.2-21_sparc.deb > libobjc-4.8-dev_4.8.2-21_sparc.deb > libstdc++-4.8-dev_4.8.2-21_sparc.deb > libstdc++-4.8-doc_4.8.2-21_all.deb > libstdc++-4.8-pic_4.8.2-21_sparc.deb > libstdc++6-4.8-dbg_4.8.2-21_sparc.deb > > > > > On Tue, Apr 29, 2014 at 3:12 PM, Sébastien Bernard wrote: > >> Le 26/04/2014 21:33, Ralf Treinen a écrit : >> >> Hello, >>> >>> we currently have in unstable/main/sparc precisely 35491 packages, of >>> a total of 40634 available packages, that cannot be installed in the >>> current version of unstable: >>> >>> % dose-debcheck --fg Packages --deb-ignore-essential >>> background-packages: 0 >>> foreground-packages: 40634 >>> total-packages: 40634 >>> broken-packages: 35491 >>> >>> The most common cause seems to be that libgcc1 1:4.8.2-19 depends on >>> gcc-4.8-base (= 4.8.2-19), and version 4.8.2-20 is in the archive. I just >>> found this when I investigated why the daily run of my dose-debcheck >>> script >>> explodes the last 3 days. >>> >>> -Ralf. >>> >>> >>> I tried to build the gcc-4.8-4.8.2-20 and the build is broken. >> libstdc++ and lib64stdc++ are not build, neither are build libgcc1. >> The last good build (with the missing libraries) is 4.8.2-16. >> Something broken on -20 and -21. >> >> My .002 contribution. >> >> Seb >> >> >> >> -- >> To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org >> Archive: https://lists.debian.org/53600797.2010...@nerim.net >> >> >
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
https://wiki.debian.org/PortsSparc Started a catagory of major bugs. Please place links and titles to the bug report in this list so we can better track the status and reference the problems quickly. One of my major problems with helping debian and the sparc port has been simply figuring out what is wrong. I have fixed a lot of problems upstream with KDE and alignment issues, and even have the nouveau driver working with some GeForces on sparc. It would be sad to see my plucky little sparc machines no longer get updates. -Kieron On Tue, Apr 29, 2014 at 6:45 PM, Sébastien Bernard wrote: > Le 30/04/2014 00:12, Kieron Gillespie a écrit : > > Do we currently have a master list of all the major bugs facing the >> Sparc Port right now? >> >> I don't think so. I haven't been able to get one. > > You can start one. > > Seb >
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
Do we currently have a master list of all the major bugs facing the Sparc Port right now? On Tue, Apr 29, 2014 at 3:53 PM, Patrick Baggett wrote: > > > > On Tue, Apr 29, 2014 at 2:35 PM, Patrick Baggett < > baggett.patr...@gmail.com> wrote: > >> Yes, that's the one. Interestingly, in glibc-2.19, this change is >> reverted. It is present in glibc-2.17 & glibc-2.18 as released by GNU. >> Oddly, in glibc git, the buggy version appears. >> >> >> > I've filed a bug with glibc [1] and let the author know that there is a > problem. In the meantime, I'll try to figure out what the problem is. I > think we may need to file a debian bug though since it will require a glibc > update. Sebastien, can you handle that? > > Patrick > > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=16885 >
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
On Tue, Apr 29, 2014 at 10:47 AM, Patrick Baggett wrote:
>
>
> On Tue, Apr 29, 2014 at 9:34 AM, Kieron Gillespie <
> ciaran.gilles...@gmail.com> wrote:
>
>> I am currently investigating this unusual behavior with strcmp, and I am
>> unable to reproduce the problem using the test_strcmp example provided.
>>
>> It returns the correct output of,
>>
>>
>> result from strcmp('\','\0001' is -1)
>>
>> This was built on Debian Wheezy with a T2000 SPARC processor using GCC
>> 4.6.3-14 from Debian Wheezy Repo.
>>
>>
> Can you set a breakpoint in strcmp and tell me what the file path is?
> Perhaps there is a sun4v specific function (optimized version) that does
> not have a bug?
>
> Patrick
>
>
Here is the information from strcmp breakpoint
---CUT---
Breakpoint 1, 0xf7ebd300 in strcmp () from /lib/sparc-linux-gnu/libc.so.6
(gdb) disas strcmp
Dump of assembler code for function strcmp:
=> 0xf7ebd300 <+0>: sethi %hi(0x101), %g1
0xf7ebd304 <+4>: btst 7, %o0
0xf7ebd308 <+8>: bne,pn %icc, 0xf7ebd4a0
0xf7ebd30c <+12>:or %g1, 0x101, %g1
0xf7ebd310 <+16>:andcc %o1, 7, %g3
0xf7ebd314 <+20>:bne,pn %icc, 0xf7ebd4e4
0xf7ebd318 <+24>:sllx %g1, 0x20, %g2
0xf7ebd31c <+28>:ldx [ %o0 ], %o2
---CUT---
As far as I can tell from stepping through this it seems like a correctly
implementation of strcmp.
---CUT---
(gdb) info reg
g0 0x0 0
g1 0x20754 132948
g2 0x33dfaf454393588
g3 0x3dfaf4 4061940
g4 0xf869cbac -127284308
g5 0x28 40
g6 0xfeff 65279
g7 0xf7ff66d0 -134256944
o0 0xdc48 -9144
o1 0xdc50 -9136
o2 0xdd34 -8908
---CUT---
You can see that o0 and o1 are holding the pointers for the strings
correctly and examining the value of memory at those location appears to be
correct.
With -O3 the call is the same. So I am not sure what is going on, would
like to see an "info reg" at the breakpoint of strcmp on the affected
systems. Also an examiniation of the memory that o0 and o1 are pointing too.
-Kieron
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
I'll rebuild one of my SunBlade 2500 latter with sid and see if I get the
same result. If it doesn't show the symptom I will rebuild my T2000 and see
if it is something specific to the Niagara T1.
-Kieron
On Tue, Apr 29, 2014 at 10:45 AM, Sébastien Bernard wrote:
> Le 29/04/2014 16:34, Kieron Gillespie a écrit :
>
> I am currently investigating this unusual behavior with strcmp, and I am
>> unable to reproduce the problem using the test_strcmp example provided.
>>
>> It returns the correct output of,
>>
>> result from strcmp('\','\0001' is -1)
>>
>> This was built on Debian Wheezy with a T2000 SPARC processor using GCC
>> 4.6.3-14 from Debian Wheezy Repo.
>>
>> Cheers,
>> Kieron
>>
>> Hum, I tried with a T5220 with debian 7.5 /wheezy.
> Same result, the strcmp is ok.
> Could you try with unstable ?
>
> Cheers.
>
>
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
I am currently investigating this unusual behavior with strcmp, and I am
unable to reproduce the problem using the test_strcmp example provided.
It returns the correct output of,
result from strcmp('\','\0001' is -1)
This was built on Debian Wheezy with a T2000 SPARC processor using GCC
4.6.3-14 from Debian Wheezy Repo.
Cheers,
Kieron
On Tue, Apr 29, 2014 at 3:06 AM, Thomas Schmitt wrote:
> Hi,
>
> Sébastien Bernard:
> > Cheers to team work.
>
> Special cheers to Patrick Baggett !
>
> And thanks to all who cared for this problem. I'd need more
> users who don't shrug but complain and tell me that i'm wrong.
>
> The bug fix is now committed as
> http://libburnia-project.org/changeset/5324
>
> (We still did not find any alignment problem. Does that mean
> we did not test hard enough ?)
>
>
> > The real function is in sysdeps/sparc/sparc64/strcmp.S .
> > So complicated that I'm not surprised a bug came inside.
>
> I found a medium complicated one in the libc code which
> you provided for me in /home/thomas
> eglibc-2.18/string/bits/string2.h
> Already too bloated for me to spot any mistake or correctness.
>
>
> Have a nice day :)
>
> Thomas
>
>
> --
> To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> https://lists.debian.org/30925670721203172...@scdbackup.webframe.org
>
>
Re: Compiling vanilla kernel issues.
So still no joy on my Sun Blade2500 going to post my exact steps, and maybe I'm still just missing something stupid. tar xfv linux-3.11.1.tar.xz cd linux-3.11.1 cp /boot/config-3.2.0-4-sparc64-smp ./.config make oldconfig make clean make -j2 deb-pkg cd ../ dpkg -i *.deb vi /etc/silo.conf reboot and kernel panic trying to find the root file system. So am I copying the old config incorrectly? I get asked a lot of questions about configuring options, which I just go with the default response. Does anyone have a build I can download? Wondering if I try installing a known working set of deb packages if the issue goes away. Thanks again. -Kieron On Mon, Sep 23, 2013 at 10:40 AM, Hartwig Atrops wrote: > Hi. > > I repeated the test on a Blade 100 (ATAPI/IDE system, Openboot 4, test > kernel > 3.11.1): > > No problems ... > > Regards, > >Hartwig > > > On Saturday 21 September 2013 22:37:02 Kieron Gillespie wrote: > > Strange as those steps you mentioned are exactly what I am doing on my > two > > SPARC systems. > > > > I am going to have to guess this is an issue with these particular pieces > > of hardware the Sun Blade 2500 and the Sun Fire T2000. > > > > Thanks for the help, I just wanted to eliminate the possibility I was > just > > making some stupid mistake. Looks like it's more than that. I'll > > investigate more. > > > > -Kieron > > > > On Sat, Sep 21, 2013 at 3:53 PM, Hartwig Atrops > wrote: > > > Hi. > > > > > > I used the Debian Linux Kernel Handbook: > > > > > > http://kernel-handbook.alioth.debian.org/ > > > > > > I fetched the 3.11.1 kernel source from kernel.org (wget) and > unpacked it > > > under /usr/src. > > > > > > During installation of Wheezy, I installed my usual tool set including > > > make, > > > gcc, g++ etc. > > > > > > To build the kernel, I additionally installed: > > > > > > build-essentials > > > fakeroot > > > devscripts (I don't think we need that) > > > > > > and run apt-get build-dep linux > > > > > > And now: > > > > > > copy configuration from /boot > > > make oldconfig > > > make clean (I don't think this is necessary) > > > make deb-pkg > > > > > > installation via dpkg -i (4 packages) > > > > > > configure /boot/silo.conf (additional entry) > > > > > > and reboot - it works. > > > > > > You didn't mention the build packages, the rest looks the same ... > > > > > > Regards, > > > > > >Hartwig > > > > > > On Saturday 21 September 2013 17:42:00 Kieron Gillespie wrote: > > > > Could you send me a link to the exact procedure you used. I keep find > > > > > > like > > > > > > > four different ways to make a vanilla kernel for Debian. > > > > > > > > Two of my systems are SCSI based and both of those have problems > when I > > > > > > do > > > > > > > the standard > > > > > > > > cp /boot/config- ./.config > > > > > > > > make oldconfig > > > > make deb-pkg > > > > > > > > dpkg -i linux-*.deb > > > > > > > > > > > > -Kieron > > > > > > > > On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops > > > > > > wrote: > > > > > Hi. > > > > > > > > > > Last night, I've built a kernel 3.11.1 from kernel.org the Debian > way > > > > > > (as > > > > > > > > described in "Debian Linux Kernel Handbook") - without any > problems. > > > > > > > > > > My test environment: a fresh installation of Wheezy (7.0.1) on a > Sun > > > > > Ultra 60, > > > > > i.e. a SCSI machine. > > > > > > > > > > I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I > > > > > have > > > > > > to > > > > > > > > set > > > > > up this machine first - that will take a while. > > > > > > > > > > Regards, > > > > > > > > > >Hartwig > > > > > > > > > > On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: > > > > > > So current when I build the vanilla kernel using the typical > Debian > > > > > >
Re: Compiling vanilla kernel issues.
Strange as those steps you mentioned are exactly what I am doing on my two SPARC systems. I am going to have to guess this is an issue with these particular pieces of hardware the Sun Blade 2500 and the Sun Fire T2000. Thanks for the help, I just wanted to eliminate the possibility I was just making some stupid mistake. Looks like it's more than that. I'll investigate more. -Kieron On Sat, Sep 21, 2013 at 3:53 PM, Hartwig Atrops wrote: > Hi. > > I used the Debian Linux Kernel Handbook: > > http://kernel-handbook.alioth.debian.org/ > > I fetched the 3.11.1 kernel source from kernel.org (wget) and unpacked it > under /usr/src. > > During installation of Wheezy, I installed my usual tool set including > make, > gcc, g++ etc. > > To build the kernel, I additionally installed: > > build-essentials > fakeroot > devscripts (I don't think we need that) > > and run apt-get build-dep linux > > And now: > > copy configuration from /boot > make oldconfig > make clean (I don't think this is necessary) > make deb-pkg > > installation via dpkg -i (4 packages) > > configure /boot/silo.conf (additional entry) > > and reboot - it works. > > You didn't mention the build packages, the rest looks the same ... > > Regards, > >Hartwig > > On Saturday 21 September 2013 17:42:00 Kieron Gillespie wrote: > > Could you send me a link to the exact procedure you used. I keep find > like > > four different ways to make a vanilla kernel for Debian. > > > > Two of my systems are SCSI based and both of those have problems when I > do > > the standard > > > > cp /boot/config- ./.config > > > > make oldconfig > > make deb-pkg > > > > dpkg -i linux-*.deb > > > > > > -Kieron > > > > On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops > wrote: > > > Hi. > > > > > > Last night, I've built a kernel 3.11.1 from kernel.org the Debian way > (as > > > described in "Debian Linux Kernel Handbook") - without any problems. > > > > > > My test environment: a fresh installation of Wheezy (7.0.1) on a Sun > > > Ultra 60, > > > i.e. a SCSI machine. > > > > > > I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I have > to > > > set > > > up this machine first - that will take a while. > > > > > > Regards, > > > > > >Hartwig > > > > > > On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: > > > > So current when I build the vanilla kernel using the typical Debian > > > > > > method > > > > > > > with make deb-pkg I end up with a kernel that panic's on boot. > > > > > > > > It says, > > > > --CUT-- > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > > > unknown-block(0,0) > > > > > > > > CPU: 0 PID: 1 Comm: swapper/1 Not tainted 3.12.0-rc #1 > > > > Call Trace: > > > > --END CUT-- > > > > > > > > Any ideas? If someone has instructions on how they typically build > > > > there kernel for SPARC system I would like to know. Though this is > how > > > > I always have done it in the past it just recently stop working after > > > > 3.8.x > > > > > > series. > > > > > > > On Thu, Sep 19, 2013 at 9:14 AM, Patrick Baggett > > > > > > > > wrote: > > > > > I didn't have any problems, but I'm not using initramfs. To build a > > > > > kernel 'the debian way', you might need to find a guide or maybe > > > > > > someone > > > > > > > > else can chime in? > > > > > On Sep 18, 2013 10:05 PM, "Kieron Gillespie" < > > > > > > ciaran.gilles...@gmail.com> > > > > > > > > wrote: > > > > >> Hello everyone, > > > > >> > > > > >> Was wondering if anyone had any success compiling any of the > vanilla > > > > >> Linux kernel's on their SPARC wheezy systems with anything after > > > > > > version > > > > > > > >> 3.8.x. > > > > >> > > > > >> Every time I try to build myself a new kernel I seem to end up > with > > > > >> a kernel that is unable to boot complaining about not being able > to > > > > >> find the root file system. I was wondering if anyone has any > > > > >> information on how I can configure and build the Linux kernel for > my > > > > >> various SPARC systems. > > > > >> > > > > >> -Kieron > > > > > > -- > > > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org > > > with a subject of "unsubscribe". Trouble? Contact > > > listmas...@lists.debian.org > > > Archive: > > > http://lists.debian.org/201309210911.41123.hartwig.atr...@arcor.de > > > > -- > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/201309212153.31868.hartwig.atr...@arcor.de > >
Re: Compiling vanilla kernel issues.
Could you send me a link to the exact procedure you used. I keep find like four different ways to make a vanilla kernel for Debian. Two of my systems are SCSI based and both of those have problems when I do the standard cp /boot/config- ./.config make oldconfig make deb-pkg dpkg -i linux-*.deb -Kieron On Sat, Sep 21, 2013 at 3:11 AM, Hartwig Atrops wrote: > Hi. > > Last night, I've built a kernel 3.11.1 from kernel.org the Debian way (as > described in "Debian Linux Kernel Handbook") - without any problems. > > My test environment: a fresh installation of Wheezy (7.0.1) on a Sun Ultra > 60, > i.e. a SCSI machine. > > I'm going to do a test with an ATAPi/IDE Blade 100 as well, but I have to > set > up this machine first - that will take a while. > > Regards, > > Hartwig > > On Friday 20 September 2013 03:37:30 Kieron Gillespie wrote: > > So current when I build the vanilla kernel using the typical Debian > method > > with make deb-pkg I end up with a kernel that panic's on boot. > > > > It says, > > --CUT-- > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > > > CPU: 0 PID: 1 Comm: swapper/1 Not tainted 3.12.0-rc #1 > > Call Trace: > > --END CUT-- > > > > Any ideas? If someone has instructions on how they typically build there > > kernel for SPARC system I would like to know. Though this is how I always > > have done it in the past it just recently stop working after 3.8.x > series. > > > > > > On Thu, Sep 19, 2013 at 9:14 AM, Patrick Baggett > > > > wrote: > > > I didn't have any problems, but I'm not using initramfs. To build a > > > kernel 'the debian way', you might need to find a guide or maybe > someone > > > else can chime in? > > > On Sep 18, 2013 10:05 PM, "Kieron Gillespie" < > ciaran.gilles...@gmail.com> > > > > > > wrote: > > >> Hello everyone, > > >> > > >> Was wondering if anyone had any success compiling any of the vanilla > > >> Linux kernel's on their SPARC wheezy systems with anything after > version > > >> 3.8.x. > > >> > > >> Every time I try to build myself a new kernel I seem to end up with a > > >> kernel that is unable to boot complaining about not being able to find > > >> the root file system. I was wondering if anyone has any information on > > >> how I can configure and build the Linux kernel for my various SPARC > > >> systems. > > >> > > >> -Kieron > > > > -- > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/201309210911.41123.hartwig.atr...@arcor.de > >
Re: Compiling vanilla kernel issues.
So current when I build the vanilla kernel using the typical Debian method with make deb-pkg I end up with a kernel that panic's on boot. It says, --CUT-- Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/1 Not tainted 3.12.0-rc #1 Call Trace: --END CUT-- Any ideas? If someone has instructions on how they typically build there kernel for SPARC system I would like to know. Though this is how I always have done it in the past it just recently stop working after 3.8.x series. On Thu, Sep 19, 2013 at 9:14 AM, Patrick Baggett wrote: > I didn't have any problems, but I'm not using initramfs. To build a kernel > 'the debian way', you might need to find a guide or maybe someone else can > chime in? > On Sep 18, 2013 10:05 PM, "Kieron Gillespie" > wrote: > >> Hello everyone, >> >> Was wondering if anyone had any success compiling any of the vanilla >> Linux kernel's on their SPARC wheezy systems with anything after version >> 3.8.x. >> >> Every time I try to build myself a new kernel I seem to end up with a >> kernel that is unable to boot complaining about not being able to find the >> root file system. I was wondering if anyone has any information on how I >> can configure and build the Linux kernel for my various SPARC systems. >> >> -Kieron >> >
Compiling vanilla kernel issues.
Hello everyone, Was wondering if anyone had any success compiling any of the vanilla Linux kernel's on their SPARC wheezy systems with anything after version 3.8.x. Every time I try to build myself a new kernel I seem to end up with a kernel that is unable to boot complaining about not being able to find the root file system. I was wondering if anyone has any information on how I can configure and build the Linux kernel for my various SPARC systems. -Kieron
Re: Roll call for porters of architectures in sid and testing
Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the jessie release: For SPARC64, I - test a lot of the packages for KDE4 Desktop - testing and currently preparing patches for Iceweasel - test Vanilla build of the Linux kernel, trying to find out why everything after 2.8 breaks certain builds. - currently own a Sun Blade 2500, a Netra X1, and a SunFire T2000 - help port random projects to Sparc64 For Alpha, I - test basic functionality of Xorg and XFCE - port random projects to Alpha I am not a DD/DM On Sun, Sep 1, 2013 at 3:33 AM, Niels Thykier wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, > > As we announced in [LAST-BITS], we would like to get a better idea of > that status of the ports, to make an informed decision about which > port can be released with jessie. One of the steps is to get an > overview of which of the porters are (still) active for each > port. Once the results from the role-call are in, we will request > other information about the status of the ports. In the meantime, feel > free to update and collect info about the ports in the Debian wiki[WIKI]. > > If you are (or intend to become) an active porter for the lifetime of > jessie, then please send a signed email explaining your involvement in > the port to the Release Team before > 1st of October 2013. Please explain the level of your involvement in > the port. > > Feel free to use the following template as your reply: > > """ > Hi, > > I am an active porter for the following architectures and I intend > to continue this for the lifetime of the jessie release: > > For , I > - test (most|all) packages on this architecture > - fix toolchain issues > - triage arch-specific bugs > - fix arch-related bugs > - maintain buildds > - ... > > > > > """ > > Niels, on behalf of the release team > > [LAST-BITS] > http://lists.debian.org/debian-devel-announce/2013/08/msg6.html > > [WIKI] https://wiki.debian.org/ArchiveQualification/Jessie > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.14 (GNU/Linux) > > iQIcBAEBCAAGBQJSIu2TAAoJEAVLu599gGRC86EP/j/7FEZ9pxpTEHrBI41GTu6r > nENS5kAZAuxFQHfYLtKexBcgneGd6cgdmr3cIoh1ZL9lJgXq74X8FL5IbWNqUw9S > o9UQWpZJiwIIlH4fqSgFVLIphI0DQr7dXI7xcDIm4kl6Fdruo1tGxX8xqL23jzdP > nQb3jrXv3bj5943MfWeCbODILv2N6qev9VtWeQ6Wmh8PvxRUl7VqgdQaeHtlMsUp > TQT5fz0cw8gc2amlwlOZxaGDV2C8mHboJIKMEsu79BK4SlFSED9rXn4juFPUnAgG > uADsMdBBqEIgSMN42cPHQju+KLfJe/+xScmlzzDS/d7aWWs02TibcQ1ZnPi+bcgp > bd/Wa0lms+Fc2OpcuFle9Lwo+2B+ka1Dd3itm+D0SbmrxoGi6CuMMwydLcQbSJ73 > hHw9HJEIQr2x/ZItNPJrSvvj50rwYXcmFbxtVAwv2pFXfQ37iukYgAaaMvnwpNNJ > 6dM1coCF9skNkXLO8rkZ+5aupGgjpS9BdKKAEQrPy/aoaW9KNCZrLQeA4C3QySBU > OcCNBv7taSjVAVNszKtRIQpu2gzFGAV0u9Gj41qW1JzDHYrmAvMyGxrndOxTmaFr > p05QWgcMsPhNvdHjd6sWLyzJ5NYUKksCPMRgCc0BEd6moIyrt7UFsp2+guJZPBJ0 > pffEJGK2iGtrWmJfElof > =TUeZ > -END PGP SIGNATURE- > > > -- > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20130901073351.a92862...@thykier.net > >
Any experience with Radeons on SPARC?
Hello everyone, I was wondering if anyone has any experience with running stock PC graphics cards on SPARC systems. So far the only one I was able to get working well enough was the NVIDIA GeForce FX 5200 PCI. I have a Radeon HD4250 PCI that I would love to get running but am currently having problems getting it to run. I was wondering if anyone has an experience getting the radeon driver working on SPARC system with Debian. -Kieron Gillespie -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f84ca7a.9060...@gmail.com
IOMMU: Ran out of contexts. errors then the system reboots.
So I just spent a week battling some really strange errors on my Sun Blade 2500 system and I think I'm nearing something that could be called stable. Except one last problem. After a while of using the system I will get this message all over my dmesg log. IOMMU: Ran out of contexts. Then after a while of this the system will reboot all on it's own. I was wondering if anyone else had experience with this problem. -Kieron Gillespie -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caphxfefpdafvfnf7eqcspjwk_zxbu96dpegy7r01vea+xvd...@mail.gmail.com
Re: gcc: Internal Compiler error: Bus error randomly occurs.
I am running gcc version 4.6.3 so it isn't that. I too wasn't having any
problems with my older Sparc systems, Ultra 5 and Blade 100. Without
Xorg running my kernel compiling hasn't been interrupted by the Bus
error. I have also been running into a known bug with the kernel
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648766 that I am going
to try and set up a kernel debugging environment and start trying to
find the problem. I feel like all these problems I have are related.
-Kieron
On 04/02/2012 01:10 PM, Patrick Baggett wrote:
I run Xorg with nouveau on that Ultra10 and I too get bus errors from
nouveau, but I do compiles all the time without problem. I understand
that the problem is intermittent -- perhaps it is related to an older
GCC version? I'm using GCC 4.6.x and I have no problems what so ever.
On Mon, Apr 2, 2012 at 11:59 AM, Kieron Gillespie
mailto:ciaran.gilles...@gmail.com>> wrote:
The problem is that there is no particular case that it Bus Errors
on with gcc. I am right now trying to see if the random Bus Errors
have anything to do with the nouveau driver giving me Kernel
unaligned access errors. So right now I am having this system
compile the Linux kernel without Xorg running which when Xorg was
running the Bus Error happened with the unaligned access errors.
So it may just be this driver bug I have been having.
Kieron
On 04/02/2012 10:57 AM, Patrick Baggett wrote:
I haven't had any bus errors while compiling, and I do a fairly
good bit of it on a Sun Ultra 10 (UltraSPARC IIi, not IIIi like
the Blade 2500). Do have a *.c/*.cpp test case I can try to
compile that gives you SIGBUS? Also, what version of GCC are you
using?
Patrick
On Sun, Apr 1, 2012 at 8:09 PM, Kieron Gillespie
mailto:ciaran.gilles...@gmail.com>>
wrote:
Hello everyone,
I recently got a Sun Blade 2500, and have been trying to
track down some bugs. But one bug that I have constantly
noticed is that gcc will randomly get an Internal Compiler
error: Bus error message. Now all I normally have to do is
rerun the compiler and the error doesn't occur again. Though
this is quite troubling and I was wondering if anyone has any
idea what could be causing it?
-Kieron Gillespie
--
To UNSUBSCRIBE, email to
debian-sparc-requ...@lists.debian.org
<mailto:debian-sparc-requ...@lists.debian.org>
with a subject of "unsubscribe". Trouble? Contact
listmas...@lists.debian.org <mailto:listmas...@lists.debian.org>
Archive: http://lists.debian.org/4f78fc35.60...@gmail.com
Re: gcc: Internal Compiler error: Bus error randomly occurs.
The problem is that there is no particular case that it Bus Errors on with gcc. I am right now trying to see if the random Bus Errors have anything to do with the nouveau driver giving me Kernel unaligned access errors. So right now I am having this system compile the Linux kernel without Xorg running which when Xorg was running the Bus Error happened with the unaligned access errors. So it may just be this driver bug I have been having. Kieron On 04/02/2012 10:57 AM, Patrick Baggett wrote: I haven't had any bus errors while compiling, and I do a fairly good bit of it on a Sun Ultra 10 (UltraSPARC IIi, not IIIi like the Blade 2500). Do have a *.c/*.cpp test case I can try to compile that gives you SIGBUS? Also, what version of GCC are you using? Patrick On Sun, Apr 1, 2012 at 8:09 PM, Kieron Gillespie mailto:ciaran.gilles...@gmail.com>> wrote: Hello everyone, I recently got a Sun Blade 2500, and have been trying to track down some bugs. But one bug that I have constantly noticed is that gcc will randomly get an Internal Compiler error: Bus error message. Now all I normally have to do is rerun the compiler and the error doesn't occur again. Though this is quite troubling and I was wondering if anyone has any idea what could be causing it? -Kieron Gillespie -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org <mailto:debian-sparc-requ...@lists.debian.org> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org <mailto:listmas...@lists.debian.org> Archive: http://lists.debian.org/4f78fc35.60...@gmail.com
gcc: Internal Compiler error: Bus error randomly occurs.
Hello everyone, I recently got a Sun Blade 2500, and have been trying to track down some bugs. But one bug that I have constantly noticed is that gcc will randomly get an Internal Compiler error: Bus error message. Now all I normally have to do is rerun the compiler and the error doesn't occur again. Though this is quite troubling and I was wondering if anyone has any idea what could be causing it? -Kieron Gillespie -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f78fc35.60...@gmail.com
Default kernel build on SPARC doesn't have SMP enabled?
So I recently upgraded my SPARC development system to a Sun Blade 2500 with 2 SPARC IIIi processors. I would like to start working on fixing bugs for the SPARC port of Debian, lots of bus errors, and was wondering how I could get involved in patching KDE applications and maybe work on other major problems including hardware support for graphics cards on the system. Kieron Gillespie.
