Am So, den 17.04.2005 schrieb Marlon Bastida um 6:31: > Im using FC3 with lastest kernel: > 2.6.11-1.14 > I have a PCI card (sound blaster live) and an onboard AC'97. > My motherboard is a INTEL D845GRG. I have a GF4 MSI MX 440 too. With > drivers 7167 working well. > My mboard have 2 options for ACPI, s1 state and s3 state. I tested > with both but I get these messages again on dmesg. > On Xp professional I didn't get any errors... When did Windows® ever print out verbose and meaningful messages? > I would like to know, How can I correct theses errors from dmesg > output, related to ACPI and PNP?? > > Linux version 2.6.11-1.14_FC3 (bhcompile@xxxxxxxxxxxxxxxxxxxxx) (gcc > version 3.4.3 20050227 (Red Hat 3.4.3-22)) #1 Thu Apr 7 19:23:49 EDT > 2005 [ ... ] > PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2 > PCI: Using configuration type 1 > mtrr: v2.0 (20020519) > ACPI: Subsystem revision 20050211 > ACPI: Interpreter enabled > ACPI: Using PIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (00:00) > PCI: Probing PCI hardware (bus 00) > PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 > PCI: Transparent bridge - 0000:00:1e.0 > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] > ACPI: Power Resource [URP1] (off) > ACPI: Power Resource [FDDP] (off) > ACPI: Power Resource [LPTP] (off) > 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) > ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. > ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) > ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI init > ACPI-1138: *** Error: Method execution failed [\MCTH] (Node > dff3ee40), AE_AML_BUFFER_LIMIT > ACPI-1138: *** Error: Method execution failed [\OSFL] (Node > dff3ee60), AE_AML_BUFFER_LIMIT > ACPI-1138: *** Error: Method execution failed [\_SB_.SYSM._CRS] > (Node c14de800), AE_AML_BUFFER_LIMIT > ACPI-0158: *** Error: Method execution failed [\_SB_.SYSM._CRS] > (Node c14de800), AE_AML_BUFFER_LIMIT > pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0c01 > pnp: PnP ACPI: found 12 devices > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: Using ACPI for IRQ routing > ** PCI interrupts are no longer routed automatically. If this > ** causes a device to stop working, it is probably because the > ** driver failed to call pci_enable_device(). As a temporary > ** workaround, the "pci=routeirq" argument restores the old > ** behavior. If this argument makes the device work again, > ** please email the output of "lspci" to bjorn.helgaas@xxxxxx > ** so I can fix the driver. You tested what it says above? > ACPI-1138: *** Error: Method execution failed [\MCTH] (Node > dff3ee40), AE_AML_BUFFER_LIMIT > ACPI-1138: *** Error: Method execution failed [\OSFL] (Node > dff3ee60), AE_AML_BUFFER_LIMIT > ACPI-1138: *** Error: Method execution failed [\_SB_.SYSM._CRS] > (Node c14de800), AE_AML_BUFFER_LIMIT > ACPI-0158: *** Error: Method execution failed [\_SB_.SYSM._CRS] > (Node c14de800), AE_AML_BUFFER_LIMIT > pnp: 00:0b: ioport range 0x400-0x47f could not be reserved > pnp: 00:0b: ioport range 0x680-0x6ff has been reserved > pnp: 00:0b: ioport range 0x480-0x4bf has been reserved > apm: BIOS not found. You see any misbehaviour of your system besides those messages? Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.14_FC2smp Serendipity 17:00:22 up 5 days, 13:40, load average: 0.19, 0.14, 0.10
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
