Re: ACPI broke going from 8 to 9

On Sat, Dec 31, 2011 at 3:31 PM, Jeremy Chadwick
<freebsd_at_jdc.parodius.com> wrote:
> On Sat, Dec 31, 2011 at 04:17:16PM -0700, Dan Allen wrote:
>> On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote:
>>
>> > Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and
>> > try booting the new kernel. See if this works.
>>
>> It worked!  No hang, power button works.  Nice.  I hope this experimental option stays in.
>>
>> Thank you everyone for your help.  Happy New Years!
>
> This option isn't documented **anywhere** in the entire src tree.  It's
> purely #ifdef all over.
>
> The code in question was committed 7 months ago.  It was MFC'd to
> RELENG_8 6 months ago.  Here's the HEAD commit message:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci.c#rev1.420
>
> The RELENG_8 MFC is revision 1.386.2.15.
>
> The committer is jhb_at_, with mav_at_ being the individual who tested it, so
> I imagine either of these folks will have some excellent insights as to
> what's causing Dan's problem.  I'm CC'ing them both directly on this
> thread.
>
> In the meantime: Dan, when you say in your original mail, "I just
> upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9", can you
> please provide uname -a output from the system when it was running
> RELENG_8?  I'm looking specifically for the exact time when the kernel
> was built, because there may have been fixes (that broke things for you)
> between the above commit and present-day RELENG_8 (I have not examined
> all commits).

    It's going to be the feature that's going to cause headaches
post-9.0-RELEASE based on my observations of several mailing list
posts and the fact that 9.0 isn't actually RELEASEd yet (people have
run into issues with acpi, atkbdc, mfi, and usb so far, but that's
probably not everything).
    If it could be made into a runtime tunable, that would be awesome,
but that would require changes to driver structures and methods. With
a little pointer aliasing and tunable guard sprinkling it wouldn't be
hard to solve -- but it's still work.
    In the meantime, could someone please commit PR # 163748 to note
what NEW_PCIB is and MFC it to RELENG_9 and could we consider
disabling NEW_PCIB on i386 and pc98 until all the issues are ironed
out?
Thanks,
-Garrett