Update
The problem turned out to be the BIOS of the PC we were using. The
Python test program has been running fine for 5 days now (after we
upgraded the system BIOS) and is still running fine.
Sorry, I do not have any information as to what was fixed in the BIOS.
Also, I do not know exactly who
On 2006-05-10, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Grant
>
>> You might want to run some memory tests.
>
> We have multiple identical boxes and they all have the same problem.
Maybe whoever built them got a bad batch of RAM. Or maybe the
just used RAM with the wrong specs. It doesn't
On May 10, 2006, at 5:39 PM, [EMAIL PROTECTED] wrote:
> Grant
>
>> You might want to run some memory tests.
>
> We have multiple identical boxes and they all have the same problem.
>
> Olaf
They might all have flaky memory - I would follow the other poster's
advice and run memtest86 on them.
Grant
> You might want to run some memory tests.
We have multiple identical boxes and they all have the same problem.
Olaf
--
http://mail.python.org/mailman/listinfo/python-list
On 2006-05-10, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> So to make sure that no other software is involved we took the
> PC with the problem, reset the BIOS to its defaults (which
> also enables hyper-threading) and installed Windows XP
> Professional (SP2) on it (but no further driver softw
This is an update on what we found so far:
We located one other PC that was not identical to the PC with the
problem. So we installed Windows XP on it and ran the Python test
program. It ran fine all night w/o locking up.
Here is what winmsd reports for this PC:
winmsd:
OS Name: Microsoft Windo
I haven't try the files yet. But have got a similar problem before. The
situation is nearly the same.
Always at random time , it reported that the memory read or write
violently.But I use Windows 2000(Python 2.3, wxPython 2.4). Windows
issue says 2000 doesn't support HP, so I simply turn it off. I
[EMAIL PROTECTED] wrote:
> Thanks for trying and reporting the results. Both of you and Tim and
> Dave have run the .py program now (all on hyper-threaded CPUs) and
> none of you were able to reproduce the problem.
>
> So that indicates that there is something special about our PC. We
> are pla
No lockup for me after 28 hours.
Of course, I don't have HT. It's a dual Opteron system with WinXP.
--
http://mail.python.org/mailman/listinfo/python-list
Robin and Roel
Thanks for trying and reporting the results. Both of you and Tim and
Dave have run the .py program now (all on hyper-threaded CPUs) and none
of you were able to reproduce the problem.
So that indicates that there is something special about our PC. We are
planing to re-install Win
Dave send me the below as an email. Olaf
Hi Olaf,
I'm running your test for you - it's been going for about an hour now
and is continuing to generate output[1].
c:\>py
Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)]
on win32
Type "help", "copyright", "credits" or "license"
[EMAIL PROTECTED] schreef:
> Below are 2 files. The first is a Python program that isolates the
> problem within less than 1 hour (often just a few minutes). The second
> is a C++ program that shows that the Win32 Sleep() function works as
> expected (ran from Friday afternoon until Monday mornin
[EMAIL PROTECTED] wrote:
> Below are 2 files. The first is a Python program that isolates the
> problem within less than 1 hour (often just a few minutes). The second
> is a C++ program that shows that the Win32 Sleep() function works as
> expected (ran from Friday afternoon until Monday morning)
[EMAIL PROTECTED] wrote:
> Tried importing win32api instead of time and using the
> win32api.GetTickCount() and win32api.Sleep() methods.
What about win32api.SleepEx? What about
WaitForMultipleObjects
WaitForMultipleObjectsEx
WaitForSingleObject
WaitForSingleObjectEx
when the object is not expe
Tim
Many thanks for trying and reporting the details of your environment.
All our hyper-threading PC are identical. However, we identified one
that is different and we are installing Windows XP on it now ...
My hope is that other people will try this, too.
Olaf
--
http://mail.python.org/mailm
[EMAIL PROTECTED]
> Below are 2 files. The first is a Python program that isolates the
> problem within less than 1 hour (often just a few minutes).
It does not on my box. I ran that program, from a DOS shell, using
the released Windows Python 2.4.3. After an hour, it was still
printing. I lef
16 matches
Mail list logo
