Linux Redhat Enterprise

We have Ver 4. It has been NO end of problems. We have one problem that
Red Hat cannot fix at this time, and we need to reboot every 12 or so
hours even to work on the machine.

And NOW when we reboot, we get
ID "x" spawning too fast

and something about waiting 5 mins.

This is ridiculous.

I looked around google groups and found a few references to this, but
the answer was always to set init 3 at the boot prompt. But we don't
get that far.

Is there any solution or should I just loook for a better O/S?

Kate

.

Relevant Pages

  • Re: 2.6.15-rt20, "bad page state", jackd
    ... Trying to fix it up, but a reboot is needed ... # Firmware Drivers ... # ACPI Support ...
    (Linux-Kernel)
  • Re: despair
    ... fix them. ... analyzed it and told mgmt that the next time such and such falls on a ... handover admins. ... If he wants to come in to reboot it ...
    (comp.os.vms)
  • should I be worried, dmesg prints ominous message about mmap problems....
    ... Trying to fix it up, but a reboot is needed ... Call Trace: ... Bad page state at free_hot_cold_page (in process 'roller', ...
    (Debian-User)
  • Re: Outlook Express 6 Hyperlink
    ... I am running Nvidia Nforce Firewall,, Mcafee ... reboot. ... Who Cares ... Outlook will not open messages " Out of Memory Error" - your fix ...
    (microsoft.public.windowsxp.general)
  • crash on x86_64 - mm related?
    ... You can see the voluminous kernel output below. ... wait for someone to reboot the machine first. ... Trying to fix it up, ... CPU 1 ...
    (Linux-Kernel)