From owner-freebsd-current@FreeBSD.ORG Tue Aug 5 20:02:31 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C61174E for ; Tue, 5 Aug 2014 20:02:31 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7A6A2FDA for ; Tue, 5 Aug 2014 20:02:30 +0000 (UTC) Received: from [192.168.1.75] (75-48-77-17.lightspeed.cncrca.sbcglobal.net [75.48.77.17]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4327EB913; Tue, 5 Aug 2014 16:02:28 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515] From: John Baldwin In-Reply-To: <20140805142914.GJ1228@albert.catwhisker.org> Date: Tue, 5 Aug 2014 13:02:25 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140804194759.GT1228@albert.catwhisker.org> <20140805142914.GJ1228@albert.catwhisker.org> To: David Wolfskill X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 05 Aug 2014 16:02:30 -0400 (EDT) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 05 Aug 2014 20:02:31 -0000 On Aug 5, 2014, at 7:29 AM, David Wolfskill = wrote: > On Mon, Aug 04, 2014 at 12:47:59PM -0700, David Wolfskill wrote: >> ... >> I was unable to get a crash dump, and I only recorded the offsets in = the >> backtrace (no arguments; sorry -- I was expecting the build machine = to >> allow me to investigate on a machine with a serial console): >>=20 >> ... >> SMP: AP CPU #1 Launched! >> panic: aatpic_assign_cpu: bad cookie >> cpuid=3D0 >> atpic_assign_cpu(...) at atpic_assign_cpu+0x1a/frame 0xc2820d0c >> intr_shuffle_irqs(...) at intr_shuffle_irqs+0x97/frame 0xc2820d30 >> mi_startup(...) at mi_startup+0xe7/frame 0xc2820d58 >> begin(...) at begin+0x2c >> db>=20 >>=20 >> So... what can I do to help figure out what went wrong? As noted, I >> have no serial console on the laptop, and while I have captured crash >> dumps in the past, I'm guessing that at the point the above happens, = the >> machine has yet to obtain a clue about where it might put a dump if = one >> were created. >>=20 >> (No problems with stable/9 (@r269499) or stable/10 (@r269498) on the >> same hardware.) >> .... >=20 > By booting from the previously-built kernel: >=20 > FreeBSD 11.0-CURRENT #1327 r269469M/269469:1100028: Sun Aug 3 = 06:16:24 PDT 2014 = root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 >=20 > I was able to update sources to r269580 & rebuild (successfully -- = both > userland & kernel); the resulting kernel, however, exhibited the same > symptoms -- "panic: aatpic_assign_cpu: bad cookie", with a similar (if > not identical -- I couldn't refer to the previous one while I was > observing the current panic) backtrace. >=20 > I'm willing to try hacking at code (if necessary) to figure out what's > wrong & fix it; I'll need some guidance, though. >=20 > Given that my build machine did not exhibit the symptoms, and given = the > references to atpic, it may be relevant to point out that the machine > where I see the panic is a Dell Precision M4400 laptop. My guess is that the recent Xen changes tickled something. However, can = you capture a verbose dmesg from your working kernel? --=20 John Baldwin