Hi Craig !

In case nobody replied before me .... you need to issue at least
io_ios_diag_log, and possibly other commands/macros. Then you'll need to
format the config to retrieve the hardware path.

Christian

> -----Message d'origine-----
> De : HP-3000 Systems Discussion [mailto:[log in to unmask]]De la
> part de Craig Lalley
> Envoye : lundi 19 janvier 2004 18:09
> A : [log in to unmask]
> Objet : Re: [HP3000-L] Memory Dump
>
>
> Jon,
>
> I am a consultant.
>
> I should learn to be very specific in my questions.
>
> I have a memory dump,
>
> I would like to figure out which SCSI card is the culprit?
>
> How do I determine the SCSI path generating the errors?
>
> Specifically, which Debug commands will point to the path?
>
> I would like to look at the device logs, but this password
> CRAP has go to stop!
> This is the second time this week that I needed the password.
>  HP are you
> listening!  If HP is going to abandon the customers that
> choose to homestead,
> this is the biggest sign!
>
> Regards,
>
> -Craig
> EchoTech, Inc
> 541-619-1678
>
>
>
>
>
>
> --- JON OSE <[log in to unmask]> wrote:
> > Craig Lalley <[log in to unmask]> wrote:
> > >Can I figure anything else out?
> >
> > Not with what you sent. You could look at the system log
> files, and also look
> > at
> > the device logs from each device on the chain. This
> requires HP maintenance
> > passwords :(
> >
> > If this repeats, I would first isolate the chain to discs
> only, as other
> > devices, tapes and cds can hang the chain.
> >
> > Is this your system or are you a consultant? Where do I
> send the bill:)
> >
> > Jon
> >
> >
> >
> > Can I figure anything else out?
> >
> > It appears that a SCSI cable may have been loose? But that is only
> > speculation.
> >
> > Any other comments/suggestions?
> >
> > TIA,
> >
> > -Craig
> >
> > *********************************************************
> >
> > ERROR STACK FOR PIN: $252
> >
> > Entries displayed in most recent to least recent order:
> >
> > SUBSYSTEM SUBSYSTEM SUBSYSTEM
> > NUMBER ERROR NUMBER NAME
> > --------- ------------ ---------
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> > #122 #180 Port (IPC) Facility
> > An attempt to receive a message from a port; there were no
> messages on any
> > ena
> > bled subqueues, and the process did not wish to wait for a
> message to
> > arrive.
> >
> >
> >
> > STACK MARKER TRACE:
> >
> > PC=a.00873b64 wiz_tlih+$188
> > NM* 0) SP=82c43868 RP=a.001a4d48 io_do_slih+$c8
> > NM 1) SP=82c437a8 RP=a.00866d9c wiz_send_to_tlih+$a8
> > NM 2) SP=82c43728 RP=a.0086b330 wiz_io_req+$50
> > NM 3) SP=82c436a8 RP=a.00874680 fwscsi_dam+$5d4
> > NM 4) SP=82c43668 RP=a.00874098 ?fwscsi_dam+$8
> > export stub: a.00170f28 execute_server_0+$74
> > NM 5) SP=82c435a8 RP=a.009d8090 sda_send_scsi_request+$360
> > NM 6) SP=82c434d0 RP=a.0171bb4c sda_issue_next_io+$e8
> > NM 7) SP=82c433d0 RP=a.0171c200 scsi_disk_and_array_dm+$518
> > NM 8) SP=82c43350 RP=a.009e339c ?scsi_disk_and_array_dm+$8
> > export stub: a.001b1144 schedule_server.do_server+$114
> > NM 9) SP=82c43250 RP=a.001b1428 schedule_server+$dc
> > NM a) SP=82c43190 RP=a.001b05a4 schedule_deferred_ports+$100
> > NM b) SP=82c430d0 RP=a.00166800 iexit
> > --- Interrupt Marker
> > NM 1) SP=82c43050 RP=a.0016799c enable_int+$2c
> > --- End Interrupt Marker Frame ---
> >
> > PC=a.0016799c enable_int+$2c
> > NM 0) SP=4188d808 RP=a.001b06f4 queue_ics_port+$c8
> > NM 1) SP=4188d808 RP=a.001715c4 send_to_ics_server+$20
> > NM 2) SP=4188d7c8 RP=a.00732170 sendmmio+$218
> > NM 3) SP=4188d6f0 RP=a.00835a54 send_io+$3c0
> > NM 4) SP=4188d530 RP=a.01732480
> process_imi_mib.send_mib_if_ready+$ac
> > NM 5) SP=4188d3f0 RP=a.01732a50 process_imi_mib+$2f0
> > NM 6) SP=4188d370 RP=a.0083758c check_and_queue_imi_mib+$90
> > NM 7) SP=4188d270 RP=a.00837b1c fetch__pages+$328
> > NM 8) SP=4188d1f0 RP=a.01738b00 prefetch_+$514
> > NM 9) SP=4188d0f0 RP=a.0084f518 ?prefetch_+$8
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> > http://hotjobs.sweepstakes.yahoo.com/signingbonus
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *