From owner-freebsd-fs@freebsd.org Mon Sep 4 17:03:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C457E11EAE for ; Mon, 4 Sep 2017 17:03:05 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B0297E741; Mon, 4 Sep 2017 17:03:04 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-122-71.dyn.iinet.net.au [106.68.122.71]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v84H2tQN076840 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 4 Sep 2017 10:02:58 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: Tips on remote debugging for filesystem code To: Aijaz Baig Cc: Gary Palmer , Bakul Shah , Kirk McKusick , freebsd-fs@freebsd.org References: <201708250251.v7P2pwcl029687@chez.mckusick.com> <20170827195428.49400124AE9F@mail.bitblocks.com> <20170828132647.GA60563@in-addr.com> From: Julian Elischer Message-ID: <4c7a54e4-a9fb-cf8b-fb1b-4a24e3cffc7c@freebsd.org> Date: Tue, 5 Sep 2017 01:02:49 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 17:03:05 -0000 On 4/9/17 9:55 pm, Aijaz Baig wrote: > Hi Julian > > Yes it just hangs. Yes it's not like it just hangs every time. It's > more intermittent. This time I was stepping through 'kern_openat', > really slowly as I am new to this, checking out the structures and > the likes and finally this hit when I was within vn_open_cred. So > yes the total time between attaching to the stub within the VM and > this happening was close to 3 hours but nonetheless I do face this > eventually > > is there something I should watch out for, I mean is there something > time bound in some way for any of this code? Is this the reason why > the VM becomes unresponsive if I step really slowly through the > stack trace? I haven't used it for  a year or so but I used to occasionally have a problem when doing things that would disable interrupts.  I found I had to put a breakpoint on ht eother side of them and 'c'ontinue over them or it would get stuck.. > > On Mon, Sep 4, 2017 at 10:25 AM, Julian Elischer > wrote: > > On 2/9/17 8:40 pm, Aijaz Baig wrote: >> I was finally able to deploy a FreeBSD-Current VM on Bhyve but >> even with that setup I face a similar issue >> >> For instance I put a breakpoint on 'ffs_read' and let the >> debugged VM continue but the control is neither returned to >> (k)gdb nor does the VM actually run. It appears hung. > are you sure it's not stopped at the breakpoint in ddb on the > console? > >> >> Is there something within the ffs/ufs code that I need to be >> aware of that it doesn't facilitate this sort of debugging? Or >> is it because Bhyve is being run on FreeBSD which is itself run >> on another hypervisor? Will that affect this? >> >> On Mon, Aug 28, 2017 at 7:03 PM, Aijaz Baig >> > wrote: >> >> HI Gary >> >> Just checked that. Indeed that was the case. In addition I >> was running FreeBSD on top of vmware hypervisor and had not >> allowed hardware acceleration features pass through to the >> FreeBSD VM. It is now working! Need to explore more on >> getting it to connect to GDB >> >> Perhaps you'll see a thread soon for it (Has anything >> worked perfectly for the first time ever?? ;) )! >> >> On Mon, Aug 28, 2017 at 6:56 PM, Gary Palmer >> > wrote: >> >> On Mon, Aug 28, 2017 at 01:12:09PM +0530, Aijaz Baig wrote: >> > Thanks a lot bakul. Will certain look into this >> > >> > Nevertheless I got hold of a PowerEdge 320 system >> which DOES have a POPCNT >> > instruction which shows support for V-x support via >> EPT but I still get the >> > same error there >> > >> > sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M >> -t tap0 -d guest.img -i >> > -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10 >> > Launching virtual machine "fbsd10" ... >> > vm_create: Device not configured >> > >> > dmesg: >> > vmx_init: processor does not support VMX operation >> > >> > cat /var/run/dmesg.boot | grep -i popcnt >> > >> > >> Features2=0xffba2203 >> > >> > >> Features2=0xffba2203 >> > >> > Any ideas? >> >> Hi, >> >> Check the BIOS for virtualisation or other related >> options.  Some BIOSes have >> the ability to turn those features off, even if the >> processor normally >> supports them >> >> Regards, >> >> Gary >> >> >> >> >> -- >> >> Best Regards, >> Aijaz Baig >> >> >> >> >> -- >> >> Best Regards, >> Aijaz Baig > > > > > > -- > > Best Regards, > Aijaz Baig