Re: DSI_PROC error

From: Green, Simon (Simon.Green_at_EU.ALTRIA.COM)
Date: 10/06/05

  • Next message: Vincent D'Antonio: "Device/command block size" 
    Date:         Thu, 6 Oct 2005 11:24:47 +0200
To: aix-l@Princeton.EDU

    I'd also add that if you *don't* have at least a partial dump don't waste
    your time trying to find the cause. Anything less than a complete dump
    probably won't be any use, but you might get lucky.

    I haven't had to deal with a lot of DSIs, but in most cases there was
    already a PTF for the problem. They're hard to find, though, without the
    dump information.

    Dump analysis doesn't use crash anymore, it uses kdb. I'm not an expert by
    a long way, but a bit of poking around is usually sufficient to find what
    was running at the time of the crash, and maybe some useful search terms for
    the APAR database. 

    -- 
Simon Green							
Altria ITSC Europe s.a.r.l.
AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Bob
Booth - UIUC
Sent: 05 October 2005 18:41
To: aix-l@Princeton.EDU
Subject: Re: DSI_PROC error
On Wed, Oct 05, 2005 at 12:27:21PM -0400, Drew T wrote:
> Hello,
> 
> I searched the archives for DSI  errors and read there that DSI's are rare
> and normally few and far between. (Of course that's not a good answer when
> management asks why it happened).
> 
> I wanted to post this here because I just got one and we are still running
> forensics on the machine. The resources failed over but that still didn't
> prevent me from being woken up very early in the morning.
> 
> Can anyone lend any advice while I'm performing forensics? I just don't
> want to overlook anything.
Do you have any mis-behaving devices?  DSI's are usually caused by device
drivers, very rarely hardware (such as cache boards).  If you hopefully have
a good crash dump, take a look at it with the crash command.  You may find
the offending 'program'.
hth,
bob
  • Next message: Vincent D'Antonio: "Device/command block size"

    Relevant Pages

    • Re: SetUnhandledExceptionFilter
      ... The only way to prevent at all cost a crash in the applicaiton ... Looking at a full dump of Word.exe and/or LotusNotes is the only way ... A bad heap metadata will cause an access violation, ... normally dismissed in some wide exception handler) ...
      (microsoft.public.win32.programmer.kernel)
    • RE: Cluster hang -- Getting Crash Dump
      ... write a dump. ... At the console command prompt enter: crash ... > Quorum Hang,, ...
      (comp.os.vms)
    • RE: VS .Net 2003 IDE Crashes when Attaching to Debugger
      ... had to run the application much longer when attempting to get the dump than ... The crash occurs when selecting the ... Macaffee can cause some prolems with the IDE since it does ... >>application we're debugging is an inprocess DLL with Visio. ...
      (microsoft.public.vsnet.general)
    • Re: SYSDUMP.DMP corruption
      ... >..analyzing a compressed selective memory dump... ... but not fatal to crash analysis. ... This could be an invalid dump file, or a may be due to a mis-matched SDA image. ... images, but often slows performance too much ...
      (comp.os.vms)
    • Re: Online Crash Analysis for Dump from Other Computer
      ... Why can't the crashing system send the dump itself? ... interested in is knowing what the reason is for the crash you can send it to ... How can I submit a dump file to crash analysis from a different ...
      (microsoft.public.windowsxp.general)