lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1210343425.29724.39.camel@queen.suse.de>
Date:	Fri, 09 May 2008 16:30:25 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Gabriel C <nix.or.die@...glemail.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: linux-next: ACPI I/O resource conflicts warning

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.

> 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.

Thanks,

   Thomas

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ