On Saturday 28 April 2007 09:57, JJ JJ wrote: > >If you just run dmesg, and scroll down a bit you should see references to > >acpi, along with some suggestions as there are problems with it. If you > > can post the relevant acpi bits from that it might be helpfull. > > > >Nigel. > > Hello Nigel, > here's some lines from my term. window as you suggested: > > ACPI: RSDP (v002 ACPIAM ) @ > 0x00000000000f6cf0 > ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ > 0x000000007fff0100 > ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ > 0x000000007fff0281 > ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ > 0x000000007fff0380 > ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ > 0x000000007ffff040 > ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ > 0x000000007fff3990 > ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ > 0x000000007fff39d0 > ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ > 0x0000000000000000 > ACPI: Local APIC address 0xfee00000 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) > ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: IRQ0 used by override. > ACPI: IRQ2 used by override. > ACPI: IRQ9 used by override. > Setting APIC routing to xen > Using ACPI (MADT) for SMP configuration information > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI init > pnp: PnP ACPI: found 14 devices > This is pretty much all I could find running the command acpi related. I > hope there's some useful info. > Thanks again! > JJ Hi JJ. There don't appear to be any errors showing there, but when I had my FC5 shutdown problem, someone asked if I was using an SMP kernel, as that could be causing the problem, and unless I've got it wrong, you are. uname -r will show your kernel version. Out of interest this is what dmesg shows on FC5 for a kernel that is not using acpi=force. ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: Disabling ACPI support and Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to ffffd000 (017f7000) And again on FC5 with a different kernel that boots using acpi=force. IO/L-APIC disabled because your old system seems to be old overwrite with "apic" ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: acpi=force override ACPI: PM-Timer IO Port: 0x4008 and Kernel command line: ro root=LABEL=/1 acpi=force mapped APIC to ffffd000 (017f7000) If it is a problem with a XEN/SMP kernel, I don't know the fix, but hopefully someone will come in on the thread, and may be able to help. Nigel.
