From owner-freebsd-current@FreeBSD.ORG Sat Dec 13 10:26:21 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E10929E; Sat, 13 Dec 2014 10:26:21 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF1D2769; Sat, 13 Dec 2014 10:26:20 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id sBDAQFB8019777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Dec 2014 12:26:15 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua sBDAQFB8019777 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id sBDAQEe3019776; Sat, 13 Dec 2014 12:26:14 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 13 Dec 2014 12:26:14 +0200 From: Konstantin Belousov To: Guido Falsi Subject: Re: LOR on head using virtualbox between intel kms and sound, with system lockup Message-ID: <20141213102614.GT2148@kib.kiev.ua> References: <54877A3D.7010706@madpilot.net> <20141210085245.GD97072@kib.kiev.ua> <54880B4E.3050902@madpilot.net> <548B8490.2010007@madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <548B8490.2010007@madpilot.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-current@freebsd.org, glebius@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-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: Sat, 13 Dec 2014 10:26:21 -0000 On Sat, Dec 13, 2014 at 01:13:04AM +0100, Guido Falsi wrote: > On 12/10/14 09:58, Guido Falsi wrote: > > On 12/10/14 09:52, Konstantin Belousov wrote: > >> On Tue, Dec 09, 2014 at 11:39:57PM +0100, Guido Falsi wrote: > >> > [...] > >>> --- trap 0xc, tip = 0xffffffff8056834d, rsp = 0xfffffe022ed8f6b0, rbp = > >>> 0xfffffe022ed8f6e0 --- > >>> sbappendstream_locked() at sbappendstream_locked+0x2d/frame > >>> 0xfffffe022ed8f6e0 > >>> sbappendstream() at sbappendstream+0x3c/frame 0xfffffe022ed8f710 > >>> tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfffffe022ed8f790 > >>> sosend_generic() at sosend_generic+0x40b/frame 0xfffffe022ed8f850 > >>> kern_sendit() at kern_sendit+0x19e/frame 0xfffffe022ed8f900 > >>> sendit() at sendit+0x129/frame 0xfffffe022ed8f950 > >>> sys_sendto() at sys_sendto+0x4d/frame 0xfffffe022ed8f9a0 > >>> amd64_syscall() at amd64_syscall+0x211/frame 0xfffffe022ed8fab0 > >>> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe022ed8fab0 > >>> --- syscall (133, FreeBSD ELF64, sys_sendto), rip = 0x80126c5a, rsp = > >>> 0x7fffdf1e9df8, rbp = 0x7fffdf1e9e40 --- > > >> This is plain fault, in network stack, in the tcp send path. It has > >> nothing to do with sound at all, and the LOR between DRM device lock and > >> send buffer socket lock is a consequence of drm activated when panic > >> occured in the locked region. > >> > >> That said, first thing to do when you experience panic with vbox or fuse > >> modules loaded, is to remove the modules and see if it happens still. > >> If it is persistent, contact net@. > >> > > > > I see. Problem with removing the virtualbox module is I have been able > > to trigger the panic only by starting the VBox VM. I have no idea how to > > trigger it some other way. > > > > I'll try though. > > > > Thanks for the insight! > > > > Quick followup, for any interested party, I isolated the commit in > r274712, reverting this one the problem disappears. > > If anyone has some ideas about this please reply to me or followup in > bug 195822 on bugzilla. I suspect that the issue is vbox and not the revision itself. Anyway, your best route is to ask Gleb.