From owner-freebsd-xen@FreeBSD.ORG Tue Dec 2 22:10:34 2014 Return-Path: Delivered-To: freebsd-xen@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 3E5D7E47 for ; Tue, 2 Dec 2014 22:10:34 +0000 (UTC) Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F30D8B7D for ; Tue, 2 Dec 2014 22:10:33 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id b13so11138963qcw.23 for ; Tue, 02 Dec 2014 14:10:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/pZd1CoCZHcxpINydBKRCtPF8HZC3LkXY3ZwAxXE6ec=; b=hgU4H8+7aUxfFsNg6Hkacs9i0/Q3Ng9KxXV1NcgjcqShWSm0f1jHm76vF0bkOlIq0I i+WadT4yWrFEFGSBaruh6ZpMpUXwHVx7ys07vm6Jv+TmCPm5H4nX+CqLV7K52gmRXcqS M1GNfOIo4QOmofSELP9e0nCAp6QgOK8m0RGZjLrX27GgqqM7knADYV5h7bL/jsnauEZd wuJxpFL1m/pRHEFHHnnO/ykeEKiANFa4ITLTb17k/WEp/ytnxPxbQIFvYDe6/2Jv8Mu2 uZ9TDTz+Q3pVDHKiafLQ8xxXNP8pnlfLPsVk+R0clc/UGzVUB/TIBprrXxn5klce/eUY iQcA== X-Gm-Message-State: ALoCoQlhohUggojL6anXNGT0CWkxVPcc891dtD7ltj8cTAWYAVw5qa5tzUrMAFWe6G7h0vNOpNwG MIME-Version: 1.0 X-Received: by 10.224.121.142 with SMTP id h14mr2293152qar.80.1417558232512; Tue, 02 Dec 2014 14:10:32 -0800 (PST) Received: by 10.140.39.48 with HTTP; Tue, 2 Dec 2014 14:10:32 -0800 (PST) In-Reply-To: References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> Date: Tue, 2 Dec 2014 15:10:32 -0700 Message-ID: Subject: Re: Attempting to Get Xen FreeBSD Dom0 working From: Will Andrews To: "David P. Discher" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 22:10:34 -0000 On Tue, Dec 2, 2014 at 2:26 PM, David P. Discher wrote: > Can you or someone point me to how to get the line numbers ? Since this = is panic-ing before swap on/dumpon =E2=80=A6 I=E2=80=99m not sure out to ge= t the dump and load into kgdb with the symbols. My guess is that I need to= use remote debugging to do this. You can just run 'kgdb' when you boot up and type in 'l *name+off', for instance, from your previous email: > db> bt > Tracing pid 0 tid 100000 td 0xffffffff8180bbf0 > AcpiNsWalkNamespace() at AcpiNsWalkNamespace+0x31/frame 0xffffffff8= 2322940 > AcpiWalkNamespace() at AcpiWalkNamespace+0xa8/frame 0xffffffff82322= 9a0 > acpi_pci_attach() at acpi_pci_attach+0x154/frame 0xffffffff823229f0 On my system this yields: sol# kgdb [...] #0 sched_switch (td=3D0xffffffff81645e70, newtd=3D, flags=3D) at /home/will/dev/git/freebsd/sys/kern/sched_ule.c:1945 1945 cpuid =3D PCPU_GET(cpuid); (kgdb) l *AcpiNsWalkNamespace+0x31 0xffffffff80335cc1 is in AcpiNsWalkNamespace (/home/will/dev/git/freebsd/sys/contrib/dev/acpica/components/namespace/nsw= alk.c:91). [...] (kgdb) l *AcpiWalkNamespace+0xa8 0xffffffff80336268 is in AcpiWalkNamespace (/home/will/dev/git/freebsd/sys/contrib/dev/acpica/components/namespace/nsx= feval.c:665). [...] (kgdb) l *acpi_pci_attach+0x154 0xffffffff80366924 is in acpi_pci_attach (/home/will/dev/git/freebsd/sys/dev/acpica/acpi_pci.c:313). [...] It would probably also be useful to report the source revision you built. --Will.