My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary.
Thanks you.
Can I have any information about this ACT and SCAT output. It would be greatly appreciated.
Code:
SCAT -
core file: vmcore.0
user: Super-User (root:0)
release: 5.8 (64-bit)
version: Generic_117350-44
machine: sun4u
node name: hccssun5
hw_provider: Sun_Microsystems
system type: SUNW,Sun-Fire-V440 (UltraSPARC-IIIi)
hostid: 83ac50db
dump_conflags: 0x10000 (DUMP_KERNEL) on /dev/md/dsk/d10(3.90G)
time of crash: Mon Feb 8 14:42:08 EST 2010
age of system: 101 days 22 hours 58 minutes 44.84 seconds
panic CPU: 1 (4 CPUs, 16G memory)
panic string: recursive mutex_enter, lp=78027ff0 owner=2a1004d7d20 thread=2a10 04d7d20
ACT
###
CPU 0x1 is RUNNING READY CONFIGURED ENABLED ### CPU=1 (1) ###
###
PANIC occurred on this CPU
cpu addr 0x30004c7ca98
running thread addr 0x2a1004d7d20
pause thread addr 0x2a100003d20
dispatched thread addr 0x2a100007d20
interrupt stack is 0x2a1004d1f50
interrupt thread list starts at 0x2a1004ddd20
struct cpu 2280 is not the expected size 2248
PANIC occurred on this thread
***
Kernel thread:
thread addr 0x2a1004d7d20, proc addr 0x104245b0, lwp addr 0x0
Thread 0x2a100007d20 is pinned by this thread
Thread bound to cpu id 0x1
t_state is 0x4 - TS_ONPROC
Scheduling info:
t_pri is 0xa5, t_epri is 0x0, t_cid is 0x0
scheduling class is: SYS
t_disp_time: is 0x348129bf, 0t880880063
last switched: 6 mins 8 secs ago on cpu 0x1
pc is 0x10048b94, sp is 0x10424010, t_stk 0x2a1004d7b10
Stack trace is:
unix: setjmp ()
unix: panicsys+0x44 (0x10057730,0x2a1004d7468,0x10000,0x10001,0x80000000,0x5508)
unix: vpanic (0x10057730,0x2a1004d7468)
unix: panic+0x1c (0x10057730,0x10415fe8,0x78027ff0,0x2a1004d7d20,0x2a1004d7d20)
unix: mutex_panic+0x5c (0x10415fe8,0x78027ff0)
unix: mutex_vector_enter+0x250 (0x78027ff0,?,?,0x0)
unix: mutex_enter (0x78027ff0)
skip_es: skip_es_rcv+0x22c (0x300056edca0,0x300056e8300)
skip_es: skip_esr+0x84 (0x300056edca0,0x300056e8300)
unix: putnext+0x218 (0x300056ece60,0x300056e8300)
qfe: qferead_dvma+0x344 (0x30005768000,0x300055aabf8)
qfe: qfe_intr+0x154 (*0x30000158628)
pcisch: pci_intr_wrapper+0x80 (0x30005725db0)
unix: intr_thread+0xa4 ()
unix: splx ()
idlethread is 0x2a100007d20
Last edited by Scott; 02-09-2010 at 03:21 PM..
Reason: Code tags please...
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Hi,
I'm running Solaris 10 with a zone called "testzone"
If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash
However no crash file is created in testzone.
My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Hi gurus,
I will be glad if anyone can help me with this:
How do you copy a crash dump file to send to your support provider?
Thanks lots guys. (1 Reply)
Hello Guys,
I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to :
1) create a mount point?
2) add entry in /etc/vfstab?
3) is this slice wu or wm?
4) should... (3 Replies)
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
LEARN ABOUT MOJAVE
arch_prctl
ARCH_PRCTL(2) Linux Programmer's Manual ARCH_PRCTL(2)NAME
arch_prctl - set architecture-specific thread state
SYNOPSIS
#include <asm/prctl.h>
#include <sys/prctl.h>
int arch_prctl(int code, unsigned long addr);
int arch_prctl(int code, unsigned long *addr);
DESCRIPTION
arch_prctl() sets architecture-specific process or thread state. code selects a subfunction and passes argument addr to it; addr is inter-
preted as either an unsigned long for the "set" operations, or as an unsigned long *, for the "get" operations.
Subfunctions for x86-64 are:
ARCH_SET_FS
Set the 64-bit base for the FS register to addr.
ARCH_GET_FS
Return the 64-bit base value for the FS register of the current thread in the unsigned long pointed to by addr.
ARCH_SET_GS
Set the 64-bit base for the GS register to addr.
ARCH_GET_GS
Return the 64-bit base value for the GS register of the current thread in the unsigned long pointed to by addr.
RETURN VALUE
On success, arch_prctl() returns 0; on error, -1 is returned, and errno is set to indicate the error.
ERRORS
EFAULT addr points to an unmapped address or is outside the process address space.
EINVAL code is not a valid subcommand.
EPERM addr is outside the process address space.
CONFORMING TO
arch_prctl() is a Linux/x86-64 extension and should not be used in programs intended to be portable.
NOTES
arch_prctl() is supported only on Linux/x86-64 for 64-bit programs currently.
The 64-bit base changes when a new 32-bit segment selector is loaded.
ARCH_SET_GS is disabled in some kernels.
Context switches for 64-bit segment bases are rather expensive. As an optimization, if a 32-bit TLS base address is used, arch_prctl() may
use a real TLS entry as if set_thread_area(2) had been called, instead of manipulating the segment base register directly. Memory in the
first 2 GB of address space can be allocated by using mmap(2) with the MAP_32BIT flag.
Because of the aforementioned optimization, using arch_prctl() and set_thread_area(2) in the same thread is dangerous, as they may over-
write each other's TLS entries.
As of version 2.7, glibc provides no prototype for arch_prctl(). You have to declare it yourself for now. This may be fixed in future
glibc versions.
FS may be already used by the threading library. Programs that use ARCH_SET_FS directly are very likely to crash.
SEE ALSO mmap(2), modify_ldt(2), prctl(2), set_thread_area(2)
AMD X86-64 Programmer's manual
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 ARCH_PRCTL(2)