regression on HP zx1 platform from ACPI autoload modules patches

[Doug Chapman]

I am seeing a regression on the HP ia64 zx1 platforms when using
a .config with CONFIG_IA64_HP_ZX1=y.  Oddly it works OK with
CONFIG_IA64_GENERIC=y.


During bootup it panics with:

Kernel panic - not syncing: Unable to find SBA IOMMU: Try a generic or DIG kernel

I can provide the full console output if that is helpful.  Also, please let
me know if there is any other data I can provide that would be helpful.

Using git bisect I have narrowed it down to these 2 commits.  These commits
cannot be built separately as they appear to have code that depends on each
other.


commit 29b71a1ca74491fab9fed09e9d835d840d042690
Author: Thomas Renninger <trenn@xxxxxxx>
Date:   Mon Jul 23 14:43:51 2007 +0200

    ACPI: autoload modules - Create ACPI alias interface
    
    Modify modpost (file2alias.c) to add acpi*:XYZ0001: alias in modules.alias
    like:
    grep acpi /lib/modules/2.6.22-rc4-default/modules.alias
    alias acpi*:SNY5001:* sony_laptop
    alias acpi*:SNY6001:* sony_laptop
    for e.g. the sony_laptop module.
    This module matches against all ACPI devices with a HID or CID of SNY5001
    or SNY6001
    
    Export an uevent and modalias sysfs file containing the string:
    [MODALIAS=]acpi:PNP0C0C:
    additional CIDs are concatenated at the end.
    
    Signed-off-by: Thomas Renninger <trenn@xxxxxxx>
    Signed-off-by: Kay Sievers <kay.sievers@xxxxxxxx>
    Signed-off-by: Len Brown <len.brown@xxxxxxxxx>


Author: Thomas Renninger <trenn@xxxxxxx>
Date:   Mon Jul 23 14:43:32 2007 +0200

    ACPI: autoload modules - ACPICA modifications
    
    Define standardized HIDs - Rename current acpi_device_id to acpica_device_id
    
    Signed-off-by: Thomas Renninger <trenn@xxxxxxx>
    Signed-off-by: Len Brown <len.brown@xxxxxxxxx>



- Doug


-
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/