Data Storage Interrupt - software?

[Daniel Packman]

On a venerable 595 RS6000 I repeatadly get a
DSI_PROC, Data Storage Interrupt on the system when
running a big rsync job. The error message in the
log indicates that the probable cause is a software
program. Is this really true and the hardware is still ok?

--
Daniel Packman
NCAR/ACD
pa...@ucar.edu

[mark taylor]

hello,

paste the following sub commands from crash into the thread...

stat
status
t -mk
cpu
od prog_log 8 a
od vmmerrlog 9 a
od thewall 1 dec
od allocated 1 dec
od vmker 16

also, what machine type? lslpp -l bos.mp? instfix -ik | grep ML ?

Rgds
Mark

[mark taylor]

if its v4 that is...

post the following from kdb on v5

run the following commands
set 10
set 18
stat
status
dw prog_log 8 a
dw vmker 16 a
dw vmmerrlog 9 a

rgds
Mark

[Nicholas Dronen]

mark taylor <m...@talk21.com> wrote:
> if its v4 that is...

> post the following from kdb on v5

> dw prog_log 8 a
> dw vmker 16 a

I know what sort of information vmmerrlog provides.
What about prog_log and vmker?

Regards,

Nicholas

--
Do not reply to USENET posts, at least to mine, by email.

[Surinder Kumar]

prog_log :- It is used to find out if the dump was due to a hardware
problem.

vmker :- For finnding out free paging space. Now a days this command is not
used as with time
the offset of free_paging_space/total_paging_space has changed.
The command od
vmker 16 used to be used to look at total paging space and free paging
space but
the field values have changed. It is easier to use the vmm
command to look at the vmker
data. The numpsblks field is the number of total paging space
blocks.
The psfreeblks is the free paging space blocks.

[mark taylor]

It is easier to use the vmm > command to look at the vmker
> data.

crash > vmm > d

or

crash > od vmker 16

easier?? preferential surely!

[mark taylor]

> vmker :- For finnding out free paging space. Now a days this command is not
> used as with time the offset of free_paging_space/total_paging_space has changed.

vmker command is still used in kdb
echo vmker | kdb dump unix

> The command od vmker 16 used to be used to look at total paging space and free > > paging > space but the field values have changed. It is easier to use the vmm
> command to look at the vmker data. The numpsblks field is the number of total > > paging space blocks. The psfreeblks is the free paging space blocks.

vmm in kdb on v5? vmm is only on v4 in crash where "od vmker 16" gives
the
correct offsets. agreed the offsets have changed from v4 to v5 and the
"dw vmker 16" was a typo. it should have read "dw vmker 20"

appologies :) ...

[Surinder Kumar]

Aix team is coming up with some good features in kdb. We don't need to
remember which field contains
what. We no longer need to dump values. They have given commands for most
widely accessed data
structures e.g.

crash to kdb
replaced (vmm->vmker) with vmker
replaced vmmerrlog with vmlog

[Surinder Kumar]

forgot to add this..

(0)> vmker

VMM Kernel Data:

vmm srval (vmmsrval) : 20000801
pgsp map srval (dmapsrval) : 20001803
ram disk srval (ramdsrval) : 00000000
kernel ext srval (kexsrval) : 00000000
iplcb vsid (iplcbvmh) : 0000736F
offset of iplcb (iplcboff) : 00000000
hashbits (hashbits) : 00000010
hash shift amount (stoibits) : 0000000B
rsvd pgsp blks (psrsvdblks) : 00000200
total page frames (nrpages) : 00020000
bad page frames (badpages) : 0000000B
total pgsp blks (numpsblks) : 00020000
free pgsp blks (psfreeblks) : 0001FC0A

(0)> vmlog
Most recent VMM errorlog entry
Error id =
Exception DSISR/ISISR = 0000000000000000
Exception srval = 0000000000000000
Exception virt addr = 0000000000000000
Exception value = 00000000