From owner-freebsd-stable@freebsd.org Tue Feb 23 05:57:16 2016 Return-Path: Delivered-To: freebsd-stable@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 47E93AB1755 for ; Tue, 23 Feb 2016 05:57:16 +0000 (UTC) (envelope-from wac@google.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 294C81993 for ; Tue, 23 Feb 2016 05:57:16 +0000 (UTC) (envelope-from wac@google.com) Received: by mailman.ysv.freebsd.org (Postfix) id 26C25AB1754; Tue, 23 Feb 2016 05:57:16 +0000 (UTC) Delivered-To: stable@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 0D110AB1753 for ; Tue, 23 Feb 2016 05:57:16 +0000 (UTC) (envelope-from wac@google.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C54EF198E for ; Tue, 23 Feb 2016 05:57:15 +0000 (UTC) (envelope-from wac@google.com) Received: by mail-io0-x22b.google.com with SMTP id l127so202040884iof.3 for ; Mon, 22 Feb 2016 21:57:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=cEYjEdiFp+zsiOYJfH8K8L9LcVqZxATnyot76wnAcCM=; b=VOkmmQ+ma4A+vqeRArq3SZ0/yusj4OBU1iwdp7/1TzYWh1SAJTPM8uQbEb1/DAVbCM eG6YzhNelBHYvR2OQUO399LXa6RCa+Y8KZBUWP5AMDgX6lvnxqvk5BV7sryVii0La892 V9Mw2dOmHDI14XHA9IKvFLBuQwiCuomXDAidXt/0cFTC97w2U4qNYxiwIykOacrd30Z+ NOQ0dfb9WTEonjr3MPflhhAqsQWcexRJuVCXYtQ0QR3r+u77L3g6U4dfrpO7ZKO+HmR3 rkEhDVhUO92NJn+l9SAz6EqyDliBotAoqfRr4wznKhJ0o0s2tUirO1hq4Ca4wL/cfCC7 +pEQ== 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:from:date :message-id:subject:to:cc:content-type; bh=cEYjEdiFp+zsiOYJfH8K8L9LcVqZxATnyot76wnAcCM=; b=L4CP3JuYhY45bId4Ob2+6OZevSfZlSn6SBFmimAP5QqGdXNZrtbvO4Qy4AyT9f0ELs Cuu7Sx+U6nLGAIBauJsopzuHsH7K1B5Al8dXWLzwhLJBZUSDzxxfc8VMMQeD7VbqAe/l IpTzIH1nPcOr8C73f5x579ODGqvu3fqc+RKqB8R6WePTVocMuX5MnrzWyeQczjMd20MZ OTkk0WZUQG8I89DZWkWA45xpDp3ALbIusK0IWOpI0uDqM0ziM972Vip1PR3wJj5Ulm9g 1ZI3IsSboutes7hOdJgN3DTDagX1mLuCjwwlVNX0lujAtZapwASqgiu+Qye/rnJbQ1zL xMjQ== X-Gm-Message-State: AG10YOR1c0nV/6ajvsn8qB3mOc6IRke4jSRXSDYqJodk4DtmVuJoRGHyaxN1J1lnGv6WNBD16sOgMoyR6cGoBBm/ X-Received: by 10.107.32.144 with SMTP id g138mr30537200iog.33.1456207034755; Mon, 22 Feb 2016 21:57:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.91.225 with HTTP; Mon, 22 Feb 2016 21:56:55 -0800 (PST) In-Reply-To: <5c425565-5e1c-3c63-2b58-2e2e171856d1@FreeBSD.org> References: <5c425565-5e1c-3c63-2b58-2e2e171856d1@FreeBSD.org> From: Andy Carrel Date: Mon, 22 Feb 2016 21:56:55 -0800 Message-ID: Subject: Re: 10.3-BETA2 panic on boot with GCE NVMe To: koobs@freebsd.org Cc: stable@freebsd.org, "re@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 05:57:16 -0000 Filed as kern/207432. As noted there, it looks like ctrlr->ioq is null when nvme_ctrlr_intx_handler starts looking there. I get a feeling people don't usually use INTx for this driver though... On Mon, Feb 22, 2016 at 8:43 PM, Kubilay Kocak wrote: > On 23/02/2016 3:35 AM, Andy Carrel via freebsd-stable wrote: > > I've created a 10.3-BETA2 image for Google Compute Engine using swills' > > script and am getting a panic on boot when the VM is configured with > Local > > SSD as NVMe (--local-ssd interface="NVME"). This is a regression from > > 10.2-RELEASE which will boot successfully with an identical > configuration. > > > > """ > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x60 > > fault code = supervisor read data, page not present > > instruction pointer = 0x20:0xffffffff80e16019 > > stack pointer = 0x28:0xfffffe01bfff59c0 > > frame pointer = 0x28:0xfffffe01bfff59e0 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 12 (irq11: virtio_pci0+) > > [ thread pid 12 tid 100039 ] > > Stopped at nvme_ctrlr_intx_handler+0x39: cmpq $0,0x60(%rdi) > > db> bt > > Tracing pid 12 tid 100039 td 0xfffff8000422e000 > > nvme_ctrlr_intx_handler() at nvme_ctrlr_intx_handler+0x39/frame > > 0xfffffe01bfff59e0 > > intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame > > 0xfffffe01bfff5a20 > > ithread_loop() at ithread_loop+0x96/frame 0xfffffe01bfff5a70 > > fork_exit() at fork_exit+0x9a/frame 0xfffffe01bfff5ab0 > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01bfff5ab0 > > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > """ > > Hi Andy, > > Could you please create a Bugzilla issue for this. > > I've created a '10.3-BETA2' version so it can be tracked > > -- > Regards > > Kubilay > Bugmeister > > -- wac@google.com