From owner-freebsd-current@FreeBSD.ORG Fri May 13 10:23:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC8FA16A4CE for ; Fri, 13 May 2005 10:23:05 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 365F743D64 for ; Fri, 13 May 2005 10:23:05 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j4DAN2gZ027758 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 13 May 2005 20:23:03 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])j4DAN2mc036732; Fri, 13 May 2005 20:23:02 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.13.1/8.13.1/Submit) id j4DAN2wl036731; Fri, 13 May 2005 20:23:02 +1000 (EST) (envelope-from peter) Date: Fri, 13 May 2005 20:23:02 +1000 From: Peter Jeremy To: Andrey Chernov , current@freebsd.org Message-ID: <20050513102302.GC34537@server.vk2pj.dyndns.org> References: <20050513041929.GA34210@nagual.pp.ru> <20050513072713.GB34537@server.vk2pj.dyndns.org> <20050513074948.GA41987@nagual.pp.ru> <20050513084514.GB43605@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050513084514.GB43605@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i Subject: Re: Who/what broke -current kernel? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 10:23:05 -0000 On Fri, May 13, 2005 at 12:45:15PM +0400, Andrey Chernov wrote: >On Fri, May 13, 2005 at 11:49:48AM +0400, Andrey Chernov wrote: >> I'll try, but I doubt it helps, if directory is not found. >> It looks line someone damage ufs code or softupdates (I have them). > >I try bootverbose and it not difers from old (i.e. working) kernel >output. OK. Elsewhere you've wondered if it is a low-level bug in ATAmkIII. If you believe it may be a low-level bug, you could try: 1) Get a USB memory stick, floppy disk or CD-ROM 2) Build a UFS[2] filesystem on it 3) Copy /sbin/init into an sbin subdirectory on the device 4) Use "boot -a" and specify that device as the root filesystem. This won't work (because there's nothing for init to do if it starts) but it will let you determine whether the bug is in the UFS[2] code (exec still fails) or in the ATA driver (the exec works - init starts but dies because there's nothing else in root). Your other option is a binary search through -current and/or a session with kgdb or ddb. Peter