On Tue, 2006-09-26 at 05:46 +, Fabio Massimo Di Nitto wrote:
> I have asked our sysadmins to upgrade/install an edgy kernel on davis
> (where we can reproduce the problem) to see if a new kernel fixes this
> issue. ETA is within 24/48 hours. davis also needs some hw love and
> that's why they c
I have asked our sysadmins to upgrade/install an edgy kernel on davis
(where we can reproduce the problem) to see if a new kernel fixes this
issue. ETA is within 24/48 hours. davis also needs some hw love and
that's why they can't reboot it right away.
Fabio
--
fails to build on ppc
https://laun
Well, it didn't reproduce on my quad g5, at least not right away.
However, looking at the source is a bit scary ... that thing is just a
steaming pile of poo to re-use paulus expression... especially the way
it "synchronizes" with the timer thread without using any
synchronisation primitives, not e
The easiest way to reproduce it is to upgrade to edgy running dapper
kernel and:
apt-get source ruby1.8
sudo apt-get build-dep ruby1.8
sudo apt-get install fakeroot
cd ruby1.8-$version
dpkg-buildpackage -rfakeroot -uc -us -b
If upgrading to edgy is not an option you can easily use debootstrap to
Can I get a quick step-by-step howto reproduce the build environment ? I
have a quad g5 running dapper here that should be able to reproduce. Or
at least how to get the source of the bits that are segfaulting...
There is something that comes to mind right away though: rb_thread_* . I
don't know wh
Ben,
do you happen to have any idea what the problem could be? the kernel on
these machines is .15 from dapper ppc64.
Thanks
Fabio
** Description changed:
Build segfaults on ppc, but only on the machines in the datacentre so
- far.
+ far (that are running 64bit kernels)
--
fails to build on
Unfortunately, my sched_setaffinity workaround doesn't actually appear
to work.
--
fails to build on ppc
https://launchpad.net/bugs/61861
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is a threading bug. While applying gdb to the problem, I noticed
that (a) the thing that was NULL was prot_tag and (b) prot_tag was
fiddled with in some rb_thread_* functions, so I tried building with
threading disabled, and it built fine (at least 'debian/rules build';
'debian/rules binary' f
(The sched_setaffinity rune above effectively disables concurrent
execution of threads without ABI problems by binding the process to run
on only a single CPU. It is definitely not an optimal solution.)
--
fails to build on ppc
https://launchpad.net/bugs/61861
--
ubuntu-bugs mailing list
ubuntu
** Description changed:
- Build segfaults on pcc, but only on the machines in the datacentre so
+ Build segfaults on ppc, but only on the machines in the datacentre so
far.
--
fails to build on ppc
https://launchpad.net/bugs/61861
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
10 matches
Mail list logo