From owner-freebsd-alpha Mon Dec 9 16:28:40 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D571337B401 for ; Mon, 9 Dec 2002 16:28:38 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34FB543EA9 for ; Mon, 9 Dec 2002 16:28:38 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA24629; Mon, 9 Dec 2002 19:28:37 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gBA0S7o03216; Mon, 9 Dec 2002 19:28:07 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15861.13591.592853.836992@grasshopper.cs.duke.edu> Date: Mon, 9 Dec 2002 19:28:07 -0500 (EST) To: "Sergey Amelyuschenko" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/45947: init does not invoke getty In-Reply-To: <200212060910.gB69A3ls034629@freefall.freebsd.org> References: <200212060910.gB69A3ls034629@freefall.freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sergey Amelyuschenko writes: > It is much worse - it does not even try to open /etc/ttys :-( > I run this sequence "ktrace -di -p 1 ; kill -HUP 1 ; sleep 0.5 ; ktrace -C" > after editing /etc/ttys on both alpha and i386. Here is the result: > > alpha# kdump | grep init > 1 init PSIG SIGHUP caught handler=0x120002780 mask=0x9e7c9054 > code=0xffffffff > 1 init RET wait4 -1 errno 4 Interrupted system call > 1 init CALL sigreturn(0x11ffb8c8) > 1 init RET sigreturn JUSTRETURN > 1 init CALL wait4(0xffffffffffffffff,0x11ffbc70,0x2,0) Hmm.. 2 ideas: 1) Perhaps it still thinks that its running a startup script and has not made it fully multi-user. Have you installed or upgraded any ports recently? something in /usr/local/etc/rc.d/foo.sh started so that it does not go into the background might block init. 2) init has gone totally insane. I'd stick some printfs in transition_handler(), and in multi_user(), and in clean_ttys(). So as to try to see what's happening when the signal is delivered. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message