The backtraces mention "cheetah", which is the UltraSPARC III CPU IIRC.
Also, Blade 100, Ultra 5/10 are single (US-II) CPU systems -- perhaps it is
related to also having SMP? You could try running a UP kernel and see what
happens...
Patrick
On Mon, Apr 2, 2012 at 12:34 PM, Kieron Gillespie <
cia
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.o
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, 201
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
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
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
6 matches
Mail list logo