From: Gabriel C <nix.or.die@googlemail.com>
To: trenn@suse.de
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: linux-next: ACPI I/O resource conflicts warning
Date: Fri, 09 May 2008 18:52:11 +0200 [thread overview]
Message-ID: <4824813B.6090607@googlemail.com> (raw)
In-Reply-To: <1210343425.29724.39.camel@queen.suse.de>
Thomas Renninger wrote:
> On Fri, 2008-05-09 at 03:20 +0200, Gabriel C wrote:
>> Hi all ,
>>
>> I've noticed on linux-next from today the following ACPI warning:
>>
>> ...
>>
>> [4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18
>> [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f]
>> [4294023.316478] ACPI: Device needs an ACPI driver
>
> You use libsensors and the sensor you use is also declared and possibly
> used via ACPI.
Not really , lsmsensors was not running and no modules loaded for my sensors but yeah when I start it another warning
pops up ( this one I've reported to lm-sensors mailing list )
w83627ehf: Found W83627DHG chip at 0x290
ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
ACPI: Device needs an ACPI driver
>
>> dsdt.dsl from my motherboard can be found there:
>>
>> http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
>>
>> full dmesg:
>>
>> http://frugalware.org/~crazy/dmesg/DMAR/dmesg
>>
>> Please let me know if you need more infos.
>
> Maybe you could open a bug report on bugzilla.kernel.org and post
> acpidump and dmi output (not only dsdt) there. Then we could collect
> affected BIOSes at one central place for further evaluation and
> discussion.
Sure I will open an task about soon.
>
> Thanks,
>
> Thomas
Gabriel
next prev parent reply other threads:[~2008-05-09 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 1:20 linux-next: ACPI I/O resource conflicts warning Gabriel C
2008-05-09 14:30 ` Thomas Renninger
2008-05-09 16:52 ` Gabriel C [this message]
2008-05-09 16:58 ` Jean Delvare
2008-05-09 17:04 ` Gabriel C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4824813B.6090607@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox