mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zeno R.R. Davatz" <zdavatz@ywesee.com>
To: linux-kernel@vger.kernel.org
Subject: Re: INIT:ld"2" respawning too fast:disabled for 5 minutes
Date: Thu, 26 Jun 2003 11:34:53 +0200	[thread overview]
Message-ID: <20030626113453.5f61c0f8.zdavatz@ywesee.com> (raw)
In-Reply-To: <36993D449C7FA647BF43568E0793AB3E061D2C@nevis_pune_xchg.pune.nevisnetworks.com>

Hi 

thanks for the input.

You mean I need to check the config in 'make menuconfig'?

Any idea where exactly I could look?

Also, how did you boot into the old kernel, getting your maschine back up again? I only manage to reinstall from zero...

Thanks for your time and help.

Zeno

On Thu, 26 Jun 2003 14:44:34 +0530
"Girish Kale" <girish.kale@nevisnetworks.com> wrote:

> Hi,
> 
> What this message means is that :
> 
> "if you make a mistake that prevents a particular program from starting,
> and the action is respawned, init might get caught in a loop. That is,
> init tries to start the program, cannot, for whatever reason and then
> tries to start it again. If init finds that it is starting the program
> more than 10 times within 2 minutes, it will treat this as an error and
> stops trying. Typically you will get messages in the system log that the
> process is "respawning too rapidly"." Please read :
> 
> http://www.linux-tutorial.info/cgi-bin/display.pl?65&0&64&0&3
> 
> I also faced a similar problem - it gave me INIT:ID"1" respawning too
> fast" , when I tried to login to my machine. This got resolved when I
> reconfigured the kernel. But yet to figure out the "exact" change which
> causes my problem.
> 
> Regards,
> Girish
> 
> -----Original Message-----
> From: Zeno R.R. Davatz [mailto:zdavatz@ywesee.com] 
> Sent: Thursday, June 26, 2003 2:28 PM
> To: linux-kernel@vger.kernel.org
> Subject: INIT:ld"2" respawning too fast:disabled for 5 minutes
> 
> Hi List
> 
> I succeded twice in making a kernel_image with the Debian kernel-package
> and installaing the .deb file (2.4.18, 2.4.20).
> 
> My Installation where I boot from is bf24-2.4.20 (floppies).
> 
> I download the kernel sources to /usr/src/linux-2.4.21 I do make clean,
> make menuconfig and then make-kpkg -rev ywesee.1 kernel_image. 
> 
> The maschine ends the compilation just fine and I do dpkg -i
> kernel_image-2.4.21-ywesee.1-i386.deb.
> 
> Then I reboot, everythings starts fine _without a kernel panic.
> 
> But: After starting the cron daemon I get:
> INIT:ld"2" respawning too fast:disabled for 5 minutes 
> 
> I get this several times...
> 
> Why do I get this message and how can I get rid of it so my 2.4.21 boots
> nicely.
> 
> (I need to start my installation again from the beginning as I can not
> boot into the old system).
> 
> Many thanks in advance for any help and hints.
> 
> Zeno
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
Mit freundlichen Gruessen / Best regards

Zeno Davatz
Strategie und Akquisition

+41 1 350 85 86

www.ywesee.com > intellectual capital connected > www.generika.cc

  reply	other threads:[~2003-06-26  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26  9:14 Girish Kale
2003-06-26  9:34 ` Zeno R.R. Davatz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-26 11:53 Girish Kale
2003-06-26 10:01 Girish Kale
2003-06-26 10:25 ` Zeno R.R. Davatz
2003-06-26 11:08   ` Michael Hunold
2003-06-26  8:58 Zeno R.R. Davatz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030626113453.5f61c0f8.zdavatz@ywesee.com \
    --to=zdavatz@ywesee.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®