ID:               39221
 Comment by:       paradiso at gmail dot com
 Reported By:      kris at k-software dot org
 Status:           No Feedback
 Bug Type:         Apache2 related
 Operating System: windows server 2003 x64
 PHP Version:      5CVS-2006-10-20 (snap)
 New Comment:

This is really a bug.
on my p4 2.4c + 865G + 1G ram, win2k3 server, apache 2.2.3.0 & php 5.2,
this happens all the time.


Previous Comments:
------------------------------------------------------------------------

[2006-10-31 01:00:01] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

------------------------------------------------------------------------

[2006-10-22 14:14:23] kris at k-software dot org

Error in CPU IDs in previous comment, from microsoft support article ID
252867:

Processor enumeration on computers that use hyperthreading first assign
processor numbers to the primary logical processor for each processor
and then assign numbers to the secondary. For example, for dual
physical processor computers with hyperthreading, the first processor
has logical processor 0 and 2, and the second processor has logical
processor 1 and 3.

------------------------------------------------------------------------

[2006-10-22 13:59:13] kris at k-software dot org

It appears that setting the CPU affinity of the apache http process to
a single physical processor stops the crashing...

Setting the server to NOT use the second hyperthreaded core of the
xeons (i.e. CPUs 0+2 or 1+3) seems to solve this random crashing.

Will test with a prefork MPM.

------------------------------------------------------------------------

[2006-10-22 12:49:58] kris at k-software dot org

I'm currently unable to track down a single script/function which
causes this error, and am therefore unable to provide a code sample. 

I realise that the bug report is pretty useless without reproducable
code, so I'm still investigating and trying to track down the exact
cause of the crashes.

------------------------------------------------------------------------

[2006-10-21 20:38:21] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.



------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/39221

-- 
Edit this bug report at http://bugs.php.net/?id=39221&edit=1

Reply via email to