In , on 10/17/07
   at 07:37 PM, Jim Byrnes  said:

Hi,

>This led me to believe that I had scsi hardware problems.  Since the 
>scsi was on-board I began looking for a scsi card to put in the 
>machine.Today I disabled the on board scsi and installed a Adaptec 
>29160.  (the on-board scsi was also adapted).  I was up and running for 
>about 10 minutes when I got the following trap:

>Exception in module: AICU160
>TRAP 000d ERRCD=0000 ERACC=**** ERLIM=******** CPU=1
>EAX=00000040 EBX=ffeb0ce9 ECX=80010000 EDX=00000000
>ESI=ff800000 EDI=fd400ce9 EBP=f8f8ff72 FLG=00010013
>CS:EIP=0710:0000a000 CSACC=009b CSLIM=0000ea37
>SS:ESP=15e8:000ff64 SSACC=0097 SSLIM=0000dfff
>DS=0700 DSACC=0093 DSLIM=0000b628 CR0=8001003b
>ES=0000 ESACC=**** ESLIM=******** CR2=1c1547b0
>FS=0000 FSACC=**** FSLIM=********
>GS=0000 GSACC=**** GSLIM=********

It's hard to say much other than that since ss is 15e8, the trap occurred
within the interrupt handler.  Perhaps a trap dump would provide more
clues.

What version of the driver are you running?  I suspect it's 10.03 or
something very close The CSLIM value matches what I expect to see and the
DSLIM is very close.

FWIW, it's not terribly useful to post trap screens without including the
kernel and driver versions.

I run the 10.03 driver here and the code at the trap location is

06a8:0000a000 26c41c         les       bx,dword ptr es:[si] 

If this matches your code, the trap occurred because the code wandered
past the end of some table (es is 0).

IAC, I recommend you figure out what you changed that caused the traps to
start to occur.

FWIW, trap Ds are generally software,  Trap Es can be hardware related,
but when they occur in drivers it's software more often than not.

>Anyone have any ideas what is happening?  Could the AICU160.ADD be 
>corrupted and replacing it with a fresh copy be in order?

I hear this a lot and it never makes sense to me.  A corrupted executable
is probably the least likely reason for any system error.  First of all,
unlike data files, nothing is supposed to writes to them.  If the system
was behaving badly enough to corrupt an excutable, you would have gobs of
corrupted data long ago.

Perhaps it has to do with Windows thinking.  Even so, it's not the windows
executables that get corrupted, it's the registry data that points to
them.  Reinstalling the app is just a simple way of getting the registry
fixed.

Steven

-- 
----------------------------------------------------------------------
"Steven Levine"   MR2/ICE 3.00 beta
09pre #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
----------------------------------------------------------------------



 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 Your email settings:
    Individual Email | Traditional

 To change settings online go to:
    http://groups.yahoo.com/group/os2hardware/join
    (Yahoo! ID required)

 To change settings via email:
    mailto:os2hardware-digest{at}yahoogroups.com 
    mailto:os2hardware-fullfeatured{at}yahoogroups.com

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

---