From owner-freebsd-current@FreeBSD.ORG Sat Dec 13 11:03:51 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 3C241739; Sat, 13 Dec 2014 11:03:51 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B843CA6E; Sat, 13 Dec 2014 11:03:50 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3k05Zd120RzZrR; Sat, 13 Dec 2014 12:03:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1418468615; x=1420283016; bh=7LD4W3uMW+4lqQyjC35pJLBYXePPN1gy4kRIF9Ic448=; b= kHN1elioM88ExzJzTVxMcahQb1tq5cOmhxqCZKhwDHTfBYemHCNnYyTd/JGjhX4d CHjuGjA378pEZMHTZGKtsEgcO37bC0zFr/WTLVXAXTrqFrbUl0G4N/qYqHsOzMhU XRy9dVqw3A9rjAZHyflfHZZdjcoMkTW7Jge9ROYR//s= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id WpCPzY7lDZf8; Sat, 13 Dec 2014 12:03:35 +0100 (CET) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Sat, 13 Dec 2014 12:03:35 +0100 (CET) Message-ID: <548C1D06.9060900@madpilot.net> Date: Sat, 13 Dec 2014 12:03:34 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: LOR on head using virtualbox between intel kms and sound, with system lockup References: <54877A3D.7010706@madpilot.net> <20141210085245.GD97072@kib.kiev.ua> <54880B4E.3050902@madpilot.net> <548B8490.2010007@madpilot.net> <20141213102614.GT2148@kib.kiev.ua> In-Reply-To: <20141213102614.GT2148@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 11:03:51 -0000 On 12/13/14 11:26, Konstantin Belousov wrote: > 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. > It's quite possible. Just to clarify, I did not mean that commit is wrong or anything like that. In fact I'm unable to tell not having a clear understanding of that code. I just thought this bit of information could help the diagnosis. > Anyway, your best route is to ask Gleb. > I did. He sad he's taking a look. -- Guido Falsi