Am 17.01.2014 18:14, schrieb Daniel Frey:
On 01/16/2014 08:07 PM, lovely2 wrote:
I doubt this is a memory problem. I've just had the same problem with
glibc-2.17 and python. I manually went back to glibc-2.16 and everything is
fine again. I then tried re-emerging all the python versions with
On 01/16/2014 08:07 PM, lovely2 wrote:
I doubt this is a memory problem. I've just had the same problem with
glibc-2.17 and python. I manually went back to glibc-2.16 and everything is
fine again. I then tried re-emerging all the python versions with glibc-2.16
installed and then re-emerged
And bingo was his nameo. Updated kernel to 3.6.25 and emerge glibc-2.17 and
python still works. :)
--
View this message in context:
http://gentoo.2317880.n4.nabble.com/updating-old-box-segfaults-with-python-tp274112p274876.html
Sent from the gentoo-user mailing list archive at Nabble.com.
I doubt this is a memory problem. I've just had the same problem with
glibc-2.17 and python. I manually went back to glibc-2.16 and everything is
fine again. I then tried re-emerging all the python versions with glibc-2.16
installed and then re-emerged glibc-2.17 and had the same problem.
After
On 01/08/2014 11:39:21 PM, Stefan G. Weichinger wrote:
Am 08.01.2014 19:47, schrieb Grant Edwards:
On 2014-01-08, Stefan G. Weichinger li...@xunil.at wrote:
Looking forward to some clever suggestions ;-)
Well, I'd start by running memtest86 overnight just to eliminate the
possibility of
Am 09.01.2014 09:16, schrieb Helmut Jarausch:
You can use sys-apps/memtester without physical access to the machine.
I had cases where memtester found errors which memtest86 didn't.
One of these cases was a machine which probably had a cache coherence
problem
since the error showed up only
On 01/09/2014 10:59:45 AM, Stefan G. Weichinger wrote:
Am 09.01.2014 09:16, schrieb Helmut Jarausch:
You can use sys-apps/memtester without physical access to the
machine.
I had cases where memtester found errors which memtest86 didn't.
One of these cases was a machine which probably had
Am 09.01.2014 11:15, schrieb Helmut Jarausch:
You can't test all of memory, especially not low memory.
But if you had a problem with some chip mapped to low memory
I doubt Linux would even boot.
Furthermore, memtester locks pages, i.e. it disables paging.
So the machine might not be very
Am 09.01.2014 09:16, schrieb Helmut Jarausch:
Did you try www.sysresccd.org/ version 3.8.1? I'm not sure if it is
based on
glibc-2.17, yet.
2.15-r3 ... just booted it in a VM and looked it up.
Stefan G. Weichinger lists at xunil.at writes:
yesterday I started to upgrade an older gentoo server at a customer. It
has only been updated now and then as they tend to save money and rarely
contact me ...
I would like to avoid to have to drive there so it would be great to be
able to
On 2014-01-08, Stefan G. Weichinger li...@xunil.at wrote:
Looking forward to some clever suggestions ;-)
Well, I'd start by running memtest86 overnight just to eliminate the
possibility of marginal memory. But, if memory serves, this is a
remote server at a customer site -- so that may not be
Am 08.01.2014 19:47, schrieb Grant Edwards:
On 2014-01-08, Stefan G. Weichinger li...@xunil.at wrote:
Looking forward to some clever suggestions ;-)
Well, I'd start by running memtest86 overnight just to eliminate the
possibility of marginal memory. But, if memory serves, this is a
12 matches
Mail list logo
