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
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
baggett.patr...@gmail.comwrote:
I kicked off a gcc build
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
baggett.patr...@gmail.comwrote:
I tried to build the gcc-4.8-4.8.2-20 and the build is broken.
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
/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
On Tue, Apr 29, 2014 at 10:47 AM, Patrick Baggett baggett.patr...@gmail.com
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
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
baggett.patr...@gmail.comwrote:
On Tue, Apr 29, 2014 at 2:35 PM, Patrick Baggett
baggett.patr...@gmail.com wrote:
Yes, that's the one.
...@nerim.netwrote:
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
to load the firmware package and see if that causes the problem as
it is the one package I have not reinstalled.
On 04/07/2012 08:22 AM, Jonathan Nieder wrote:
Kieron Gillespie wrote:
With a completely clean install of Debian and every major version of
the Linux kernel I haven't run
, Jonathan Nieder wrote:
Kieron Gillespie wrote:
I am right now testing one major kernel version at a time, and on
the 3.0.0-1 I got
Just to be clear, if each time you test the version halfway between
the newest known-good and oldest known-bad kernel then you only have
to test log(n) kernels
~experimental.1
tags 648766 + upstream
quit
Kieron Gillespie wrote:
Now with that said I can't seem to crash the 2.6.32 kernel in the
same way with SMP off, haven't tried with SMP on yet, but I have a
feeling that will work fine as well. So this seems like it's some
sort of regression
kernel bug.
-Kieron
On 04/03/2012 01:29 PM, Jonathan Nieder wrote:
Kieron Gillespie wrote:
Here are the dmesg output from the current system running Linux
3.2.13 with SMP enabled with tickless disabled.
Great.
Is this reproducible without nouveau? It might be possible to test
by putting
[105595a8]
nv_wo32+0xb0/0xbc [nouveau]
On 04/03/2012 12:02 PM, Jonathan Nieder wrote:
severity 648766 important
quit
Kieron Gillespie wrote:
I've attached some images to this bug message, not sure if they will
appear
Received; thanks much.
What version of the kernel are you using? Full
wrote:
Kieron Gillespie wrote:
Here are the dmesg output from the current system running Linux
3.2.13 with SMP enabled with tickless disabled.
Great.
Is this reproducible without nouveau? It might be possible to test
by putting
blacklist nouveau
in /etc/modprobe.d/kg-disable
So I have obtain a similar error again, this time CPU1 locked up though.
Once again all I have are images of the crash, I am still trying to set
up a serial connection so I can log these errors better. I am right now
trying out different configuration options in the kernel to see if one
of
I own a Sun Blade2500 that has two TI UltraSparc IIIi (Jalapeno) and
1GB of RAM using Kernel Version 3.2.12 with SMP enabled.
When the system is in high load this tends to happen. I have only seen
the fault occur with CPU0 though.
I was wondering if anyone has any ideas of how to fix this? My
Package: Konsole
Version: 4:4.4.4-1
When ever I attempt to invoke any command in konsole that seems to clear
previously written text in the terminal it will crash with a signal Bus
Error.
This can be recreated simply by trying to use the clear command.
My system is a Sun Microsystems Ultra 5.
17 matches
Mail list logo
