APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > News Posts > crash failure ––>Re: 'crash' utility failure
Printer Friendly Version




News Group Posts

crash failure




From: bv@wjv.com (Bill Vermillion)
Subject: Re: 'crash' utility failure
References: <00a001c19be0$a6975640$7001a8c0@estacion3>
<20020114020456.J14415@mammoth.ca.sco.com>
<1c9ceead.0201180451.b264d9c@posting.google.com> Date: Fri, 18 Jan 2002 19:39:26 GMT In article <1c9ceead.0201180451.b264d9c@posting.google.com>, Fernando Ronci <fernando@waycom.com.ar> wrote: >Bela Lubkin <belal@sco.com> wrote in message news:<20020114020456.J14415@mammoth.ca.sco.com>... >> Fernando Ronci wrote: >> > What can be wrong with a dump image after a kernel panic (0x0000000E) of OSR >> > 5.0.0 that it cannot be read by the 'crash' utility? >> > I saved the image in /usr/tmp/dump.1201 and when I issue: >> > crash -d /usr/tmp/dump.1201 >> > >> > I get: >> > dumpfile = /usr/tmp/dump.1201, namelist = /unix, outfile = stdout >> > Read error on page table entry at 0xfc60ff0

>> > What does the "Read error on page table entry at 0xfc60ff0" error mean?

>> It means that the dump image is corrupt, for crash's purposes.

>> During a panic, the system is in an unstable state (by
>> definition). Not all panics produce clean, readable dumps.

>> It's also possible that it was a clean dump, but you corrupted it
>> when you saved it.

>> > I need to know why my system began panicing at random
>> > intervals (about 3 times a day) after a major hardware
>> > upgrade. I moved the old SCSI HD to a new motherboard with
>> > a PIII 900 MHz, new memory, new NIC, legacy ISA computone
>> > and legacy Adaptec card. After reading Tony's document at
>> > http://www.aplawrence.com/Unixart/trape.shtml I'm almost sure
>> > the culprit is either the memory or the new NIC driver (a very
>> > ordinary Encore PCI card), but 'crash' needs to be able to read
>> > the dump image to confirm that.

The bad dump, the crashes, the errors coming in with different
locations still sound to me like SCSI problems.  You said OLD SCSI
drive above.  But did you move the old controller, and cables, and
everything that worked before, or just the old SCSI drive to a new
computer.  It really smells/feels like cabling termination.  The
higher speed of the new CPU could be causing enough RF type
problems to cause SCSI failure.  Make sure you have a >>ACTIVE<<
terminator on the line.  So often spurious SCSI problem give
messages that make you think the error is elsehwere.














>In this past week, I changed no less than half a dozen PS/2 keyboards,
>some very new, others very old.

I don't know why you keep thinking it is a keyboard error.  The
results you dislayed don't indicate that to me.

>As all of you know OpenServer way far too more than me, I will be
>infinitely thankful if some helps me get rid of this problem. OSR
>5.0.0 is rather old, has memory leak issues and so forth, but I had it
>up and running for almost 6 years and no single panic at all !!. So
>I'm convinced I've got a piece of hardware (probably the keyboard)
>that is interrupting in such a way that OSR 5.0.0 doesn't know how to
>handle and thus panics.

But you had OSR5 up an running on an old motherboard.  I really
suspect that if you put the OSR 5.0.6 on that old system it would
run rock solid.   You are attributing what appears to me to be HW
errors to SW.   Almost invariably that is not the case.

Bill
-- 
Bill Vermillion - bv @ wjv . com
 

If this page was useful to you, please click to help others find it:  

Your +1's can help friends, contacts, and others on the web find the best stuff when they search.

Comments?



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

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.

g_face.jpg

This post tagged:

       - SCO_OSR5




Unix/Linux Consultants

Skills Tests

Guest Post Here