linux-kernel - ACPI error when mapping a 2GB BAR w/ 4GB of RAM

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinORYZOYk9xsST+J=zxgeZPr2BNw3S=dvPPTcdn@mail.gmail.com>
Date:	Fri, 17 Sep 2010 14:00:00 -0600
From:	Cam Macdonell <cam@...ualberta.ca>
To:	"qemu-devel@...gnu.org Developers" <qemu-devel@...gnu.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Chris Wright <chrisw@...hat.com>
Subject: ACPI error when mapping a 2GB BAR w/ 4GB of RAM

After fixing the resource_size_t return value with
pci_resource_alignment, I see one other strange behaviour only when
using 4GB of RAM and a 2GB BAR.  I haven't found any other combination
of RAM/BAR size that triggers this bug.  I am using 2.6.36-rc3.

ACPI Error: The DSDT has been corrupted or replaced - old, new headers
below (20100702/tbutils-372)
ACPI: DSDT (null) 01F15 (v01   BXPC   BXDSDT 00000001 INTL 20090123)
ACPI:      (null) 00000 (v00                 00000000      00000000)
ACPI Error: Please send DMI info to linux-acpi@...r.kernel.org
If system does not work as expected, please boot with acpi=copy_dsdt
(20100702/tbutils-378)
ACPI: PCI Interrupt Link [LNKC] disabled and referenced, BIOS bug
ACPI Exception: AE_AML_INVALID_RESOURCE_TYPE, Evaluating _CRS
(20100702/pci_link-283)
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKC]. Try pci=noacpi
or acpi=off
virtio-pci 0000:00:03.0: PCI INT A: no GSI - using ISA IRQ 11
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

with acpi=off, the ACPI error output goes away, but the boot does not
get any further.

here are the PCI writes from Qemu related to this BAR's assignment in
case they are helpful,

pci_write_config: (val) 0x80000004 -> 0x18 (addr)
IVSHMEM: guest pci addr = 80000000, guest h/w addr = 4312137728, size = 80000000
pci_read_config: (val) 0x80000004 <- 0x18 (addr)
pci_write_config: (val) 0x1 -> 0x1c (addr)
IVSHMEM: guest pci addr = 180000000, guest h/w addr = 4312137728, size
= 80000000
pci_read_config: (val) 0x1 <- 0x1c (addr)

Any pointers are appreciated,
Cam
--
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/