Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Aug 2014 20:49:49 -0700
From:      John Baldwin <jhb@FreeBSD.org>
To:        Michael Butler <imb@protected-networks.net>
Cc:        royger@FreeBSD.org, current@freebsd.org
Subject:   Re: panic: aatpic_assign_cpu: bad cookie [Was: Build machine OK; laptop panics @r269515]
Message-ID:  <8B832384-C1CC-4622-BA67-7447ECE317C9@FreeBSD.org>
In-Reply-To: <53E14CD1.20308@protected-networks.net>
References:  <20140804194759.GT1228@albert.catwhisker.org> <20140805142914.GJ1228@albert.catwhisker.org> <C248C4AE-65AB-406A-A523-F7D7FAA8FBBE@FreeBSD.org> <53E1450D.5090708@protected-networks.net> <53E14CD1.20308@protected-networks.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Aug 5, 2014, at 2:29 PM, Michael Butler <imb@protected-networks.net> =
wrote:

> On 08/05/14 16:56, Michael Butler wrote:
>> On 08/05/14 16:02, John Baldwin wrote:
>>=20
>>> My guess is that the recent Xen changes tickled something.
>>=20
>> I can confirm this on a kernel which is otherwise up to date ..
>>=20
>> FreeBSD toshi.auburn.protected-networks.net 11.0-CURRENT FreeBSD
>> 11.0-CURRENT #2 r269608M: Tue Aug  5 16:48:12 EDT 2014
>>=20
>> I backed out all of SVN r269507 through r269515.
>>=20
>> Now working ..
>=20
> [ .. snip .. ]
>=20
>> Now to see if it's related to the other machine's disk woes (it's a
>> single-core device),
>=20
> And it fixes the inability to probe disks on my single-core machine =
:-)

It looks like the MADT code to probe the I/O APICs isn't working so it's =
trying to fall back to using the ATPIC while using SMP (which doesn't =
work).  I know it's a pain on a laptop, but if it is at all possible to =
capture either a verbose or non-verbose dmesg that would really help =
narrow it down.

Also, if anyone can try reverting just the MADT-related changes in the =
recent Xen changes to see if you can narrow down which exact one =
triggers the panic that would be really helpful.

--=20
John Baldwin









Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8B832384-C1CC-4622-BA67-7447ECE317C9>