Re: core 6 issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you for the clarifications, Nigel. Here's a list of what I got running the command:

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])
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.
Using ACPI (MADT) for SMP configuration information
ACPI: Core revision 20060707
ACPI: bus type pci registered
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
PCI: Using ACPI for IRQ routing
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707]
ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 17 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:02:0b.1[B] -> GSI 18 (level, low) -> IRQ 18
ACPI: PCI Interrupt 0000:02:00.0[D] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:02:00.1[D] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:02:0b.2[C] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 18 (level, low) -> IRQ 18
ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]

this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended.
Oh, well....



On Friday 27 April 2007 22:31, JJ JJ wrote:
> Hey Aaron,
> sorry I saw your message only now. I tried Nigel's tips, and still no go.
> So, at the grub menu I have to digit this line:
> dmesg |grep ACPI
> am I correct?
> I also noticed that at the end, I get this message:
> acpi: pci interrupt for device 0000:02:03.0 disabled
> My guess is that if I enable it, this P.O.S. should work, but  how do I
> enable it?
> Thanks again!!
> JJ

You run dmesg from the CLI (Konsole/Terminal) once you have booted up. if you just run dmesg from the CLI you get all of the bootup stuff displayed in the terminal. Running dmesg | grep acpi limits the output to what just applies to
acpi.

This is a horrible problem, and seems to appear with more recent kernels, and just on some hardware. My original kernel that was installed from the cdroms for FC5 still shutsdown ok, but kernels 2.6.17. and later have this shutdown
problem, and in my case on FC5 acpi=force added to the kernel lines
in /boot/grub/grub.conf seems to fix the problem.

Hope we can fix this for you, as it's an inconvenience having to push the
button to shutdown.

Nigel.

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

_________________________________________________________________
Interest Rates NEAR 39yr LOWS! $430,000 Mortgage for $1,299/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-19132&moid=14888


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux