said:
>1. Removed the external SCSI cable running to my scanners & rebooted. It
>worked! ONCE! dumped again the next time. :-(
Humm. I'm not sure what this is telling us.
>2. Removed & reseated all cards. It worked! Now, however, I get a SYS1474
>during boot. Help for this says:
>SYS1474: The system does not have enough storage to activate swapping.
Odd.
>There's a red herring here somewhere...
>I have 1 GiB RAM. BIOS shows 1024 MiB. SysInfo same. eCenter showed ~175
>MiB.
175MB is rather low for a system with 1GB physical. I would expect well
over 700MB free at startup. It might be time to run a memory checker and
Dani's patchldr test.
>CONFIG.SYS shows: SWAPPATH=D:\OS2\SYSTEM 2048 2048
>D: has 1.3 GiB free
>Rebooted. Back to normal. Hello!?!?!?!?
So it is really fixed?
>Reading y:\dumpdata.001 05-13-04 23:11:36
>##0168:fff0f69b - 000f:e69b , 06860680
>9084
>Exception in module: OS2KRNL
>TRAP 000e ERRCD=0002 ERACC=**** ERLIM=******** CPU=01
>EAX=00000000 EBX=00001000 ECX=00000400 EDX=fe6f1238 ESI=00000008
>EDI=11ccfff0 EBP=00004f12 FLG=00250216
>CS:EIP=0168:fffbd614 CSACC=c09b CSLIM=ffffffff
>SS:ESP=1530:00004ede SSACC=1097 SSLIM=00003fff
>DS=0160 DSACC=c0f3 DSLIM=ffffffff CR0=8001003b
>ES=0160 ESACC=c0f3 ESLIM=ffffffff CR2=11ccfff0
>FS=0000 FSACC=**** FSLIM=********
>GS=0000 GSACC=**** GSLIM=********
>Internal revision 14.097f_SMP
>PMDF (for the latest dump) shows:
># ln 0168:fffbd614
>%fffbd52c OS2KRNL _SMReinit + e8
>#
>Is this where SMP gets turned on?
SM could be SMP and it could be Session Manager. I recommend posting the
dump screen and a synopsis of your hardware to comp.os.os2.bug. Scott
will know and may provide some useful comments.
>I looked in the BIOS, but can't find
>any place to disable one of the CPUs. Tyan/Phoenix don't give me very
>many choices... I REALLY don't want to physically remove a CPU. It's a
I don't blame you. It's messy with all the grease and heat sinks. What
you may be able to do is is swap in a W4 or UNI kernel and not load the
PSD.
># Checking call gates for all slots
Typically the only one that matters is the failing thread.
>Slot *sysinit 8:
>is in a 32 bit call gate: 0148:00004ce0 OS2KRNL DOSSICG
>Slot *jitdaemon 9:
>is in a 32 bit call gate: 0148:00004d28 OS2KRNL DOSSYSTEMSERVICE Called
>by: %1ffc95c8 DOSCALL1 _JITDispatcherThread + 233
>Invalid linear address: 003f:00000d24
Is one of these the failing thread?
>In light of the above wierdness, there is probably not much point in
>sending you the dump which is not the original one anyway.
Hold off for now on sending dumps for now. We are still have somewhat of
a moving target. If you have enough free space, you might want to archive
a couple of generations of dump files in case we want to do some
comparisons. zip them up and they will not take all that much space.
HTH,
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
>> Next Message >>
Return to [ 15 |
May |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.