Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PANIC: k_trap - Kernel mode trap type 0x0000000E

Status
Not open for further replies.

sharper

MIS
Sep 4, 2001
109
IE
Hello all,

I'm working on a Compaq Proliant 1600 300MHz PII with SCO openserver 5.05A that is crashing with the above error on average once a week but without any consistency (except that it seems to be happening more regularly in the morning at start of business(I thought that it may be only when users are logging in but it doesn't happen every morning)). I've saved the last three memory dumps and ran crash(ADM) on them. As an article on pcunix.com suggested (that k_trap at 0x0000000E is commonly caused by faulty memory)I replaced the memory (256MB) with known good memory. The server panic'd the following morning. (The server is a 4 hour drive away so I have to plan a visit to site).This SCO box is serving about 25 users and running an informix (I think) database.

Looking at the result of 'panic' in crash(ADM) the top of the stack is kmem_alloc then in_getmem then in_getzmem. Am I right in thinking that these are memory management functions? (the STKADDR and FRAMEPTR are the same in all crash dumps but the POSSIBLE ARGUMENTS are different). Could this still me a hardware error ie the memory slot/processor board?. the results of the last two crash dumps can be found at:


and the result of hw can befounds at




Any ideas on what could be causing this whould be greatly appreciated.

Oscar McMahon
 
If you're still having problems and it seems intermittant or random, try replacing the backplane.
 
Installed SCO 5.0.5 on a IBM Netfinity. When try to reboot the system using "init 6", I receive the following error:

PANIC: pfntopfdat - Bad pf num 000EFE9A.
Cannot dump ####pages to dumpdev hd (1/41): Space for only #### pages.

Dump not complete......
Could you help me?
Thanks.

Mike
 
Mikefn

PANIC: pfntopfdat - Bad pf num n

A page frame number yielded an invalid physical address.

Does this happen on a cold boot?
Try at the boot prompt:
defbootstr mem=/p

 
stanhubble

It doesn't happen on a cold boot.
It only happens when I type "init 6".
If I type "reboot" then it works fine.
Have any ideas?
Thanks.

Mike
 
ok then it is something executing either from
/etc/rc.d/6
or
something in /etc/inittab that runs on transition to the init level 6
check anything with a 6 in the 2nd : delimited field in the inittab file
if you find something with a 6 in it try commenting it out and see if the problem persists
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top