From owner-freebsd-current@freebsd.org Sat Mar 24 14:11:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB2A9F4C6A5 for ; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) (envelope-from wlosh@bsdimp.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 5D7E96DEA7 for ; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1716EF4C6A4; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E74CBF4C6A1 for ; Sat, 24 Mar 2018 14:11:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 855196DEA2 for ; Sat, 24 Mar 2018 14:11:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x244.google.com with SMTP id r18so18325388ioa.1 for ; Sat, 24 Mar 2018 07:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r3l+MLFkpDQGUJ1dpCGInJjOIn4k1Wj6OMFVOuStju4=; b=kZ5ZVHfUEcGOsM674xmp9+YJsTLTKqtYKPxGu6RqOY7MugkGNmqbPv3iCMYUr8faXy 0UDHqmCvFCXndiYsg/SUqmKrNm5zLyTMHuYmRwI7FbzrgCE9MhgshjDPLj0fhrIDHUye uI79Z5qjPv2Trx+bUAj2K/pXVlbszc68UgoQH6P54MPXSg9tIpnq4Fsuis3Mu/PVCrJc iu3L+iCTaKSRniDo3DfQhVtGAUkJj6ZkPohiSTTpxN0trNVDdDutl4nXxwWlee4ERJN0 u52H48aVUvxpTnjMfkAf+DWF4iWsENX2ct/prMIEeuzAsiP+XLe224YHLJa8BoZOl7FJ IdVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r3l+MLFkpDQGUJ1dpCGInJjOIn4k1Wj6OMFVOuStju4=; b=NyK4Ie8RFhF0Rf9z8U1q68BhX5ayXPQNxAP9xUBNMNDhtgnk/1ESOE3OB6CI/+gQoH MbrVn3FZbgpIZ7gC52lzlC+JPKVaYVc01qHaU68LlzCCkyZD80x4u2yaMdCEMnNkAZ97 FpSEDeyv3v6q/ALaoo9bjMyO1VglcjAWVbJyM/Qpz0p/zG2mPYXTAuRf13FGf2mBzPG3 KC7jPrMBABptQixqMwO1MqPBWL45ZcBme+cl8HBFUaL1TyAKF+EKLj72r9dukrkkuZFC ttvRTqwR7H+8zOOmtzqrinsZVTpRl9YmmVv2zVmib+CWCc72LoKKKKJuptWdQQ2Kttip ZnEw== X-Gm-Message-State: AElRT7ET8UloTUFejGAcw9TpR029vnYQmlgbX2vV8qOVOo5x3kjyHdBh SO5Df/lCAAaGugsLaJn5Hz2faYtpPazjA1JT9LFmqw== X-Google-Smtp-Source: AG47ELtOOpnClnfp+DNPBOj5fgdXYQs/0y9ynbKhl1MgfVhuwD7vxl5GNbszFfNVe3dUwiea7DPYb6uvbGmMZANs8ag= X-Received: by 10.107.144.11 with SMTP id s11mr34165866iod.37.1521900674658; Sat, 24 Mar 2018 07:11:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sat, 24 Mar 2018 07:11:13 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180324035653.GA3411@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> From: Warner Losh Date: Sat, 24 Mar 2018 08:11:13 -0600 X-Google-Sender-Auth: -tuyySFsQ25ud7xCpEVX1ZTR__M Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 24 Mar 2018 14:11:17 -0000 That lock has been there for a long, long time (like 5 or 6 major releases)... It's surprising that it's causing issues now. Can you bisect versions to find when this starts happening? Warner On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly wrote: > Hi all, > > For reasons that still escape me, I haven't been able to get a kernel dump > to debug, sorry. > > Just thought that I'd generate a fairly low-quality report, to see if > anyone has some ideas. > > The last kernel that I have that booted OK (and I'm now running) is: > FreeBSD Zen.ac-r.nu 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r331064M: Sat > Mar 17 07:54:51 AEDT 2018 root@Zen:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > The machine is a: > CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class > CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > Features=0x178bfbff APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > Kernels built from head as of a couple of hours ago get through launching > the other CPUs and then stops somewhere in random, apparently: > > SMP: AP CPU #2 Launched! > Timecounter "TSC-low" frequency 1497223020 Hz quality 1000 > random: entpanic: mtx_lock() of spin mutex (null) @ > /usr/src/sys/kern/subr_bus.c:617 > cpuid = 0 > time = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00004507a0 > vpanic() at vpanic+0x18d/frame 0xfffffe0000450800 > doadump () at doadump/frame 0xfffffe0000450880 > __mtx_lock_flags() at __mtx_lock_flags+0x163/frame 0xfffffe00004508d0 > devctl_queue_data_f() at devctl_queue_data_f+0x6a/frame 0xfffffe0000450900 > g_dev_taste() at g_dev_taste+0x370/frame 0xfffffe0000450a10 > g_new_provider_event() at g_new_provider_event+0xfa/frame > 0xfffffe0000450a30 > g_run_events() at g_run_events+0x151/frame 0xfffffe0000450a70 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000450ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000450ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 14 tid 100052 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> dump > Cannot dump: no dump device specified. > db> > > Now dumping worked fine the last time the kernel panicked: I have > dumpdev=AUTO in rc.conf and I have swap on nvd0p3 (first) and > /dev/zvol/root/swap > (second, larger than the first.) > > Root on the nvd0p2 is ZFS, and ther's a four-drive raidZ with user > directories and what-not on them, and another ZFS on an external USB drive > that I use > for backups, unmounted. > > In the new kernels, we clearly aren't even getting as far as finding the > hubs and controllers, let alone the drives. > > I've attached dmesg.boot from the last boot from last week's good kernel. > (While briefly in yoyo mode I turned the SMT back on, so now there are 16 > cores > instead of the eight mentioned in the crash dump. Didn't help, but I > haven't turned it back off yet.) > > Cheers, > > Andrew > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >