From owner-freebsd-current@FreeBSD.ORG Tue Feb 5 19:56:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF64416A41B for ; Tue, 5 Feb 2008 19:56:27 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 57F9413C504 for ; Tue, 5 Feb 2008 19:56:26 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2406596fgg.35 for ; Tue, 05 Feb 2008 11:56:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Pauk1JoTiXsAfNlDsw3EcbpIKh2GGBGLe7JdFZu/jOU=; b=BBfn+yu/aEmfEihTj8vSUmGjP+lAvObF0vA3lHtIB92ImoMGeoQ0jNJw33LNIWsYHuTHtaEFtwlAhvOAgzXAlGlQAVwQrpIyjJJ7Q84FxLL+oVOLPQz17mEftzVD7EeQZpTnXTfkSVjEKZ9QmRMq1hplD7uZvDY95mimDers/1s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=xj/1M0CedB6HM+OHKoUSFbozmrtPOcFtoL8ojp5OPtcr70OAcHrepdgfVoaXJb3qZcLWfx5w9ZKUWlig5v8DlhxVZryaWxmxPSzBygAv8DRPQEgGivbaJILNS0q+W0zAZebBYXOQXUmbEMCaDijJewk8T85LfsR9c8d8Lixz+Zg= Received: by 10.86.31.18 with SMTP id e18mr8186111fge.35.1202241386081; Tue, 05 Feb 2008 11:56:26 -0800 (PST) Received: by 10.86.28.19 with HTTP; Tue, 5 Feb 2008 11:56:26 -0800 (PST) Message-ID: <3bbf2fe10802051156p1cc6ea67t7938a60e306323ce@mail.gmail.com> Date: Tue, 5 Feb 2008 20:56:26 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yar Tikhiy" In-Reply-To: <20080205162217.GA56373@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3bbf2fe10801291411v302dd33at54ebe538397e8fac@mail.gmail.com> <3bbf2fe10801300707u3fd121c0k199605c2f0be6cbf@mail.gmail.com> <790a9fff0801301352xa91a69ci3f08488dfcfc982@mail.gmail.com> <3bbf2fe10801310243tddedfeckbc4c94be87f0a4ca@mail.gmail.com> <20080131130210.GA37090@comp.chem.msu.su> <3bbf2fe10801310504j486924bdm86e0436597a42b09@mail.gmail.com> <790a9fff0801312241s346068b6s40fcae71ebbf546@mail.gmail.com> <20080201145051.GE79881@comp.chem.msu.su> <3bbf2fe10802011041t28e419c9n5f0f6f34d6450184@mail.gmail.com> <20080205162217.GA56373@comp.chem.msu.su> X-Google-Sender-Auth: 01d297c946f46499 Cc: Kostik Belousov , Scot Hetzel , freebsd-current@freebsd.org, Doug Barton Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 05 Feb 2008 19:56:28 -0000 2008/2/5, Yar Tikhiy : > On Fri, Feb 01, 2008 at 07:41:58PM +0100, Attilio Rao wrote: > > 2008/2/1, Yar Tikhiy : > > [...] > > > > Fatal trap 12: page fault while in kernel mode > > > > > > cpuid = 0; apic id = 00 > > > > > > fault virtual address = 0xdeadc0ee > > > fault code = supervisor read, page not present > > > instruction pointer = 0x20:0xc07a0676 > > > stack pointer = 0x28:0xd614e9a0 > > > frame pointer = 0x28:0xd614e9a4 > > > > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > > > > = DPL 0, pres 1, def32 1, gran 1 > > > > > > processor eflags = resume, IOPL = 0 > > > > > > current process = 43 (umount) > > > [thread pid 43 tid 100052 ] > > > Stopped at isitmychild+0x6: movl 0x10(%eax),%ecx > > > db> panic: Assertion !mtx_owned(&w_mtx) failed at /usr/src/sys/kern/subr_witness > > > .c:959 > > > cpuid = 0 > > > Uptime: 2m14s > > > Cannot dump. No dump device defined. > > > Automatic reboot in 15 seconds - press a key on the console to abort > > > > It would be suitable for you to add DDB to your kernel config and see > > a backtrace for it? > > > DDB was there (my kernel was GENERIC + DEBUG_VFS_LOCKS,) but it > failed, too. Fortunately, I've managed to save a dump with the > whole call stack. Attached is the respective output from kgdb, > showing multiple failures including the one in NTFS. Currently it is DDB which let it fail in witness after memory corruption. But I'm more interested in the panic originator; so, as far as it is unusable, can you please remove DDB option and try to get the panic again? it should not give you the failing assertion without DDB. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein