panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]

John Baldwin jhb at
Tue Aug 5 20:02:31 UTC 2014

On Aug 5, 2014, at 7:29 AM, David Wolfskill <david at> 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):
>> ...
>> SMP: AP CPU #1 Launched!
>> panic: aatpic_assign_cpu: bad cookie
>> cpuid=0
>> 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> 
>> 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.
>> (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 PDT 2014     root at  i386
> 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.

My guess is that the recent Xen changes tickled something.  However, can you capture a verbose dmesg from your working kernel?

John Baldwin

More information about the freebsd-current mailing list