Date: Tue, 5 Aug 2014 07:29:14 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515] Message-ID: <20140805142914.GJ1228@albert.catwhisker.org> In-Reply-To: <20140804194759.GT1228@albert.catwhisker.org> References: <20140804194759.GT1228@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--VPk9As2FDNdbSgZX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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.) > .... By booting from the previously-built kernel: FreeBSD 11.0-CURRENT #1327 r269469M/269469:1100028: Sun Aug 3 06:16:24 PD= T 2014 root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i3= 86 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. I'm willing to try hacking at code (if necessary) to figure out what's wrong & fix it; I'll need some guidance, though. 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. Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --VPk9As2FDNdbSgZX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJT4Oo4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk73b4QAJmpYF+dr/ZVNdhSCuCh5AQx kfRqenOVVG90Rs2/79/EvHJoe9xDEbMKED8C0liwlckewFeIULbb3RfxKpUo7tRg 4zMjo2Dcws45wIBGgrUXes/uH07wQ+6jfOxkzC7ycZX/C+/0PfCy5kC3FwcXJtP7 rCfVCVDBIe3FLR7OSqXgELw82LEIy1ph078urE/8jaZLolmW2wNARsLEOt0+IOx3 qtW6Tw5ycuSADQP0bgqPA5WwORQFpEFd4K9FkZw1ewccDHePabLQAwo9NbSd9cCZ AD6s/jrRDQPp0mLn52iM57NF7b2HTx086ONhBy4naRO/3nrQG3IvE/4HVAQxyaK4 sLn5E7lhUQv9mpBNjByaEvY2mt4G7bdqifWFcQkqABr446I7xA4JE83ZP6m8wDIX n8M//jk7zMRdl3yV9f+ap+tEJk8NzQsqKJzGLWF1NnqTNYGHhmdWz7Bk9FFXAPd1 0vNiTgKoe/XRTFGU7BP6o0PoSNjF//PNZtEPvB/zBCJ9IsAy0YO/E7mrXvZSmiQu 7nzu6j2YxKSyE8GCOpmY2LLKmqy6Z2B5EeWyPLzGSR/B5ruUUVGZKwDcqVz72yLr WWfzDT/DQYnzzv5k/PZSocn9xZyPkaZJFcrSP5af4ioOzsKP26mFF3Cr2MAoLiJI auUkI4DYtxdgiz2w7snS =C9Yh -----END PGP SIGNATURE----- --VPk9As2FDNdbSgZX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140805142914.GJ1228>