compaq proliant 1600

[Toto Gamez]

thanks guys,

It's good that I have not yet formatted my old server. I return to production my old server again because my Compaq proliant stops every now and then without any error messages including in dmesg except for  this:
pasay modprobe: modprobe: Can't locate module char-major-10-134
pasay modprobe: modprobe: Can't locate module sound-slot-0
pasay modprobe: modprobe: Can't locate module sound-service-0-3 
 Trying to run your advise and inform you guys of the developments

thanks again

  ----- Original Message ----- 
  From: Rick Stevens 
  To: Mark Knecht ; Getting started with Red Hat Linux 
  Sent: Saturday, October 02, 2004 1:09 AM
  Subject: Re: compaq proliant 1600


  Mark Knecht wrote:
  > After rebooting my machine I look on my /var/log/messages for any
  > reason that caused my machine to stop responding and only sw this
  > messages:
  >   
  >  
  > pasay modprobe: modprobe: Can't locate module char-major-10-134
  > pasay modprobe: modprobe: Can't locate module sound-slot-0
  > pasay modprobe: modprobe: Can't locate module sound-service-0-3
  >  
  > I dont have any sound card in my machine, and it hungs every now and then 
  > any hint?    
  >   
  > 
  > Toto,
  >    These look like Alsa driver messages saying they cannot find a
  > sound card. I'm guessing that there may be some default messages in
  > /etc/modules.conf. If you're not using sound then you can just comment
  > them out.
  > 
  >    If they truly cause a machine to hang at boot time then it seems as
  > if there is a bug that needs reporting, either to the Alsa developers
  > or to someone else.

  Those messages are quite typical and aren't fatal.  They surely
  shouldn't cause the system to die.  You should also check /var/log/dmesg
  for any messages pertaining to the problem.

  To be honest, this sort of thing is typically caused one of two things:

  1.  Intermittent connections on PCI cards, RAM sticks or CPUs.  Shut the
  machine down and reseat all of the PCI and RAM cards.  If you can, try
  reseating the CPUs, too (not always so easy).  If you moved the machine
  physically, this is the most likely problem.

  2.  Flakey RAM.  Just because the machine will run Windows is no
  indication that RAM is reliable.  If you can, download and run memtest86
  (http://www.memtest86.com) to check it (or boot a Fedora Core CD and
  enter "memtest86" at the "boot:" prompt).
  ----------------------------------------------------------------------
  - Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
  - VitalStream, Inc.                       http://www.vitalstream.com -
  -                                                                    -
  -         Okay, who put a "stop payment" on my reality check?        -
  ----------------------------------------------------------------------



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/redhat-install-list/attachments/20041004/8af6d0ec/attachment.htm>