ACPI Error

Hello!
I have the laptop HP Pavilion 15-n062sr with Intel HD Graphics 4400 and Nvidia GeForce 740M
After the boot I have in `dmesg`:
[ 20.741621] ACPI Error: Method parse/execution failed [\_SB_.PCI0.RP05.PEGP.DD02._BCL] (Node ffff8802568629b0), AE_NOT_FOUND (20131218/psparse-536)
[ 20.741759] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:19/LNXVIDEO:00/input/input11
[ 20.778625] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 28.739296] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
I think bacause of this I can't to enable Bumblebee
Can you help me? Thank you!

Able to resolve this problem
Error (Source: acpiec, Event: 1, time: 9:04:09)
\Device\ACPIEC: The embedded controller (EC) hardware didn't respond within the timeout period. This may indicate an error in the EC hardware or firmware, or possibly a poorly designed BIOS which accesses the EC in an unsafe manner. The EC driver will retry the failed transaction if possible.
SPTD driver used in alcohol 52% was the source of the probe. removing the sptd driver stopped this message. but the other acpi error message is still happening.

Similar Messages

MacBook Air running Bootcamp getting ACPI errors in Windows

We have a number of MacBook Air 13" mid-2014 A1466 models running Bootcamp with Windows 7 64 bit Enterprise.
(We image them with Windows & Bootcamp, no Mac OS X partition)
We are using latest Bootcamp 5.1.5640 drivers
They work fine for most applications.
We are regularly getting ACPI errors
The error in Windows System log is
Source: ACPI
Description: The embedded controller (EC) did not respond within the specified timeoutperiod. This may indicate there is an error in the EC hardware or firmware that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.
The error we are seeing is when a user is logged into a Windows domain it should pass the Windows password to other applications like Outlook, Lync, etc. Instead, on these Macs, they regularly prompt for the Windows password to re-connect to the source. We don't get this issue with normal Windows PCs.
Also booting has a slight delay of around 10 seconds before Windows begins loading. Don't this delay with older MacBook Airs.
Have looked at repairing Bootcamp drivers. EFI & SMC looks up to date, had to use Mac boot USB to check this info.

VikingBrad wrote:
Just re-reading my post and I was unclear. Yes we do use EFI and boot directly into Windows.
This is good to know.
The Windows partition is joined to an AD domain and logs in fine with AD credentials.
The only problem being that when we open Outlook or Lync or other apps that require AD authentication the user is prompted for their AD credentials.
We have cleared Credential Manager in Windows, tried different users with no success. It works with older MacBooks and Windows PC. Seems to just be these latest MacBook Air 2014 models with the issue. After user re-enters AD credentials they can connect to Outlook, etc.
This may be a bit off-topic, but Macs do not "officially" support Enterprise versions of Windows. Can I suggest using a test 2014 MBA, installing W7/W8 64-bit, and configuring for AD authentication and testing. Are there any known DNS issues on this Macs? In all the applications which do not function correctly, does the username show up correctly populated, when prompted for login?
The only error we see in Event log is the ACPI error so suspect it is related. But we have latest Bootcamp drivers from Apple perhaps we are off track.
If the user successfully enters credentials when prompted for say, Outlook, and the computer is made to sleep or hibernate, is the connection to Outlook/Lync still up if the timeout for sessions (if any) has not yet expired and the computer is woken up?
It may also be worthwhile to look for requests being made for authentication before the applications prompt the user for credentials.

10.4.9 Upgrade: Fails. Reboot results in Kernel Panic ACPI error

I am upgrading 11 MacBook Pros 10.4.6 to 10.4.9. Becasue they are all on a slow Wifi I am using the manual updates via a thumb drive.
So far 2 out of 6 have failed the install process. One gave me a general error. I tried to re-run the program but when I did the font for the drop down menu turned into all boxes with capital As inside them. In both cases when I have rebooted I have gotten a Kernel Panic ACPI error. I have tried all the Kernel Panic tricks mentioned in the 10.4.9 threads. I am now reinstalling on the two machines.
1 of 6 did the install just fine but is now stopped on the "Starting Mac OS X..." screen with a full blue bar.
Does anyone have any idea what is wrong?

You may find the following useful:
From a recent article at MacFixit:
Mac OS X 10.4.9 Special Report: Update procedure recommendation
First, make a full backup of your current Mac OS X installation -- preferably a clone ( try SuperDuper! or Carbon Copy Cloner). If something goes wrong, or you experience a major incompatibility after updating, the backup will prove invaluable.
Next, if you are the cautious type, run a disk repair on the volume targeted for installation. You can use an n alternative startup drive or your Mac OS X installation disc. If you are starting up from your Mac OS X install disc, put the disc in your optical drive and restart holding down the "C" key. After your system starts up and you've selected your language, go to the "Utilties" menu and select "Disk Utility." Use the "Repair Disk" function. After disk repairs are complete, restart from your normal startup drive and continue.
Avoid performing any other operations (in Mac OS X or third-party applications) while the update process is occurring.
Performing other tasks during the update process potentiates various issues, including problems with prebinding (which is happening during the "Optimizing the system" phase of the update process) and others that can occur when files are being replaced by the update are also being read/written by the currently logged in user. You should not only refrain from launching applications or working with files during the update process, but also from putting the system to sleep, disconnecting/connecting devices, and other potentially interruptive actions.
In addition, before installing the update, make sure all Apple-installed applications and utilities are in their original locations. Moving one of these applications to a different location on your hard drive can lead to an incomplete update. Also, disconnect any FireWire/USB devices before applying Mac OS X 10.4.9 (except for your startup drive, if it is FireWire or USB, and your keyboard/mouse), then re-connect the devices one by one (checking for issues created by any particular device) after the update process is complete and the system has restarted. Also, note that the first restart after applying Mac OS X 10.4.9 may be abnormally long. Subsequent restarts should take place at normal speed.
And this further article from MacFixit is also very important:
When a Mac OS X update won't install with "Volume does not meet requirements for this update" message
The error message "Volume does not meet requirements for this update" may appear when attempting to install a Mac OS X updater or a full release from disc. Generally the problem falls into one of the following categories:
Make sure you are using the right updater (Server vs. client) There are usually a few varieties of the same Mac OS X update version. Make sure that you are not trying to install the Intel client build on a PowerPC-based Mac, or the Server build on a Mac OS X client system.
Although we generally recommend using the standalone Mac OS X updaters rather than Software Update, the latter method will generally correctly identify the copy of Mac OS X applicable to your current system state.
Retail vs. shipped-with-system (build numbers) Different Macs ship with different builds of Mac OS X, and one build may not be compatible with a different system. The build that ships with a MacBook Core 2 Duo, for instance, may not properly install on a Mac Pro. Hence you may receive the "Volume does not meet requirements for this update" message when mixing and matching systems and discs.
Some retail copies of Mac OS X 10.4.x may also be unable to install on some systems that require newer builds.
In addition, it appears that while some builds will install on specific systems, those systems will then refuse to accept subsequent updates. To ensure compatibility, inspect the following matrices:
• Mac OS: Versions, builds included with Intel-based Macs
http://docs.info.apple.com/article.html?artnum=303315
• Mac OS: Versions, builds included with PowerPC Macs (since 1998)
http://docs.info.apple.com/article.html?artnum=25517
and note that you should not use a Mac OS version earlier than the one included with the computer.
Combo vs. Delta Remember that delta Mac OS X updaters can only update systems version-to-version, e.g. Mac OS X 10.4.8 to Mac OS X 10.4.9. Combo updaters can bring any version within the scope of a major release (Panther, Tiger, etc.) up-to-date, e.g. Mac OS X 10.4.3 to Mac OS X 10.4.9.
Attempting to run a delta update on anything other than the directly precedent version may result in the "Volume does not meet requirements for this update" message.

Event Viewer ACPI error MBP mid09

Hi, I have installed Win 7 on my MBP 5.5 mid 2009 and although its running well I am getting an error message in event viewer saying:
Error
25/09/2014 00:00:32
ACPI
13
None
something about the embedded controller failed to start in a reasonable time. Would anyone with the same mac please check their event logs to see if they have this error please?
I had this and a HAL error under Win 7 ultimate x64 (used this as a test os) so I installed Win 7 Pro from a Genuine Disc (I do not condone piracy) and I am getting the ACPI error (only after all the drivers were installed, the error message didnt show prior to boot camp 4 install). So before I spend £100 on a Genuine Windows disc (I already purchased Windows 8 at £106 but it seems apple dont support it on this mac :-(...) I'd like to know if its a failing logic board or driver related.
Thanks in advance
Darren

I have been running OSX for around 1 hour and then I rebooted into windows 7, loaded the event logs immediately and found the ACPI error had been recorded precisely 1 hour before windows had booted, I am wondering if this could be a bug between Mac/Windows time feature. after more restarts the ACPI isn't being recorded and other events times are correct.
edit:
I have just disabled the Synchronise with internet time feature in windows. I'll keep a look out.

PnP ACPI error at the time instalation.

Hi i am using Enterprise-R5-U4-Server-x86_64, while installing on IBM X3400 M3 model its shows following error
PnP ACPI - Method_name_CRS failure for PnPP0a03 at the time of booting and machine is rebooting after one hours.
Please tell me the solution to it.

Sir,
I try to disable ACPI=off at boot promt ,but the macine get restart the afterone hours.
The kernel version installed is 2.6.18.164.el5xen
and i also trace the error in /var/log /message ,following message i found
testdb kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
testdb kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
testdb kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
testdb kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
testdb kernel: ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24])
testdb kernel: IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
testdb kernel: Setting APIC routing to xen
testdb kernel: Using ACPI (MADT) for SMP configuration information
testdb kernel: Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
testdb kernel: Built 1 zonelists. Total pages: 448326
testdb kernel: Kernel command line: ro root=LABEL=/ rhgb quiet
testdb kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
testdb kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: GSI 17 sharing vector 0xA0 and IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: GSI 18 sharing vector 0xA8 and IRQ 18
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 18
testdb kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 18
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
testdb kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
testdb kernel: ACPI: Processor [CPU1] (supports 8 throttling states)
testdb kernel: Real Time Clock Driver v1.12ac
testdb kernel: Non-volatile memory driver v1.2
testdb kernel: Linux agpgart interface v0.101 (c) Dave Jones
testdb kernel: brd: module loaded
testdb kernel: Xen virtual console successfully installed as ttyS0
testdb kernel: Event-channel device installed.
testdb kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
testdb kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
testdb kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1
testdb kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 19
testdb kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
testdb kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
testdb kernel: uhci_hcd 0000:00:1d.0: irq 19, io base 0x00001800
testdb kernel: usb usb2: configuration #1 chosen from 1 choice
testdb kernel: hub 2-0:1.0: USB hub found
testdb kernel: hub 2-0:1.0: 2 ports detected
testdb kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 23 (level, low) -> IRQ 19
testdb kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
testdb kernel: ACPI: Power Button (FF) [PWRF]
testdb kernel: ACPI: Power Button (CM) [PWRB]
testdb avahi-daemon[2779]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
testdb kernel: Dazed and confused, but trying to continue
testdb kernel: Do you have a strange power saving mode enabled?
testdb syslogd 1.4.1: restart.
testdb kernel: klogd 1.4.1, log source = /proc/kmsg started.
testdb kernel: Bootdata ok (command line is ro root=LABEL=/ rhgb quiet)
testdb kernel: Linux version 2.6.18-164.el5xen ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Thu Sep 3 04:41:04 EDT 2009
testdb kernel: BIOS-provided physical RAM map:
testdb kernel: Xen: 0000000000000000 - 000000006d746000 (usable)
testdb kernel: DMI present.
testdb kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
testdb kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
testdb kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
testdb kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
testdb kernel: ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24])
testdb kernel: IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
testdb kernel: Setting APIC routing to xen
testdb kernel: Using ACPI (MADT) for SMP configuration information
testdb kernel: Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
testdb kernel: Built 1 zonelists. Total pages: 448326
testdb kernel: Kernel command line: ro root=LABEL=/ rhgb quiet
testdb kernel: Initializing CPU#0
testdb kernel: PID hash table entries: 4096 (order: 12, 32768 bytes)
testdb kernel: Xen reported: 1861.949 MHz processor.
testdb kernel: Console: colour VGA+ 80x25
testdb kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
testdb kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
testdb kernel: Software IO TLB enabled:
testdb kernel: Aperture: 2 megabytes
testdb kernel: Kernel range: 0xffff880000df8000 - 0xffff880000ff8000
testdb kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
testdb kernel: Memory: 1735168k/1793304k available (2490k kernel code, 49284k reserved, 1388k data, 184k init)
testdb kernel: Calibrating delay using timer specific routine.. 4657.90 BogoMIPS (lpj=9315810)
testdb kernel: Security Framework v1.0.0 initialized
testdb kernel: SELinux: Initializing.
Jul 25 04:08:08 testdb kernel: (SMP-)alternatives turned off
testdb kernel: ACPI: Core revision 20060707
testdb kernel: Brought up 2 CPUs
testdb kernel: Initializing CPU#1
testdb kernel: migration_cost=19
testdb kernel: checking if image is initramfs... it is
testdb kernel: Grant table initialized
testdb kernel: NET: Registered protocol family 16
testdb kernel: ACPI: bus type pci registered
testdb kernel: PCI: Not using MMCONFIG.
testdb kernel: PCI: Using configuration type 1
testdb kernel: ACPI: Interpreter enabled
testdb kernel: ACPI: Using IOAPIC for interrupt routing
testdb kernel: ACPI: No dock devices found.
testdb kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
testdb kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
testdb kernel: PCI: Transparent bridge - 0000:00:1e.0
testdb kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 *6 7 10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *9
testdb kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
testdb kernel: pnp: PnP ACPI init
testdb kernel: ACPI Error (exregion-0165): Could not map memory at 00000000FEC80000, size 100 [20060707]
testdb kernel: ACPI Exception (evregion-0424): AE_NO_MEMORY, Returned by Handler for [SystemMemory] [20060707]
testdb kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._CRS] (Node ffff88000002d670), AE_NO_MEMORY
Jul 25 04:08:08 testdb kernel: ACPI Error (uteval-0212): Method execution failed [\_SB_.PCI0._CRS] (Node ffff88000002d670), AE_NO_MEMORY
testdb kernel: pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0a03
testdb kernel: pnp: PnP ACPI: found 10 devices
testdb kernel: xen_mem: Initialising balloon driver.
testdb kernel: usbcore: registered new driver usbfs
testdb kernel: usbcore: registered new driver hub
testdb kernel: PCI: Using ACPI for IRQ routing
testdb kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
testdb kernel: NetLabel: Initializing
testdb kernel: NetLabel: domain hash size = 128
testdb kernel: PREFETCH window 0x00000000d0000000-0x00000000d7ffffff
testdb kernel: GSI 16 sharing vector 0x98 and IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: GSI 17 sharing vector 0xA0 and IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: GSI 18 sharing vector 0xA8 and IRQ 18
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 18
testdb kernel: NET: Registered protocol family 2
testdb kernel: IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
testdb kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
testdb kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 18
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 16
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: assign_interrupt_mode Found MSI capability
testdb kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
testdb kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
testdb kernel: ACPI: Processor [CPU1] (supports 8 throttling states)
testdb kernel: Real Time Clock Driver v1.12ac
testdb kernel: Non-volatile memory driver v1.2
testdb kernel: Linux agpgart interface v0.101 (c) Dave Jones
testdb kernel: brd: module loaded
testdb kernel: Xen virtual console successfully installed as ttyS0
kernel: Event-channel device installed.
kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1
kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 17
kernel: ESB2: chipset revision 9
kernel: ESB2: not 100% native mode: will probe irqs later
kernel: ide0: BM-DMA at 0x18c0-0x18c7, BIOS settings: hda:DMA, hdb:pio
kernel: hda: HL-DT-STDVD-RAM GSA-H55N, ATAPI CD/DVD-ROM drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: ide-floppy driver 0.99.newide
kernel: usbcore: registered new driver hiddev
kernel: usbcore: registered new driver usbhid
kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
testdb kernel: PNP: PS/2 Controller [PNP0303:KBC0] at 0x60,0x64 irq 1
testdb kernel: PNP: PS/2 controller doesn't have AUX irq; using default 12
testdb kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
testdb kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
testdb kernel: mice: PS/2 mouse device common for all mice
testdb kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
testdb kernel: md: bitmap version 4.39
testdb kernel: TCP bic registered
testdb kernel: Initializing IPsec netlink socket
kernel: GSI 19 sharing vector 0x41 and IRQ 19
testdb kernel: sda: sda1 sda2 sda3
testdb kernel: sd 0:0:0:0: Attached scsi removable disk sda
testdb kernel: Vendor: IBM-ESXS Model: ST3146755SS Rev: BA32
testdb kernel: Type: Direct-Access ANSI SCSI revision: 05
testdb kernel: Vendor: IBM-ESXS Model: GNA146C3ESTT0Z N Rev: BH0G
testdb kernel: Type: Direct-Access ANSI SCSI revision: 05
testdb kernel: Vendor: IBM-ESXS Model: GNA146C3ESTT0Z N Rev: BH0G
testdb kernel: Type: Direct-Access ANSI SCSI revision: 05
testdb kernel: Vendor: IBM-ESXS Model: GNA146C3ESTT0Z N Rev: BH0G
testdb kernel: Type: Direct-Access ANSI SCSI revision: 05
testdb kernel: Vendor: IBM Model: SAS SES-2 DEVICE Rev: 1.06
testdb kernel: Type: Enclosure ANSI SCSI revision: 05
testdb kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
testdb kernel: device-mapper: uevent: version 1.0.3
testdb kernel: device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: [email protected]
testdb kernel: device-mapper: dm-raid45: initialized v0.2594l
testdb kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
testdb kernel: EXT3-fs: write access will be enabled during recovery.
testdb kernel: kjournald starting. Commit interval 5 seconds
testdb kernel: EXT3-fs: recovery complete.
testdb kernel: EXT3-fs: mounted filesystem with ordered data mode.
testdb kernel: SELinux: Disabled at runtime.
testdb kernel: type=1404 audit(1311581265.509:2): selinux=0 auid=4294967295 ses=4294967295
testdb kernel: parport: PnPBIOS parport detected.
testdb kernel: parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
testdb kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
testdb kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
testdb kernel: hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66)
testdb kernel: Uniform CD-ROM driver Revision: 3.20
testdb kernel: tg3.c:v3.96-1 (November 21, 2008)
testdb kernel: ACPI: PCI Interrupt 0000:1a:00.0[A] -> GSI 16 (level, low) -> IRQ 17
testdb kernel: eth0: Tigon3 [partno(BCM95721) rev 4201 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet
testdb kernel: ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 18
testdb kernel: BIOS-provided physical RAM map:
testdb kernel: Xen: 0000000000000000 - 000000006d746000 (usable)
testdb kernel: DMI present.
testdb kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
testdb kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
testdb kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
testdb kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
testdb kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
testdb kernel: ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24])
testdb kernel: IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
testdb kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
testdb kernel: Setting APIC routing to xen
testdb kernel: Using ACPI (MADT) for SMP configuration information
testdb kernel: Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
testdb kernel: ACPI: bus type pci registered
testdb kernel: PCI: Not using MMCONFIG.
testdb kernel: PCI: Using configuration type 1
testdb kernel: ACPI: Interpreter enabled
testdb kernel: ACPI: Using IOAPIC for interrupt routing
testdb kernel: ACPI: No dock devices found.
testdb kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
testdb kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
testdb kernel: PCI: Transparent bridge - 0000:00:1e.0
testdb kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 *6 7 10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 14 15)
testdb kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
testdb kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *9
testdb kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
testdb kernel: pnp: PnP ACPI init
testdb kernel: ACPI Error (exregion-0165): Could not map memory at 00000000FEC80000, size 100 [20060707]
testdb kernel: ACPI Exception (evregion-0424): AE_NO_MEMORY,
Returned by Handler for [SystemMemory] [20060707]
testdb kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._CRS] (Node ffff88000002d670), AE_NO_MEMORY
testdb kernel: ACPI Error (uteval-0212): Method execution failed [\_SB_.PCI0._CRS] (Node ffff88000002d670), AE_NO_MEMORY
* testdb *kernel: pnp: PnPACPI: METHODNAME__CRS failure for PNP0a03_
* testdb kernel: pnp: PnP ACPI: found 10 devices*testdb kernel: xen_mem: Initialising balloon driver.
I also try to find out flash bios from IBM Sites mention. but i could not able to get exact one. Kindly suggest me once again.
Edited by: opcare on Jul 25, 2011 3:55 AM

Acpi:error when booting the install

Hi guys,
So I want to install Arch, but when I boot into the install USB I directly see the following error:
ACPI: ERROR installing CMOS-RTC region handler
I saw here that apparently it's a kernel bug since the 3.15.3 version. The latest download has the 3.15.7 version.
First, I wanted to know if others came across this issue while installing.
I also wondered if it's worth to install with an older kernel (if possible) or just wait for a fix..

It doesn't block you from proceeding with install right?
If so, that just ignore it and proceed with install.
Your resulting installation will use most up-to-date kernel which is also "3.15.7-1-ARCH" (as of now) so that might indicate, that you might see this error also after installation.
Nevertheless, it's a not a deal-breaker, and just without looking into it much deeper it doesn't sound critical (CMOS Real Time Clock, is indeed not critical piece of system), tough you might see some problems with RTC subsystem.
Quickly skimming over the thread you linked, I don't see any relevant symptoms people are having there. I see different errors in my journal during boot. Reported as errors, but to be understood as warnings.
It's not so much beneficial to get over-excited about every red line in your journal, if there is not any documented real negative side-effects, usually this small issues tend to come and go, but it's always good to keep an eye on them.
If it bothers you though, you can install with downgraded kernel (but I don't think this error justifies doing so).

ACPI Error filling up logs, is generally disconcerting.

I keep getting these errors in my kernel log
Sep 6 00:02:01 computer kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L09] (Node eb80fdb0), AE_LIMIT
Sep 6 00:02:01 computer kernel: ACPI Exception (evgpe-0568): AE_LIMIT, while evaluating GPE method [_L09] [20090320]
Sep 6 00:02:01 computer kernel: ACPI Error (hwvalid-0154): Illegal I/O port address/length above 64K: 0x00400020/4 [20090320]
Sep 6 00:02:01 computer kernel: ACPI Exception (evregion-0422): AE_LIMIT, Returned by Handler for [SystemIO] [20090320]
They just repeat over and over again. The only problem I'm noticing is my logs are getting ridiculously large. I could probably change syslog around and never know I have a problem but I figure that would just lead to trouble later on. Google and some other linux sources turned up nothing helpful on these errors. So I'm hoping someone can atleast tell me where to start looking if they don't know exactly what's wrong.

Suppose if the source or the endsystem is in maintenance and is not availabel for the whole day.Now a days, it should be really a very rare scenario where a system goes down for an entire day for maintenance. 2-3 hours maintenance window is normal. If in your case, long maintenance windows are normal and frequent then I would suggest to change the design. Instead of polling remote system, let remote system push the files to OSB server (may be on JMS or any other persistent destination) and then even if remote system goes down it won't affect OSB.
As far enabling and disabling proxy services are concerned, you may handle it through scripts or java API's -
https://blogs.oracle.com/ateamsoab2b/entry/automatic_disabling_proxy_service_when
http://orasoa.blogspot.in/2011/05/disable-and-enable-osb-proxy-services.html
still no other choice?If most of the maintenance windows are scheduled then it is easy to handle the scenario with manual enable/disable of proxy services, but if mostly it is unscheduled then changing the solution design seems better option.
Regards,
Anuj

Solaris 11 ACPI Errors on Cisco USC C250 Server

I'm getting the errors listed below on a Cisco USC C250 Server. I don't get the errors on our Cisco C200 servers.
I'm wondering if there is something that should be disabled in the bios. I'm not sure what the ACPI errors mean.
Jan 28 18:43:47 server1282 acpica: [ID 177805 kern.notice] ACPI Error: No handler for Region [POWS] (ffffff1148343570) [IPMI] (20091112/evregion-484)
Jan 28 18:43:47 server1282 acpica: [ID 576484 kern.notice] ACPI Error: Region IPMI(7) has no handler (20091112/exfldio-380)
Jan 28 18:43:47 server1282 acpica: [ID 100000 kern.notice]
Jan 28 18:43:47 server1282 acpica: [ID 856526 kern.notice] **** Exception AE_NOT_EXIST during execution of method [\_SB_.PCI0.LPC0.P111._PSR] (Node ffffff1148314080)
Jan 28 18:43:47 server1282 acpica: [ID 100000 kern.notice]
Jan 28 18:43:47 server1282 acpica: [ID 652514 kern.notice] Method Execution Stack:
Jan 28 18:43:47 server1282 acpica: [ID 107261 kern.notice] Method [_PSR] executing: Store (BUFF, PPIF)
Jan 28 18:43:47 server1282 acpica: [ID 100000 kern.notice]
Jan 28 18:43:47 server1282 acpica: [ID 325098 kern.notice] Local Variables for method [_PSR]:
Jan 28 18:43:47 server1282 acpica: [ID 168412 kern.notice] Local0: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 170460 kern.notice] Local1: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 172508 kern.notice] Local2: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 174556 kern.notice] Local3: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 176604 kern.notice] Local4: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 178652 kern.notice] Local5: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 180700 kern.notice] Local6: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 182748 kern.notice] Local7: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 100000 kern.notice]
Jan 28 18:43:47 server1282 acpica: [ID 404092 kern.notice] Arguments for Method [_PSR]: (0 arguments defined, max concurrency = 0)
Jan 28 18:43:47 server1282 acpica: [ID 975559 kern.notice] Arg0: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975561 kern.notice] Arg1: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975563 kern.notice] Arg2: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975565 kern.notice] Arg3: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975567 kern.notice] Arg4: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975569 kern.notice] Arg5: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 975571 kern.notice] Arg6: 0 <Null Object>
Jan 28 18:43:47 server1282 acpica: [ID 100000 kern.notice]
Jan 28 18:43:47 server1282 acpica: [ID 872790 kern.notice] ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.PCI0.LPC0.P111._PSR] (Node ffffff1148314080), AE_NOT_EXIST

The server is not in the HCL list but you can try to boot with ACPI partially or fully disabled. Boot the solaris kernel with option "-B ...,user-acpi-options=0x8" or "-B ....,user-acpi-options=0x2".
When ACPI is disabled, make sure that the BIOS is configured to "Plug&Play OS" = "DISABLED" (BIOS must assign and configure resources for all PCI devices).

ACPI error and warnings on Linux Thinkpad T430

Hello,
i found in dmesg command output on my linux 3.13 (fedora 20) running on Thinkpad T430 (2349-H2G) the following warnings/errors about ACPI tables
-> ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
-> ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \_SB_.PCI0.LPC_.PMIO 1 (20131115/utaddress-251)
-> ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.LPC_.LPIO 1 (20131115/utaddress-251)
-> ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.LPC_.LPIO 1 (20131115/utaddress-251)
-> ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
->PCI: not using MMCONFIG
->ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
->ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
-> acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
-> acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
-> acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
-> acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
-> acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
-> acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
they seem related to a missing part on a FADT ACPI table or incorrect sintax
please can you fix it?

I have a W520 running Fedora20, with the same messages in the dmesg output; I assumed it was related to my nvidia (Optimus) card and, therefore, didn't worry since Optimus is still not quite fully supported--far from it, in fact. Do the T430s have switchable graphics? From what I can make out, it's referring to a "PlugNPlay??" device on the PCIe bus. Take a look around bugzilla.kernel.org, see if there are some similar bugs filed; I see this one that mentions "the acpi_idle driver is not registering with cpuidle no matter the parameters used, and Powertop-2.5 shows up empty in the Idle State tab". Try booting with these kernel parameters, see if it makes any difference at all:
intel_idle.max_cstate=0 and processor.nocst=1
and/or if you see something similar suggested in your dmesg output. Mine has
ACPI: Using IOAPIC for interrupt routing
[ +0.000026] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug

ACPI Error and warning

Hi everyone,
I just switched over from Ubuntu 14.04 after installing a new hard drive on my Samsung 900x3c. I did a clean Arch install with Lxqt as my desktop and in an attempt to get all the function keys working and installing samsung-tools I discovered a couple of errors and warnings in the dmesg output related to AE_NOT_FOUND as well as conflict between the systemIO range and the OpRegion. Now I would really like to remove these errors/warnings even though for the moment apart from the missing function keys (which might even be unrelated) I do not have any major side effects. The output of dmesg -t | grep -i 'error\|warn\|exception' is:
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20141107/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20141107/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20141107/utaddress-258)
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20141107/utaddress-258)
ACPI Warning: SystemIO range 0x000000000000efa0-0x000000000000efbf conflicts with OpRegion 0x000000000000efa0-0x000000000000efaf (\_SB_.PCI0.SBUS.SMBI) (20141107/utaddress-258)
Any ideas?
Thanks a lot in advance and best regards,
S

You can ignore those.
If you look at the journal entries around those lines you'll get more context for those messages.
The first one is part of the probing to find supported sleep states. Your system doesn't support the S2 sleep state.
The second is caused by your system's firmware not allowing the OS to use ASPM (Active State Power Management) to control the power mode of the PCI Express bus/devices. There can be lots of reasons for that - e.g. no support in firmware, firmware deliberately not allowing OS control, bug in firmware, specific manual settings have been set in the firmware, etc. Unless you care about the power management of PCI Express devices, just ignore the message. Otherwise, check the PCI Express power settings (if available) in your system's firmware, alternativelyi there may be a newer firmware - if there is, see what the changes are to determine if updating will help.
for the ACPI warnings see https://bbs.archlinux.org/viewtopic.php?id=163556

6199-VA and ACPI error in XP Pro

I get an error in Win XP:
"the ACPI Bios tries to read a forbidden port I/O address
(0x4d1). This can cause a system instability."
I've upgrade the MS-6199 Bios to the latest and Win XP
to the Service pack1, but the problem is still there.
Plese help me!!!

face facts its an old board if you think msi are going to do a new bios for that now ,well lets say its just not about to happen

Cannot boot from OSX DVD - ACPI error

I am unable to boot from my OSX installation DVD. While booting I receive the following message:
Panic (cpu 0 caller 0x003A934F) Unable to find driver for this platform: ACPI.
I have tried re-installing the combo updater and flashing the PRAM, without any success.
Can anyone PLEASE HELP? My hard drive needs repair and I must boot from DVD in order to gain access to make the repairs with the Disk Utility.
Much thanks!

Will it run the Extended Tests from Apple Hardware Test (Boot while holding "D")?
If it won't boot from the install disk, it is not a problem with any software on your hard drive. It has to be a hardware problem; probably the DVD drive, since OSX is mostly working. If you have another Mac that can read DVDs and has FireWire, put the DVD in that Mac and boot it in Target Disk Mode (hold "T" while booting. Connect it to the Mac Pro with a FireWire cable, and boot the Mac Pro while holding Option. If the DVD shows up, select it and click the straight, right-pointing, arrow.
If that doesn't work, try booting the Mac Pro in Target Disk Mode (Boot while pressing "T"), connect it to another Mac via FireWire, and try to repair the Mac Pro disk with Disk Utility (Tiger version), or Disk Warrior (version 4 or later).

ACPI error while installing on Dell Dimension

Try to install Solaris 8 on Dell Dimension 4100,
right after starting from CD rom, system reported:
Sun Secondary Boot Version 3.00
Warning : ACPI Tables not in Reclaim Memory
prom_panic:kmem_free block already free
I try to continue and was told to reboot the computer by press "ctrl-alt-del"
Is there any solution to the problem?

Hi Vijay
I can see a constarint on / and /dev directory.Rest Of directory has a lot of available space.Can this cause the problem.
Filesystem size used avail capacity Mounted on
/ 2.0G 1.6G 371M 82% /
/dev 2.0G 1.6G 371M 82% /dev
/lib 59G 8.3G 50G 15% /lib
/platform 59G 8.3G 50G 15% /platform
/sbin 59G 8.3G 50G 15% /sbin
/usr 59G 8.3G 50G 15% /usr
/usr/local 30G 2.3G 26G 8% /usr/local
/usr/openv 6.0G 3.1G 2.8G 53% /usr/openv
proc 0K 0K 0K 0% /proc
ctfs 0K 0K 0K 0% /system/contract
mnttab 0K 0K 0K 0% /etc/mnttab
objfs 0K 0K 0K 0% /system/object
swap 102G 392K 102G 1% /etc/svc/volatile
/platform/SUNW,T5240/lib/libc_psr/libc_psr_hwcap2.so.1
59G 8.3G 50G 15% /platform/sun4v/lib/libc_psr.so.1
/platform/SUNW,T5240/lib/sparcv9/libc_psr/libc_psr_hwcap2.so.1
59G 8.3G 50G 15% /platform/sun4v/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
swap 102G 48K 102G 1% /tmp
swap 102G 48K 102G 1% /var/run
3.24.144.10:/vol/preprovis_88
25G 972M 24G 4% /u01
Thanks
Chinmay

BIOS acpi error with WXP SP2 on Sat Pro 4310 model

Hello,
I keep getting this message in my event logs
Is there a way (update,etc) to come around it
Thanks in advance
William

Hello
Well, I think its a Windows Xp problem. After a long investigation I found this information on the official Microsoft website.
http://support.microsoft.com/kb/q283649/
That is because the new ACPI specifications are not compatible with the BIOS.
Please check this:
http://www.microsoft.com/HWDEV/Onnow/BIOSAML.htm
It seems you have to upgrade your BIOS to solve this problem.
Bye

MOVED: K9A2 Platinum ACPI errors after resume

This topic has been moved to Vista problems.
https://forum-en.msi.com/index.php?topic=114100.0

You're welcome!
I had same problem with my old build; same RX1950 card but with K8NGM2-FID board. I think I may have updated the Catalyst drivers after I gave up trying to get standby to work, but it works flawlessly now in this new K9A2 Platinum system I have. Just to note, I rebuilt my brother's K7N2 Delta2 system with the old K8NGM2-FID board, and resume from standby works fine there too. So it could well have just been a driver issue.

ACPI Error

Similar Messages

Maybe you are looking for