Date: Wed, 25 Sep 2019 08:02:12 -0400 From: Alexander Motin <mav@FreeBSD.org> To: current@freebsd.org Subject: Re: "panic: sched_pickcpu: Failed to find a cpu" after r352636 -> r352671 Message-ID: <17ed84c1-daa8-8a01-d9ce-2b433f4228ae@FreeBSD.org> In-Reply-To: <20190925105430.GW1108@albert.catwhisker.org> References: <20190925105430.GW1108@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the notice, it was a wrong assertion. Fixed. I'm sorry. On 25.09.2019 06:54, David Wolfskill wrote: > ... > SMP: AP CPU #3 Launched! > cpu3 AP: > ID: 0x00000003 VER: 0x01060015 LDR: 0x00000008 DFR: 0x00000000 x2APIC: 1 > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000011ff > timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 > cmci: 0x000100f2 > SMP: AP CPU #6 Launched! > cpu6 AP: > ID: 0x00000006 VER: 0x01060015 LDR: 0x00000040 DFR: 0x00000000 x2APIC: 1 > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000011ff > timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 > cmci: 0x000100f2 > panic: sched_pickcpu: Failed to find a cpu. > cpuid = 0 > time = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff82550830 > vpanic() at vpanic+0x19d/frame 0xffffffff82550880 > panic() at panic+0x43/frame 0xffffffff825508e0 > sched_pickcpu() at sched_pickcpu+0x4c1/frame 0xffffffff82550990 > sched_add() at sched_add+0x6e/frame 0xffffffff825509d0 > gtaskqueue_start_threads() at gtaskqueue_start_threads+0x124/frame 0xffffffff82550a70 > taskqgroup_cpu_create() at taskqgroup_cpu_create+0x135/frame 0xffffffff82550ab0 > taskqgroup_adjust() at taskqgroup_adjust+0x1ad/frame 0xffffffff82550b20 > mi_startup() at mi_startup+0x210/frame 0xffffffff82550b70 > btext() at btext+0x2c > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> > > This is an Intel amd64 on a 4-core, 2 threads/core machine; I note > that src/sys/kern/sched_ule.c was modified in this update: > > ------------------------------------------------------------------------ > r352658 | mav | 2019-09-24 13:01:20 -0700 (Tue, 24 Sep 2019) | 24 lines > > Fix/improve interrupt threads scheduling. > .... > > A copy of "dmesg.boot" from a verbose boot from yesterday for the > machine may be found at > http://www.catwhisker.org/~david/FreeBSD/history/freebeast.13_dmesg.txt > > I'm about to find out if my laptop (which shares the above salient > characteristics, and is being updated in parallel) exhibits similar > symptoms. > > Peace, > david > -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17ed84c1-daa8-8a01-d9ce-2b433f4228ae>