[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Aeolus

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Aeolus
  • Date: Wed, 10 Apr 2002 12:38:16 -0600
Larry Riddle wrote:
> 
> The replacement of aeolus memory chips made no difference.  The ldm
> shutdown more or less on schedule last night and again this
> morning.  However, my "nag me" script worked just fine and I received
> numerous pages telling me the METAR files were too small.
> 
> Note: we examined the memory board slots while we were changing chips
> yesterday.  There were no bent pins or extraneous material in the sockets.
> 
> I'm open to suggestions.
> 
> Larry
> 
>       ---===---=-=-=-=-=-=-=-=-=-=-=====[\/]=====-=-=-=-=-=-=-=-=-=-=---===---
>     -----===(*  Climate's what we expect, but weather's what we
> get.  *)===-----
>    Larry Riddle : Climate Research Division : Scripps Institution of
> Oceanography
>        University of California, San Diego : La Jolla, California  92093-0224
>        Phone: (858) 534-1869 : Fax: (858) 534-8561 : E-Mail: address@hidden

Hi Larry,

I'm sorry the memory swap did not solve the problem.  Are you sure the
chips that were put in were good?  That's not exactly the way I would
have gone about it myself as it does introduce a new variable.

The system logs are reporting the same problems even after the memory
swap:

# grep panic messages
Jan  3 14:19:51 aeolus vmunix: panic (cpu 0): kernel memory fault
Jan  7 09:39:45 aeolus vmunix: panic (cpu 0): kernel memory fault
Jan 19 14:55:42 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active
Feb  5 07:56:31 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active
Mar 12 14:18:00 aeolus vmunix: panic (cpu 0): ialloc: dup alloc
Apr  4 18:48:46 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active
Apr  5 19:31:38 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active
Apr  6 07:34:42 aeolus vmunix: panic (cpu 0): kernel memory fault
Apr  7 20:34:16 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active
Apr  8 01:42:38 aeolus vmunix: panic (cpu 0): kernel memory fault
Apr  9 01:42:36 aeolus vmunix: panic (cpu 0): u_vp_oop_badop: vnode
object operation not supported
Apr 10 00:44:17 aeolus vmunix: panic (cpu 0): kernel memory fault
Apr 10 08:00:16 aeolus vmunix: panic (cpu 0): vm_page_activate: already
active

If the new memory is definately good, then this may be a motherboard
problem.  Do you have hardware support for this machine?

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************