Bug 802227 - acpi error message at boot "[io 0x4040-0x405f] conflicts with ACPI region SMBI [io 0x4040-0x404f]"
Summary: acpi error message at boot "[io 0x4040-0x405f] conflicts with ACPI region SM...
Keywords:
Status: CLOSED DUPLICATE of bug 802224
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 07:30 UTC by Michael
Modified: 2012-03-12 14:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-12 14:05:16 UTC
Type: ---


Attachments (Terms of Use)
lspci -vvnn (12.56 KB, text/plain)
2012-03-12 07:30 UTC, Michael
no flags Details
dmidecode (13.28 KB, text/plain)
2012-03-12 07:30 UTC, Michael
no flags Details
dmesg | grep ACPI (8.16 KB, text/plain)
2012-03-12 07:32 UTC, Michael
no flags Details

Description Michael 2012-03-12 07:30:16 UTC
Created attachment 569291 [details]
lspci -vvnn

Description of problem:
The problem is that the following error message appears at the boot log of my laptop

Version-Release number of selected component (if applicable):
Fedora with last updates

How reproducible:
every time at boot

Steps to Reproduce:
1. reboot laptop
2. cat /var/log/messages
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Michael 2012-03-12 07:30:59 UTC
Created attachment 569292 [details]
dmidecode

Comment 2 Michael 2012-03-12 07:32:01 UTC
Created attachment 569293 [details]
dmesg | grep ACPI

Comment 3 Josh Boyer 2012-03-12 14:05:16 UTC
Are you actually having some kind of functional problem with the machine, or are you just seeing these messages?

Also, you probably didn't need to open two bugs for this, so I'm duplicating this to the other one you opened.

*** This bug has been marked as a duplicate of bug 802224 ***


Note You need to log in before you can comment on or make changes to this bug.