From owner-freebsd-current@freebsd.org Thu Aug 31 08:32:06 2017 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 EA9AEE18FFD for ; Thu, 31 Aug 2017 08:32:06 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::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 7D6B86E808 for ; Thu, 31 Aug 2017 08:32:06 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id u26so4134777wma.5 for ; Thu, 31 Aug 2017 01:32:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=/R91uHVpBA/oJ3F8nH0VxdDF8YV1pqOiklgAX8iHKs8=; b=sVBPEWUxw51BSK0CcIJLbCyGU50TegFJ5WJt9Z7gSlW8hLchW3S8RJkm+qDo0sWoDy QtXfPxvWAC/nBkTo/45FzUKEoFQKUBSLIyd9+c9Eh5Wj/CuKGQsFVv3aWCTPl0mwgiRz kvbzHzrfWnRDlxCN8kgAb2rUtpi9UngjtTqslsv//vSoLisKRGEmEHzqNWQZP+kXvXkl DyOGaTZ763X1Gn7JXoIDvEBOdZcpRtWV7kM5tpl7jkZ5vXXz0Yoefn51zFPbaL+JSBwO hNy3aXkuUSfoVWirJe7kEGehS3ooZJ2lilcrYHV8nRWZ/kfUBH63zrPygs2HVGMDIWzL +gdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=/R91uHVpBA/oJ3F8nH0VxdDF8YV1pqOiklgAX8iHKs8=; b=ErIDDwrMWxBpEsIfwxBFP5iGh2b973JRC9dNEoyB++lHhFn6DVkshBMKu+HqLKbBNc 833Tbi0eriv5VQjxjdMIRItwk3RltDLoLMJFm+/LyMlMspMP0U4zcWlhRRZwILlCCzuG 4joP8GWZVqb+9Z2pN0wgBbDDpzcRSCb8OmEhAa9QnX6w95HEYJ1shavQZ8YCEdNyZU1D SU9mnfohTJscd6pr17rQRz+bjenJ6WwVN27t0HExkszU6pd9Q7J3ZYSUJUsyUlI/uS8g 2ryDfIyT02WWK/4OYSM6Jts5bVIvobIOrc76GSxeAIFexvxDGaC9N2lRFZu/8jQuTr2C 8rQw== X-Gm-Message-State: AHYfb5imp96fU+5g0+gcHz0XF0wdQM8qC+UNdE40M+t0ab8xG4JEMfIh 3kqz44hwZnkbckUc X-Received: by 10.28.156.146 with SMTP id f140mr2670431wme.32.1504168324886; Thu, 31 Aug 2017 01:32:04 -0700 (PDT) Received: from ernst.home (p4FCA62DB.dip0.t-ipconnect.de. [79.202.98.219]) by smtp.gmail.com with ESMTPSA id k10sm3109583wre.38.2017.08.31.01.32.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 Aug 2017 01:32:03 -0700 (PDT) Date: Thu, 31 Aug 2017 10:31:57 +0200 From: Gary Jennejohn To: Kevin Bowling Cc: freebsd-current@freebsd.org Subject: Re: !EARLY_AP_STARTUP and -CURRENT Message-ID: <20170831103157.0eecbcba@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.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.23 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: Thu, 31 Aug 2017 08:32:07 -0000 On Wed, 30 Aug 2017 16:54:07 -0700 Kevin Bowling wrote: > I'm dealing with a shit sandwich right now where the mps(4) or cam_da > reorders drives on a few thousand legacy MBR machines I have (and I > can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have > regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right > quick so I can take a more leisurely approach to fixing mps(4) boot > probe correctly (freebsd-scsi@ has that thread). > > With WITNESS and !EARLY_AP_STARTUP I hit an assert in sched_setpreempt > in kern/sched_ule.c 100% of the time. Here are a couple invocations, > with oddness around a different CPU holding the curthread lock but > somehow a different AP is runnable in the function: > You might consider using SCHED_4BSD until this problem can be resolved. I tried booting a system with WITNESS and !EARLY_AP_STARTUP, but using SCHED_4BSD, and it at least reaches multi-user mode. Since it isn't clear under what circumstances your problem arises I didn't pursue it any further, but this approach may at least allow you to continue on. > Tracing pid 11 tid 100020 td 0xfffff80128cd1560 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e653dcc10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e653dcc90 > panic() at panic+0x43/frame 0xfffffe3e653dccf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e653dcd00 > sched_add() at sched_add+0x152/frame 0xfffffe3e653dcd40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e653dcd80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e653dcdc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e653dce70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e653dcef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e653dcf30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e653dcf60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e653dcf90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e653dcff0 > > > db> show thread 0xfffff80128cd1560 > Thread 100020 at 0xfffff80128cd1560: > proc (pid 11): 0xfffff80128cb5000 > name: idle: cpu17 > stack: 0xfffffe3e5cd88000-0xfffffe3e5cd8bfff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cca000 (tid 100017, pid 11, "idle: cpu14") > > > db> bt > Tracing pid 11 tid 100021 td 0xfffff80128cd2000 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e655e4c10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e655e4c90 > panic() at panic+0x43/frame 0xfffffe3e655e4cf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e655e4d00 > sched_add() at sched_add+0x152/frame 0xfffffe3e655e4d40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e655e4d80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e655e4dc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e655e4e70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e655e4ef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e655e4f30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e655e4f60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e655e4f90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e655e4ff0 > db> show thread 0xfffff80128cd2000 > Thread 100021 at 0xfffff80128cd2000: > proc (pid 11): 0xfffff80128cb6000 > name: idle: cpu18 > stack: 0xfffffe3e5cf17000-0xfffffe3e5cf1afff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cdb560 (tid 100028, pid 11, "idle: cpu25") > > Regards, > Kevin > _______________________________________________ > 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" -- Gary Jennejohn