Bug reports requested - acpi

[Roman Kurakin]

Nate Lawson wrote:

> Roman Kurakin wrote:
>
>> Nate Lawson wrote:
>>
>>> Roman Kurakin wrote:
>>>
>>>> You want it:
>>>>   
>>>> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2624308+0+/usr/local/www/db/text/2004/freebsd-current/20040822.freebsd-current 
>>>>
>>>>
>>>> It seems that problems I have due to acpi code update between 
>>>> 2004-08-13 and 2004-08-14.
>>>> I'll check tomorrow that I didn't mix up sources.
>>>>
>>>> I've just applied changes in vm code that was made while 13-14, and 
>>>> after
>>>> restart I was able to log in to buggy system. So vm is not the 
>>>> place of problems.
>>>> The only unapplied patch is a acpi changes.
>>>
>>> Does booting without ACPI fix the problem?
>>
>> No. Only safe mode. As I understand it also turn off MP.
>
>
> Safe mode disables the APIC in addition to ACPI.  Since disabling ACPI 
> alone doesn't fix your problem, I doubt I can be much more help right 
> now since I'm not an APIC expert.  Why don't you try booting with APIC 
> disabled but ACPI still active and see how things work?
>
> set hint.apic.0.disabled="1" at the loader prompt

I was unaware of all that safe mode turns off, and than I last time 
check this I ovelooked
that apic is also disabled. It seems that problem with APIC.

But could you tell me how changes in ACPICA affect APIC code?

rik

>> Again, if I set break point at install_ap_tramp this function start 
>> to work correctly.
>> (No trap at write access). And panic occures from other place (And I 
>> unable to fix
>> it by debugging ;-)) in mp_machdep.c.
>>
>> Now I'll try to understan what part of that ACPI commit I could leave 
>> and which to
>> backout to minimize search area.
>
> -Nate
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"