Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a legacy equipment based on the Sun SPARCstation 1+ architecture. Slackware 14.1 is the
installed OS.
I am starting to see software trap errors with a code number appear frequently now. These are
causing system processor switches to occur. Is there somewhere under the OS where I can
troubleshoot what is causing these errors? I have checked under /var/log but has not helped.
An example of an error is "RTP B software trap, code $4629 $00000000". This indicates that a RTP
(Real Time Processor) trap occurred on processor side B (online) side. This error causes the system
to switch to offline processor side A.
I have no manufacturing support for this equipment but need to keep this system running!
I do not use Slackware, but I thought your problem was interesting and was waiting for a response from a more knowledgeable person to help you so I could learn on the sidelines. Since no one has stepped up I thought I would do a little research. I came across the following document that may, or may not, help you in you search for an answer concerning the software trap errors. I read through the document and in Chapter 4, "Finding Faults in Error Handling Code," for Linux systems, some actions are discussed that may help your situation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
