SCO Unix ® FAQ section

Unix (3.2v4.2) and ODT FAQ

This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open Desktop or Openserver.

There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.

How do I fix a kernel trap 0x00000006?

This is an ancient post with no relevance to modern systems.

NOTE: This problem appeared at some point in 3.2v4.x, and is fixed in OpenServer 5. See the documentation in TA 482366 for more detail.

This is due to executing an invalid instruction in kernel mode (trap 6 is for an invalid instruction; a user process which does this will simply die with a core dump). If your particular problem is a double panic and it doesn't leave a system memory dump in whatever device you've chosen for dumps (usually /dev/swap), apply the following patch.

This is due to a problem in the kernel's querytlb() routine, which may allow the Pentium to execute a 386-specific instruction which is not supported on the Pentium. The cure involves patching a kernel module using _fst. (see part 1 on where to find /etc/_fst). Go into the /etc/conf/pack.d/kernel directory. We're going to work on locore.o, so make a backup and then run _fst -w locore.o - The conversation between you and _fst goes like this (the * is a prompt from _fst; don't type it or any of _fst's responses):

* querytlb+5?w 0x9090
querytlb+ox5:     0x375=0x9090
* querytlb,4?ai
querytlb:          call  near 0x17:0x0
querytlb+0x5:      nop
querytlb+0x6:      nop
querytlb+0x7       sub     eax, eax
* $q
 

This fixes one of the modules which is linked into the kernel, so you only have to apply it once. Relink and reboot.

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.