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: <1a297b360702041709l3b0309c7y8fcd33df1d487889@mail.gmail.com>
Date:	Mon, 5 Feb 2007 05:09:01 +0400
From:	"Manu Abraham" <abraham.manu@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-pci@...ey.karlin.mff.cuni.cz, greg@...ah.com,
	"Andrew Morton" <akpm@...l.org>
Subject: 2.6.20 PCI Cannot allocate resource region 2

Hi,

I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
the message is slightly different in 2.6.17.7)

PCI Cannot allocate resource region 2 of device 0000:02:0a.0
PCI Error while updating region 000:02:0a.0/5 (f3e00004 != 0200)
PCI Error while updating region 000:02:0a.0/5 (high 00000000 != 4e351)

lspci shows me a bit weird status BIST is running (on 2.6.17.7)
on 2.6.20, the line which says BIST is running, does not exist.

I have attached the lspci outputs on both 2.6.17.7 and 2.6.20

The device is a PCI 2.2 compliant device a multimedia bridge device
called Mantis.
The card is a plain 32 bit PCI card in a 32 bit PCI slot on an Asus
P4C800 motherboard.

looking at lspci output, the last 3 PCI devices are using the same chip.

The last 2 devices are Rev 1 chips, whereas the one which is acting a
bit strange is a newer version from the same vendor.

Any ideas as to why it could not allocate the region ?

Thanks,
Manu

View attachment "lspci-2.6.17.7.txt" of type "text/plain" (10324 bytes)

View attachment "lspci-2.6.20.txt" of type "text/plain" (10321 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ