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

[Yinghai Lu]

On Wed, Jul 16, 2008 at 6:21 PM, Jack Howarth <howarth@xxxxxxxxxxxxxxxxx> wrote:
> On Wed, Jul 16, 2008 at 05:49:39PM -0700, Yinghai Lu wrote:
>>
>> 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
>
> Yinghai,
>    Here is what I see with 'debug initcall_debug apci=verbose pci=routeirq'.
> Hopefully nothing important scrolled off the top of the screen (I've not found
> a higher resolution vga kernel option that works on my MacBook Pro yet).
>
> calling blk_ioc_init+0x0/0x2a
> initcall blk_ioc_init+0x0/0x2a returned 0 after 0 msecs
> calling genhd_device_init+0x0/0x55
> initcall genhd_device_init+0x0/0x55 returned 0 after 0 msecs
> calling fbmem_init+0x0/0x8a
> initcall fbmem_init+0x0/0x8a returned 0 after 0 msecs
> calling acpi_init+0x0/0x221
> ACPI: EC: EC description table is found, configuring boot EC
> ACPI: EC: non-query interrupt received, switching to interrupt mode
> ACPI: BIOS_IOS(Linux) query ignored via DMI
> ACPI: Interpreter enabled
> ACPI: (supports S0 S3 S4 S5)
> ACPI: Using IOAPIC for interrupt routing
> initcall acpi_init+0x0/0x221 returned 0 after 16 msecs
> calling acpi_scan_init+0x0/0x10a
> initcall acpi_scan_init+0x0/0x10a returned 0 after 35 msecs
> calling acpi_ec_init+0x0/0x61
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> ACPI: EC: driver started in interrupt mode
> initcall acpi_ec_init+0x0/0x61 returned 0 after 0 msecs
> calling acpi_pci_root+init+0x0/0x28
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> pci 0000:00:1f.0 :quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
> pci 0000:00.1f.0 :quirk: region 0500-053f claimed by ICH6 GPIO
>

ok, please out lspci -vvxxx under 2.6.25.10

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/