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

Bug#74346: marked as done (INIT locks up installing debian 2.2)

Your message dated 15 Oct 2000 01:51:15 -0400
with message-id <oar95i4ppo.fsf@arroz.fake>
and subject line Bug#74346: MB-CPU trouble
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 8 Oct 2000 21:15:22 +0000
>From palou@yahoo.com Sun Oct 08 16:15:22 2000
Return-path: <palou@yahoo.com>
Received: from smtp3.mail.yahoo.com (smtp1b.mail.yahoo.com) [::ffff:] 
	by master.debian.org with smtp (Exim 3.12 1 (Debian))
	id 13iNn0-0003Hn-00; Sun, 08 Oct 2000 16:15:22 -0500
Received: from 82-barc-x44.libre.retevision.es (HELO kitten.ai) (
  by smtp.mail.vip.suc.yahoo.com with SMTP; 8 Oct 2000 21:15:19 -0000
X-Apparently-From: <palou@yahoo.com>
Received: (from palou@localhost)
	by kitten.ai (8.9.3/8.9.3) id XAA01427;
	Sun, 8 Oct 2000 23:15:33 +0200
Date: Sun, 8 Oct 2000 23:15:33 +0200
Message-Id: <200010082115.XAA01427@kitten.ai>
X-Authentication-Warning: kitten.ai: palou set sender to palou@yahoo.com using -f
From: <palou@yahoo.com>
To: submit@bugs.debian.org
Subject: INIT locks up installing debian 2.2
Delivered-To: submit@bugs.debian.org

Package: Install, boot disks
Version: debian 2.2 r0

Installing debian 2.2 r0 from CD
No probelms until writing MBR on hard drive, and re-boot
Re-boot to hard drive, after message "Starting internet superserver:
inetd" I get different responses, but they always end with the same
message and tty1 freezes. The message is:

INIT: Id "1" respawning too fast disabled for 5 minutes

If left for 5 minutes, this happens again.
I have tracked it down to the special inittab file for the first
boot. In it, for tty1 there is:

1:2345:respawn:/usr/sbin/dpkg-reconfigure base-config </dev/tty1
>/dev/tty1 2>&1

If I try to tun the dpkg-reconfigure from another tty, I get a variety
of Segmentation faults and other crashes. I tried changing the respawn
to once in the inittab, but the tty just locks up. So I guess the
dpkg-reconfigure is crashing so often that it cause INIT to respawn
too fast. I've made a few more tests and it looks like any perl script
script can cause a Segmentation fault. Even the plain invocation of
perl cause (intermittently) Segmentation faults.

Are there any knwon cause for behavior like this? Any ways to bypass
it? Am I correct thinking I could just install packages and my final
configurations myself without too much trouble?



Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Received: (at 74346-done) by bugs.debian.org; 15 Oct 2000 05:50:33 +0000
>From adam@onshore.com Sun Oct 15 00:50:33 2000
Return-path: <adam@onshore.com>
Received: from (burrito.onshore.com) [::ffff:] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 13kggr-0000cN-00; Sun, 15 Oct 2000 00:50:33 -0500
Received: from arroz.fake (localhost [])
	by burrito.onshore.com (Postfix) with ESMTP
	id 1943D93804; Sun, 15 Oct 2000 01:51:16 -0400 (EDT)
Sender: apharris@burrito.onshore.com
To: <palou@yahoo.com>
Cc: 74346-done@bugs.debian.org
Subject: Re: Bug#74346: MB-CPU trouble
References: <[🔎] 200010121644.SAA02073@kitten.ai>
From: Adam Di Carlo <adam@onshore.com>
Date: 15 Oct 2000 01:51:15 -0400
In-Reply-To: <palou@yahoo.com>'s message of "Thu, 12 Oct 2000 18:44:48 +0200"
Message-ID: <oar95i4ppo.fsf@arroz.fake>
Lines: 12
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 74346-done@bugs.debian.org

<palou@yahoo.com> writes:

> I put back the old trsuty Cyrix 6x86 166+ in the machine and
> everything runs like a charm. Therefore I'm sure this is a MB-CPU
> problem and nothing to do with Debian.

Yeah, I figured it was a hardware problem.

Closing this bug.

.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>

Reply to: