It is currently Wed, 22 Mar 2023 06:40:25 GMT

Author Message
 scat: assertion failure

I had a system crash on one machine and would like to analyze the crash
dump. So I installed SUNWscat4.1_Lite. But it crashes immediately:

# ./scat /var/crash/anduril/unix.0 /var/crash/anduril/vmcore.0

  Solaris[TM] CAT 4.1 (build 526) for Solaris 10 64-bit SPARC(sun4u)

  Copyright ? 2003 Sun Microsystems, Inc. All rights reserved.

  Sun Microsystems, Inc. has intellectual property rights relating
  to technology embodied in the product that is described in this
  document. In particular, and without limitation, these intellectual
  property rights may include one or more of the U.S. patents listed
  at http://www.**-**.com/
  pending patent applications in the U.S. and in other countries.

  U.S. Government Rights - Commercial software. Government users are
  subject to the Sun Microsystems, Inc. standard license agreement
  and applicable provisions of the FAR and its supplements.

  Use is subject to license terms.

  This distribution may include materials developed by third parties.

  Portions may be derived from Berkeley BSD systems, licensed from
  U. of CA. Sun, Sun Microsystems, the Sun logo, SunSolve, Java and
  Solaris are trademarks or registered trademarks of Sun Microsystems,
  Inc. in the U.S. and other countries. All SPARC trademarks are used
  under license and are trademarks or registered trademarks of SPARC
  International, Inc. in the U.S. and other countries.
  Sun Microsystems proprietary - DO NOT RE-DISTRIBUTE!

  Feedback regarding the tool should be sent to SolarisCAT_Feedb...@Sun.COM

opening /var/crash/anduril/vmcore.0 ...dumphdr...symtab...Assertion
failed: RW_LOCK_HELD(&(scn->s_elf->ed_rwlock)), file
../common/getdata.c, line 99
Abbruch (core dumped)

Has anybody seen this? Is there a workaround?

BTW: the crash looks like this:
debugging crash dump /var/crash/anduril/vmcore.0 (64-bit) from anduril
operating system: 5.10 Generic_118822-26 (sun4u)
panic message: BAD TRAP: type=30 rp=2a100a993d0 addr=0 mmu_fsr=58043d
dump content: kernel pages only
             cpu                1
          thread      30005e10fa0
         message BAD TRAP: type=30 rp=2a100a993d0 addr=0 mmu_fsr=58043d
          tstate          4001407
              g1          1811c00
              g2                0
              g3               60
              g4      2cdbec05d4a
              g5            2625a
              g6                0
              g7      30005e10fa0
              o0         fcf3e000
              o1              ce3
              o2                0
              o3          1800000
              o4                0
              o5               16
              o6      2a100a98c71
              o7          1031688
              pc          11e58c4
             npc          11e58c8
               y                0
            sfsr           58043d
            sfar                0
              tt               30
%g0 = 0x0000000000000000                 %l0 = 0x0000000000000020
%g1 = 0x0000000001811c00    knl_unload+8 %l1 = 0x0000000000002000
%g2 = 0x0000000000000000                 %l2 = 0x0000030003ac34b0
%g3 = 0x0000000000000060                 %l3 = 0x0000030000d70000
%g4 = 0x000002cdbec05d4a                 %l4 = 0x000000000184739c
%g5 = 0x000000000002625a                 %l5 = 0x0000000000000001
%g6 = 0x0000000000000000                 %l6 = 0x0000000000000000
%g7 = 0x0000030005e10fa0                 %l7 = 0x000000000003ffff

%o0 = 0x00000000fcf3e000                 %i0 = 0x000002a100a99850
%o1 = 0x0000000000000ce3                 %i1 = 0x0000000000000ce3
%o2 = 0x0000000000000000                 %i2 = 0x0000000000000003
%o3 = 0x0000000001800000         t0stack %i3 = 0x00000000fcf3e000
%o4 = 0x0000000000000000                 %i4 = 0x0000000000000000
%o5 = 0x0000000000000016                 %i5 = 0x0000000000000032
%o6 = 0x000002a100a98c71                 %i6 = 0x000002a100a98d21
%o7 = 0x0000000001031688 sfmmu_tlb_range_demap+0x1b0 %i7 =

 %ccr = 0x00 xcc=nzvc icc=nzvc
%fprs = 0x00 fef=0 du=0 dl=0
 %asi = 0x04
   %y = 0x0000000000000000
  %pc = 0x00000000011e58c4 vtag_flushpage+0x44
 %npc = 0x00000000011e58c8 vtag_flushpage+0x48
  %sp = 0x000002a100a98c71 unbiased=0x000002a100a99470
  %fp = 0x000002a100a98d21

  %tick = 0x0000000000000000
   %tba = 0x0000000000000000
    %tt = 0x30
    %tl = 0x0
   %pil = 0x0
%pstate = 0x014 cle=0 tle=0 mm=TSO red=0 pef=1 am=0 priv=1 ie=0 ag=0

       %cwp = 0x07  %cansave = 0x00
%canrestore = 0x00 %otherwin = 0x00
    %wstate = 0x00 %cleanwin = 0x00
vtag_flushpage+0x44(2a100a99850, ce3, 3, fcf3e000, 0, 32)
hat_unload_callback+0x7f0(1, fcf64000, 0, 0, 0, 30003ac34b0)
segvn_unmap+0x1b8(300068973f8, fce00000, 164000, ffffffffffffffff,
as_unmap+0xe4(30003a7eb08, 300068973f8, 300057f4cf0, 164000, 1, 1)
munmap+0x78(1fff, 1632b8, 1072800, 30005260020, 30005260020, fce00000)
syscall_trap32+0xcc(fce00000, 1632b8, 10, 411614, 1, 0)


 Fri, 18 Jul 2008 20:29:22 GMT   
 scat: assertion failure
Solaris CAT 4.1 was released well before Solaris 10. As such it can't be
used to look at Solaris 10 crashdumps.

You'll need 4.2, which is currently going through the release processes
and hopefully shouldn't be too long (but I wouldn't hold my breath).

Alan Hargreaves -
Staff Engineer (Kernel/VOSJEC/Performance)
Product Technical Support (APAC)
Sun Microsystems

 Sun, 27 Jul 2008 16:18:17 GMT   
   [ 2 post ] 

Similar Threads

1. Strange failure (internal assertion failure?)

2. Assertion failure on solaris 2.8 causes system to crash

3. usb assertion failure

4. Assertion Failure in Compilat

5. xemacs dies with an assertion failure error message

6. Assertion failure in 2.5.69-mm9

7. Assertion failure in journal_dirty_metadata()

8. Kernel Bug Assertion Failure

9. Kernel assertion failures

10. KERNEL BUG: assertion failure in reiserfs code

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software