Re: 2.6.26-rc9-git9 doesn't boot on Macintel

[Justin Mattock]

On Thu, Jul 17, 2008 at 12:49 AM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
> On Wed, Jul 16, 2008 at 5:40 PM, Jack Howarth <howarth@xxxxxxxxxxxxxxxxx> wrote:
>> On Wed, Jul 16, 2008 at 03:35:17PM -0700, Yinghai Lu wrote:
>>> please check latest linus tree.
>>>
>>> the commit could be related.
>>>
>>> commit c91d924e3af08d4f98eab6ebf81f2b8ce132448f
>>> Author: Bob Moore <robert.moore@xxxxxxxxx>
>>> Date:   Tue Jun 10 12:38:10 2008 +0800
>>>
>>>     ACPICA: Fix for hang on GPE method invocation
>>>
>>>     Fixes problem where the new method argument count validation mechanism
>>>     will enter an infinite loop when a GPE method is dispatched.
>>>     Problem fixed be removing the obsolete code that passes GPE block
>>>     information to the notify handler via the control method parameter pointer.
>>>
>>> YH
>>
>> Yinghai,
>>   The latest linus tree doesn't eliminate the hangs in 2.6.26 with your
>> mmconfig patch. Also, I've been unable to repeat the boot with pci=noacpi using
>> the mmconfig patch under 2.6.26. I've uploaded a dmesg file though from
>> the 2.6.25.10 kernel booted with apic=verbose in case that sheds any light
>> on these problems.
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=11087
>>
>> Also, I assume you meant earlier that is bad that with your mmconfig patch
>> that I only see 0 - 63 buses. Any idea how we might fix that (in case it
>> is related to the hang)?
>
> please boot with
> debug initcall_debug apic=verbose pci=routeirq?
>
> and try pci=nommconf
>
> I suspect that could be pci bridge is using 0xf0000000-0xf400000 too
> after Linus merge pci tree, please try to boot with
> pci=early_config_dump
> to see if it is true.
>
> please don't drop the cc list.
>
> YH
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

No I have not tried the .iso yet. I am more concerned with the PCI
option i.g. I'm using Direct, if I change to MMCONFIG will it cause
this same bug?
right now I'm occupied with drinking at the moment, but tomorrow I am curious
as to see if this occurs. keep in mind if I'm going to have to deal
with having a stuck system
this means I need to use a live cd to recover the system, the problem
is SELinux why: chrooting into the hardive and then compiling is going
to kind of mess
my policy a little bit(avc's)., but anyways easily resolved within a few hours.
regards;

-- 
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/