Sponsored Content
Full Discussion: Panic on SCO6
Top Forums UNIX for Dummies Questions & Answers Panic on SCO6 Post 302914407 by Carlitos71 on Monday 25th of August 2014 04:41:52 PM
Old 08-25-2014
Panic on SCO6

Hi all,

I am running SCO6 in a VMWare environment. For the past two Sunday's during the system's automatic reboot I have received a Panic and the system has locked up. I have had to power off the VM and back on. I have never run into this sort of thing. Can someone help direct me to where the problem is? Thanks...

Code:
PANIC: address fault from interrupt routine; kernel address 0xF342EFFF
Kernel Page Fault from (cs:eip) = (100:C0203EA5):
 eax=F342EFFF ebx=F87A7F14 ecx=F3C2EEC0 edx=F87A7F10
 esi=F87A7F10 edi=F87A7F00 ebp=F95E1800 esp=FFFDAA50
Raw stack dump begins at 0xFFFDAA50:
A50 F924BE20 C01AD6D8 F95E1800 F87A7F10 00000001 F95B6A1C F924BE20 F95B6A00
A70 00000004 F924BE20 C01AD56A F924BE20 C0000A48 F924BE20 C0193731 F924BE20
A90 00000000 F981F600 EE04C300 F924BE20 C002FA1B 00000002 000000F0 C0000A48
AB0 F924BE20 C0149F95 F924BE20 EDF0CEC0 F981F600 EE04C300 EE04C378 00000000
AD0 EE04C378 F95B6E00 EE04C378 C014A041 EE04C300 F981F600 EE04C378 EE04C300
AF0 C014A2D8 EE04C300 F9226100 00000040 EE04C378 C002F941 EE04C378 F920F000
B10 C021C507 EE04C378 C08D94C0 C08D94A8 C08D94A8 F18452C0 00000000 C04D22F8
B30 00000000 00000002 F920E000 C00EE704 C0106CBF F920F000 FFFDAB80 C08D94A8
B50 00000000 00000000 C08D94D4 C04DCD24 C005B408 00000000 C0167167 C08D94A8
B70 C08D9054 C08D9084 C08D94A8 C08D9084 FFFDABC0 C0166EC3 C08D94A8 00000246

PANIC REGISTERS:
  kcp:fffdac08 trp:       - efl:       - eip:c01889db xcmn_panic+5b()
  eax:fffdac08 ebx:       0 ecx:c04dcbd0 edx:       7 cs: 100 ds: 108 fs:   0
  esi:ffff62a0 edi:c0232634 ebp:fffda940 esp:fffda920 ss: 108 es: 108 gs:   0
STACK TRACE FOR IDLE CONTEXT OF ENGINE 1:
 xcmn_panic+5b(c0232634)..............................esp:fffda944 ret:c01899c7
 xcmn_err+1c7(3 c0232634 fffda994)....................esp:fffda978 ret:c01868aa
 cmn_err+14(3 c0232634 f342efff)......................esp:fffda988 ret:c00d2875

Moderator's Comments:
Mod Comment edit by bakunin: please use CODE-tags. Thank you.

Last edited by bakunin; 08-25-2014 at 11:02 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Panic

Hi All, When I came officce this morning I saw this error messages on the screen ----- PANIC:srmountfun - Error 6 mounting rootdev hd (1/42) Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages Dump not completed -------- and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies

2. SCO

Panic :

Hi Friends , i am getting the following error when iam booting a sco unix system. ------------------ H init PANIC : srmountfun --Error 22 mounting rootdev hd(1/42) cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages. Dump not completed. Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies

3. Solaris

panic message

When ever i change my hard disk position from primary master to secondary slave, the solaris os gives a panic messge. how could i solve it. (2 Replies)
Discussion started by: ajay234
2 Replies

4. Solaris

Savemail panic - Need help

Hi All, I've been troubleshooting this sendmail panic I'm getting on my dmesg. The errors are: Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: Losing ./qfl1G1hGuD000884: savemail panic Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: SYSERR(root): savemail: cannot save... (2 Replies)
Discussion started by: grumash
2 Replies

5. HP-UX

Reboot After Panic

Hi all, Does anybody know what kinds of events can prompt the following? I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies

6. SCO

Usb To Serial (sco6)

According to sco6 usb supplement, once you install it, you can install a bafo industries (BF-810) in the computer. I have done all that and followed the intructions completely and it shows up using usbprobe and l /dev/usb_ser* Problem is that when I go to mkdev serial, it is not there. Anyone... (1 Reply)
Discussion started by: jn5519
1 Replies

7. SCO

SCO6 NFS Problem mounting Windows resource

Hi, We are testing SCO6 for an upgrade. We currently have a SCO5.0.4 system that mounts a remote directory on a Windows 2000 server. The windows server has 'services for unix' installed to enable the required directory to be mounted on the SCO system. On SCO we run '/etc/mount -v -f NFS... (2 Replies)
Discussion started by: sidnagra
2 Replies

8. SCO

SCO6: Upgrading nd: no intel gigabit drivers?

I just (re)installed SCO6 here from scratch because I am hunting a problem. So, I installed it, then got the SCO OpenServer Release 6.0.0 Maintenance Pack 4 Device Drivers Supplement .iso and installed the nd package. # mount -F cdfs /dev/cd0 /cd-rom # pkgadd -d /cd-rom Then elect the nd... (2 Replies)
Discussion started by: dalek
2 Replies

9. Red Hat

server panic

Hi, one of our linux server got panic with the following messages Jun 2 17:09:57 inchesfttu006 kernel: ------------------------ Jun 2 17:09:57 inchesfttu006 kernel: kernel BUG at kernel/exit.c:904! Jun 2 17:09:57 inchesfttu006 kernel: invalid operand: 0000 Jun 2 17:09:57 inchesfttu006... (1 Reply)
Discussion started by: rajasekg
1 Replies

10. UNIX for Advanced & Expert Users

what does the kernel panic mean?

Hi, all: How should I obtain the reason of kernel panic? How should I debug the program which result in a kernel panic? What can I get from the panic information? li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies
STAPFUNCS(3stap)                                                                                                                  STAPFUNCS(3stap)

NAME
stapfuncs - systemtap functions DESCRIPTION
The following sections enumerate a few of public functions provided by standard tapsets installed, show in the stappaths(7) manual page. Most are individually documented in the 3stap manual section, with the function:: prefix. Each function is described with a signature, and its behavior/restrictions. The signature line includes the name of the function, the type of its return value (if any), and the names and types of all parameters. The syntax is the same as printed with the stap option -p2. Examples: example1:long (v:string, k:long) In function "example1", do something with the given string and integer. Return some integer. example2:unknown () In function "example2", do something. There is no explicit return value and take no parameters. TARGET_SET target_set_pid:long (tid:long) Return whether the given process-id is within the "target set", that is whether it is a descendent of the top-level target() process. target_set_report:unknown () Print a report about the target set, and their ancestry. ERRNO errno_str:string (e:long) Return the symbolic string associated with the given error code, like "ENOENT" for the number 2, or "E#3333" for an out-of-range value like 3333. REGISTERS register:long (name:string) Return the value of the named CPU register, as it was saved when the current probe point was hit. If the register is 32 bits, it is sign-extended to 64 bits. For the i386 architecture, the following names are recognized. (name1/name2 indicates that name1 and name2 are alternative names for the same register.) eax/ax, ebp/bp, ebx/bx, ecx/cx, edi/di, edx/dx, eflags/flags, eip/ip, esi/si, esp/sp, orig_eax/orig_ax, xcs/cs, xds/ds, xes/es, xfs/fs, xss/ss. For the x86_64 architecture, the following names are recognized: 64-bit registers: r8, r9, r10, r11, r12, r13, r14, r15, rax/ax, rbp/bp, rbx/bx, rcx/cx, rdi/di, rdx/dx, rip/ip, rsi/si, rsp/sp; 32-bit registers: eax, ebp, ebx, ecx, edx, edi, edx, eip, esi, esp, flags/eflags, orig_eax; segment registers: xcs/cs, xss/ss. For powerpc, the following names are recognized: r0, r1, ... r31, nip, msr, orig_gpr3, ctr, link, xer, ccr, softe, trap, dar, dsisr, result. For s390x, the following names are recognized: r0, r1, ... r15, args, psw.mask, psw.addr, orig_gpr2, ilc, trap. u_register:long (name:string) Same as register(name), except that if the register is 32 bits, it is zero-extended to 64 bits. NUMBERED FUNCTION ARGUMENTS The functions in this section provide the values of a probed function's arguments. They can be called when you have hit a probe point at the entry to a function. Arguments are referred to by number, starting at 1. Ordinarily, you can access arguments by name as well, but you may find these functions useful if the code you are probing was built without debugging information. On 32-bit architectures -- and when probing 32-bit applications on 64-bit architectures -- a 64-bit argument occupies two "arg slots." For example, if you are probing the following function void f(int a, long long b, char *c) you would refer to a, b, and c as int_arg(1), longlong_arg(2), and pointer_arg(3), respectively, on a 64-bit architecture; but on a 32-bit architecture, you would refer to c as pointer_arg(4) (since b occupies slots 2 and 3). If the function you are probing doesn't follow the default rules for argument passing, you need to call one of the following functions (which see) in your handler before calling any *_arg function: asmlinkage(), fastcall(), or regparm(). (This isn't necessary when refer- ring to arguments only by name.) int_arg:long (n:long) Return the value of argument n as a signed int (i.e., a 32-bit integer sign-extended to 64 bits). uint_arg:long (n:long) Return the value of argument n as an unsigned int (i.e., a 32-bit integer zero-extended to 64 bits). long_arg:long (n:long) Return the value of argument n as a signed long. On architectures where a long is 32 bits, the value is sign-extended to 64 bits. ulong_arg:long (n:long) Return the value of argument n as an unsigned long. On architectures where a long is 32 bits, the value is zero-extended to 64 bits. longlong_arg:long (n:long) Return the value of argument n as a 64-bit value. ulonglong_arg:long (n:long) Same as longlong_arg(n). pointer_arg:long (n:long) Same as ulong_arg(n). Use with any type of pointer. s32_arg:long (n:long) Same as int_arg(n). u32_arg:long (n:long) Same as uint_arg(n). s64_arg:long (n:long) Same as longlong_arg(n). u64_arg:long (n:long) Same as [u]longlong_arg(n). asmlinkage:unknown () The probed kernel function is declared asmlinkage in the source. fastcall:unknown () The probed kernel function is declared fastcall in the source. regparm:unknown (n:long) The probed function was built with the gcc -mregparm=n option. (The i386 kernel is built with -mregparm=3, so systemtap considers regparm(3) the default for kernel functions on that architecture.) Only valid on i386 and x86_64 (when probing 32bit applications). Produces an error on other architectures. For some architectures, the *_arg functions may reject unusually high values of n. QUEUE_STATS The queue_stats tapset provides functions that, given notifications of elementary queuing events (wait, run, done), tracks averages such as queue length, service and wait times, utilization. The following three functions should be called from appropriate probes, in sequence. qs_wait:unknown (qname:string) Record that a new request was enqueued for the given queue name. qs_run:unknown (qname:string) Record that a previously enqueued request was removed from the given wait queue and is now being serviced. qs_done:unknown (qname:string) Record that a request originally from the given queue has completed being serviced. Functions with the prefix qsq_ are for querying the statistics averaged since the first queue operation (or when qsq_start was called). Since statistics are often fractional, a scale parameter is multiplies the result to a more useful scale. For some fractions, a scale of 100 will usefully return percentage numbers. qsq_start:unknown (qname:string) Reset the statistics counters for the given queue, and start tracking anew from this moment. qsq_print:unknown (qname:string) Print a line containing a selection of the given queue's statistics. qsq_utilization:long (qname:string, scale:long) Return the fraction of elapsed time when the resource was utilized. qsq_blocked:long (qname:string, scale:long) Return the fraction of elapsed time when the wait queue was used. qsq_wait_queue_length:long (qname:string, scale:long) Return the average length of the wait queue. qsq_service_time:long (qname:string, scale:long) Return the average time required to service a request. qsq_wait_time:long (qname:string, scale:long) Return the average time a request took from being enqueued to completed. qsq_throughput:long (qname:string, scale:long) Return the average rate of requests per scale units of time. INDENT The indent tapset provides functions to generate indented lines for nested kinds of trace messages. Each line contains a relative time- stamp, and the process name / pid. thread_indent:string (delta:long) Return a string with an appropriate indentation for this thread. Call it with a small positive or matching negative delta. If this is the outermost, initial level of indentation, reset the relative timestamp base to zero. thread_timestamp:long () Return an absolute timestamp value for use by the indentation function. The default function uses gettimeofday_us SYSTEM system (cmd:string) Runs a command on the system. The command will run in the background when the current probe completes. INET These functions convert between network (big-endian) and host byte order, like their namesake C functions. ntohll:long (x:long) Convert from network to host byte order, 64-bit. ntohl:long (x:long) Convert from network to host byte order, 32-bit. ntohs:long (x:long) Convert from network to host byte order, 16-bit. htonll:long (x:long) Convert from host to network byte order, 64-bit. htonl:long (x:long) Convert from host to network byte order, 32-bit. htons:long (x:long) Convert from host to network byte order, 16-bit. SIGNAL get_sa_flags:long (act:long) Returns the numeric value of sa_flags. get_sa_handler:long (act:long) Returns the numeric value of sa_handler. sigset_mask_str:string (mask:long) Returns the string representation of the sigset sa_mask. is_sig_blocked:long (task:long, sig:long) Returns 1 if the signal is currently blocked, or 0 if it is not. sa_flags_str:string (sa_flags:long) Returns the string representation of sa_flags. sa_handler_str(handler) Returns the string representation of sa_handler. If it is not SIG_DFL, SIG_IGN or SIG_ERR, it will return the address of the han- dler. signal_str(num) Returns the string representation of the given signal number. DEVICE MAJOR:long(dev:long) Extracts the major device number from a kernel device number (kdev_t). MINOR:long(dev:long) Extracts the minor device number from a kernel device number (kdev_t). MKDEV:long(major:long, minor:long) Creates a value that can be compared to a kernel device number (kdev_t). usrdev2kerndev:long(dev:long) Converts a user-space device number into the format used in the kernel. FILES
More files and their corresponding paths can be found in the stappaths(7) manual page. SEE ALSO
stap(1), function::*(3stap), tapset::*(3stap), stappaths(7) STAPFUNCS(3stap)
All times are GMT -4. The time now is 01:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy