Hi Max,
just can get a crash dump of a hanging system by doing:
1. issue "mdb -K"
2. press F1-A on console
I tried it first via "mdb -K" (did not work... it just hang) and afterwards
with F1-A (worked fine).
But anyway: Any comments regarding the dump?
Thanks in advance
--
This message pos
Hi Ronny,
How are you getting the crash dump if your system is hung
and you are not getting into kmdb? To get into kmdb,
you need to type f1-a on the console (based on the addresses,
you are on x64, not SPARC).
max
Ronny Egner wrote:
HI all,
cpuinfo -v yields (see file "cpuinfo.txt" ).
I no
HI all,
cpuinfo -v yields (see file "cpuinfo.txt" ).
I noticed one interesting thing:
When preparing to catche the hang i opened the console and pre-typed "mdb -K"
to crash the system if needed to.
When the system hang i pressed but nothing happened. While digging
around in the core dump i fo
You might try ::cpuinfo -v
in mdb on the dump to see what was running on the cpus
at the time of the hang.
max
Brian Ruthven - Sun UK wrote:
Ronny Egner wrote:
ff008bfe0480 unix:die+dd ()
ff008bfe0590 unix:trap+177b ()
ff008bfe05a0 unix:cmntrap+e6 ()
ff008bfe0690 0 ()
ff0
Ronny Egner wrote:
ff008bfe0480 unix:die+dd ()
ff008bfe0590 unix:trap+177b ()
ff008bfe05a0 unix:cmntrap+e6 ()
ff008bfe0690 0 ()
ff008bfe06b0 unix:debug_enter+38 ()
ff008bfe06d0 unix:abort_sequence_enter+35 ()
ff008bfe0720 kbtrans:kbtrans_streams_key+102 ()
ff008b
Hi all,
i need your help debugging a hang issue on the latest build.
Occasionally the system hangs. Ping is still possible but it seems I/O to the
rpool disks is halted. The system consists of 42 disks. 40 of them are attached
via two LSI 1086E controller. The remaining two disks are attached vi
