UUvF+Ii/P6zqJmew";   
   er.org";	posting-account="U2FsdGVkX19A79bB6f0/RpZ/wI6uM4yW"   
   Gecko/20111103 Thunderbird/3.1.16   
   .os2.setup.misc:648   
   From: Peter Flass    
      
   On 11/27/2011 2:17 PM, Peter Brown wrote:   
   >   
   >   
   > Dariusz Piatkowski wrote:   
   >> Hi Peter!   
   >>   
   >> On Thu, 24 Nov 2011 15:36:39 UTC, Peter   
   >> Brown   
   >> wrote:   
   >>   
   >>> Hi Dariusz   
   >>>   
   >>> Dariusz Piatkowski wrote:   
   >>>> Hi Folks!   
   >>>>   
   >>>> Ever since my upgrade to the '21st century computing' (lol - a move   
   >>>> from an AMD   
   >>>> Barton to Phenom X4 setup) I have been experiencing an odd freeze   
   >>>> here and   
   >>>> there. These are not hard locks, rather the WPS stops responding,   
   >>>> mouse cursor   
   >>>> is still OK, CPU monitor (v 1.17) chugs along, but the WPS interface   
   >>>> seems to   
   >>>> stop working. This is always brought on by something a given   
   >>>> application has   
   >>>> attempted to do, once such app is AVXCAT, which I would love to use.   
   >>>> The 2nd on   
   >>>> is the latest PMView install program (WPI based). Both will   
   >>>> soft-lock the WPS,   
   >>>> only CAD helps.   
   >>>>   
   >>>> One thing I have been able to narrow this down to is the utilization   
   >>>> of the 4   
   >>>> cores...if I shut-off the 3 remaining cores (using setproc utility)   
   >>>> I am able to   
   >>>> breeze through these processes.   
   >>>>   
   >>>> So...what's the config I'm using? Warp4.52, CP2 with FP6 applied,   
   >>>> using the SMP   
   >>>> doscall, os2krnl, etc, PSD=OS2APIC.PSD /P=4 /APIC, although I have   
   >>>> tried a bunch   
   >>>> of different /PIC and /PREC options, none of which had made a   
   >>>> difference.   
   >>>   
   >>> Maybe os2apic.psd is not that capable with modern hardware.   
   >>>   
   >>> You may need to purchase eCS to get current apic support - when eCS   
   >>> finally get a good working version of their acpi.psd released.   
   >>>   
   >>> You could try using markexe.exe (from the os/2 toolkit) or execmode.exe   
   >>> (should be in bootdrive:\os2) to mark apps that do not work with> 1 cpu   
   >>> and, hopefully, overcome problems.   
   >>   
   >> Yes, I suspect OS2APIC has some limitations as well. My MSI BIOS   
   >> supports MPS   
   >> table configuration in 1.1 or 1.4 version...I'm currently trying both   
   >> combinations...so far not much luck though.   
   >>   
   >> eCS? Yes....but only if the general concensus out there in the OS2   
   >> community is   
   >> that the ACPI is stable enough...so far I haven't seen that, but I'm   
   >> certainly   
   >> open to this possibility.   
   >>   
   >> I have both of the EXE marking utilities here...tried them both, the   
   >> known   
   >> applications are still locking the system...so I'm guessing the   
   >> problem lies   
   >> somewhere underneath the covers...meaning, setting a single CPU   
   >> execution mode   
   >> only and shutting off the remaining CPUs do not seen to have the same   
   >> result.   
   >>   
   >> Thanks!   
   >   
   >   
   >   
   > I wonder if the updated doscall1.dll file would help - yet another eCS   
   > "goodie" that is not yet publicly available.   
   >   
   > As I understand it it cures problems with SMP "spinlocks" - and, no, I   
   > have no idea what that means. I do know that I have been experiencing   
   > less system hangs at boot when the Desktop should be starting since   
   > installing this new doscall1.dll file though.   
   >   
      
   Intel does a rather poor job maintaining cache consistency among    
   multicore systems: different CPUs can have different versions of the    
   same data.  This might mean, for example, that one CPU can free a lock    
   on some resource while the other CPU thinks it's still locked and waits    
   forever.   
      
   --- Internet Rex 2.31   
    * Origin: A noiseless patient Spider (1:261/20.999)