From owner-freebsd-current@FreeBSD.ORG Sun Jun 17 04:35:56 2012 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 BB3FE1065670; Sun, 17 Jun 2012 04:35:56 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id C58328FC08; Sun, 17 Jun 2012 04:35:55 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward11.mail.yandex.net (Yandex) with ESMTP id 69A25E81AE4; Sun, 17 Jun 2012 08:35:54 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1339907754; bh=cP4idb7F6FhY8tYH8S0n0opHNYzz9BPHRcSYNetrMAE=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=rUhXI/ESLdjtReE8tUiKqUOnlptxkke8isW+6hjGKvr1mU9fXKkGTKRB06cQ4Ryh7 +BXzvLbCoU1ABRq74eXklnw9eVB3p4kUmz7ukCrUnF1due64b2hGdIRPIUeMZd8bjO 5RirJyLzgUERNS41XX4VYA/9ugYYPYOdz3JUXUog= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 44AAE16A0524; Sun, 17 Jun 2012 08:35:54 +0400 (MSK) Received: from unknown (unknown [178.76.224.133]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Zrfeioa5-ZrfqRhq9; Sun, 17 Jun 2012 08:35:53 +0400 X-Yandex-Rcpt-Suid: jhb@freebsd.org X-Yandex-Rcpt-Suid: freebsd-current@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1339907754; bh=cP4idb7F6FhY8tYH8S0n0opHNYzz9BPHRcSYNetrMAE=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=cDDqw0zdLdUja0/bx4yK4falS8CkMwDjWTiM41w+ZzLs0/w5lvqbKZLRLgW3VRu1w cAvge5KY2jIMAILVxhckg9Ue9v85s9ztYIMi2Q8w1Ghn3zm6pVSHkl7+a60Jp0iQcB PgD863dXJ1jUugeFgofzRHSeiTbVaG+4EDQPWmTg= Message-ID: <4FDD5E78.3060904@yandex.ru> Date: Sun, 17 Jun 2012 08:35:04 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120616 Thunderbird/13.0 MIME-Version: 1.0 To: John Baldwin References: <4FD1B365.2010209@yandex.ru> <4FD1B60E.2060803@yandex.ru> <201206081045.15763.jhb@freebsd.org> In-Reply-To: <201206081045.15763.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 17 Jun 2012 04:46:36 +0000 Cc: freebsd-current@freebsd.org Subject: Re: lock order reversal in sys/kern/vfs_mount.c 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: Sun, 17 Jun 2012 04:35:57 -0000 John Baldwin wrote on 08.06.2012 18:45: > On Friday, June 08, 2012 4:21:34 am Ruslan Mahmatkhanov wrote: >> Ruslan Mahmatkhanov wrote on 08.06.2012 12:10: >>> Good day, >>> >>> After updating to yesterdays -current, I got this on boot: >>> >>> lock order reversal: >>> 1st 0xfffffe0007b04c38 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1254 >>> 2nd 0xfffffe0007ed9478 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2158 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >>> kdb_backtrace() at kdb_backtrace+0x37 >>> _witness_debugger() at _witness_debugger+0x2c >>> witness_checkorder() at witness_checkorder+0x853 >>> __lockmgr_args() at __lockmgr_args+0x113a >>> vop_stdlock() at vop_stdlock+0x39 >>> VOP_LOCK1_APV() at VOP_LOCK1_APV+0xbf >>> _vn_lock() at _vn_lock+0x47 >>> vget() at vget+0x7b >>> devfs_allocv() at devfs_allocv+0x13f >>> devfs_root() at devfs_root+0x4d >>> dounmount() at dounmount+0x45c >>> vfs_unmountall() at vfs_unmountall+0x4c >>> kern_reboot() at kern_reboot+0x84b >>> sys_reboot() at sys_reboot+0x68 >>> amd64_syscall() at amd64_syscall+0x2e0 >>> Xfast_syscall() at Xfast_syscall+0xf7 >>> --- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x40ebbc, rsp = >>> 0x7fffffffd6c8, rbp = 0x65 --- >>> >>> Reverting to old kernel (that was built about a week ago) helped to >>> avoid this. Any thoughts? >> >> And this one comes up with the recent update too: >> >> driver bug: Unable to set devclass (class: acpi_sysresource devname: >> (unknown)) >> driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) >> cpu0: on acpi0 >> driver bug: Unable to set devclass (class: acpi_sysresource devname: >> (unknown)) >> cpu1: on acpi0 >> driver bug: Unable to set devclass (class: acpi_sysresource devname: >> (unknown)) >> cpu2: on acpi0 >> driver bug: Unable to set devclass (class: acpi_sysresource devname: >> (unknown)) >> cpu3: on acpi0 >> >> What the additional info should I supply to understand what's wrong? >> Here is my full dmesg; http://people.freebsd.org/~rm/dmesg.txt > > Is this a verbose boot? Also, can you try this to get more details in > the log message: > Sorry for delay. This particular panic had triggered by intel video driver (x11-drivers/xf86-video-intel v 2.19.0). After I rebuild it with new kernel, all is going fine. The panic appeared after GDM login, and I was able to catch some driver-related errors in xorg log. Thanks John. -- Regards, Ruslan Tinderboxing kills... the drives.