From owner-freebsd-current@freebsd.org Sat May 28 12:11:48 2016 Return-Path: Delivered-To: freebsd-current@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 56966B4C8A1 for ; Sat, 28 May 2016 12:11:48 +0000 (UTC) (envelope-from gljennjohn@gmail.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 35C42123D for ; Sat, 28 May 2016 12:11:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 351CFB4C89E; Sat, 28 May 2016 12:11:48 +0000 (UTC) Delivered-To: current@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 34C5FB4C89D for ; Sat, 28 May 2016 12:11:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 BE0B51238; Sat, 28 May 2016 12:11:47 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id a136so24887891wme.0; Sat, 28 May 2016 05:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=VsRLn1TW1IFZy+nxjZmxMC8ftRnwoGOZYstMFDTdlGc=; b=cbHvbVPcdWLbTODjZ2PJJXE9m5QtNP1aJpPQ1vgUaSJGWqW/KK+/95vmzFtvMLMD6T bE6ufzmHtFbhIVW35Ni2q9r7BuzQ1COJ9+e8lAmsPq+EiY+y0vInVpr/clCMXTc3aObm U6SVlJ78pAfsPY8y2LbgNy/4f6G7y2WDaic+0WfQaoXM//cctDqiBgh39/kTxgyErRgD e4WouxcqhEj9YKaWijLIClmZZsndlP7j/d7MD/uEyPjDnRV2P8M7RWd63ESpZfI11Dhm f0Ls2QNIcG0oq/iZVD9aKIE7MAtRsV4ZnPMjOoyzIAsWVeyg1B726shjRrFLgPRVX5AV F7WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=VsRLn1TW1IFZy+nxjZmxMC8ftRnwoGOZYstMFDTdlGc=; b=fvY55dsMV19V/PvoGnrQ4C+5ZbKkuFMntuZQ7HYg8Sg3e90hizXJgp7NaH4YmktZMY E8z9l34034eBAx1LEeGSmgWhmYAuCvis3AJFtaw6u1pf9lIF+244C9L4ZQ4ZSgYEpSQN XhlqGfZBmY/oRpWKzjSwikH0Il9eUvoufwS/2ujzBncGFQIFkFT8GJoVD1bI//Mvbv74 F2UWSLUBaap7wTl4HpHj2sKemsEKXioIB9jsFcxsfC2Tl5YZIlZgRTqg2POGLfM9+Y2v AKNEOlVjz8xgceUJ4SdHT3UkbaKldlc0of02tR6N0U/wPx/YXISXkHaExOnoebwx4gqi jyhw== X-Gm-Message-State: ALyK8tIpIi3S7FYV2N60wWIw2XDz+R+46+LQGg9pMeW0oQ2H1c9Iv2tl8kzxsBON+2Bi0A== X-Received: by 10.28.46.83 with SMTP id u80mr2924082wmu.35.1464437506325; Sat, 28 May 2016 05:11:46 -0700 (PDT) Received: from ernst.home (p578E2F4B.dip0.t-ipconnect.de. [87.142.47.75]) by smtp.gmail.com with ESMTPSA id x124sm13354511wmg.24.2016.05.28.05.11.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 May 2016 05:11:45 -0700 (PDT) Date: Sat, 28 May 2016 14:11:41 +0200 From: Gary Jennejohn To: John Baldwin Cc: current@freebsd.org Subject: Re: EARLY_AP_STARTUP hangs during boot Message-ID: <20160528141141.232185a9@ernst.home> In-Reply-To: <20160527095005.0e0dc1be@ernst.home> References: <20160516122242.39249a54@ernst.home> <3960771.pvLV2Nd9Tc@ralph.baldwin.cx> <20160517184741.599597b4@ernst.home> <2245981.CzRHAP1AJo@ralph.baldwin.cx> <20160527095005.0e0dc1be@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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, 28 May 2016 12:11:48 -0000 On Fri, 27 May 2016 09:50:05 +0200 Gary Jennejohn wrote: > On Thu, 26 May 2016 16:54:35 -0700 > John Baldwin wrote: > > > On Tuesday, May 17, 2016 06:47:41 PM Gary Jennejohn wrote: > > > On Mon, 16 May 2016 10:54:19 -0700 > > > John Baldwin wrote: > > > > > > > On Monday, May 16, 2016 12:22:42 PM Gary Jennejohn wrote: > > > > > I tried out EARLY_AP_STARTUP, but the kernel hangs and I can't > > > > > break into DDB. > > > > > > > > > > I did a verbose boot and the last lines I see are related to routing > > > > > MSI-X to various local APIC vectors. I copied the last few lines and > > > > > they look like this: > > > > > > > > > > msi: routing MSI-X IRQ 256 to local APIC 2 vector 48 > > > > > msi: routing MSI-X IRQ 257 to local APIC 3 vector 48 > > > > > msi: routing MSI-X IRQ 258 to local APIC 4 vector 48 > > > > > msi: routing MSI-X IRQ 256 to local APIC 0 vector 49 > > > ^^^^^^^ Assigning > > > > > > > > > > I tried disabling msi and msix in /boot/loader.conf, but the settings > > > > > were ignored (probabaly too early). > > > > > > > > No, those settings are not too early. However, the routing to different > > > > CPUs now happens earlier than it used to. What is the line before the > > > > MSI lines? You can take a picture with your phone/camera if that's simplest. > > > > > > > > > > Here a few lines before the MSI routing happens: > > > > > > hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 > > > hpet0: vendor 0x4353, rev 0x1, 14318180 Hz, 3 timers, legacy route > > > hpet0: t0 : irqs 0x00c0ff (0), MSI, periodic > > > hpet0: t1 : irqs 0x00c0ff (0), MSI, periodic > > > hpet0: t2 : irqs 0x00c0ff (0), MSI, periodic > > > Timecounter "HPET" frequency 14318180 Hz quality 950 > > > > The assigning message means it is in the loop using > > bus_bind_intr() to setup per-CPU timers. Can you please try > > setting 'hint.hpet.0.per_cpu=0' at the loader prompt to see if > > disabling the use of per-CPU timers allows you to boot? > > > > Something has changed since the last time I generated a kernel with > this option. > > Now I get a NULL-pointer dereference in the kernel, doesn't matter > whether I set the hint or not. > OK, now that the startup has been fixed, I tried setting the hint at the loader prompt, but the kenel hangs in exactly the same place as before. I actually booted twice to make certain I hadn't made a typo when setting the hint. -- Gary Jennejohn