linux-kernel - RE: PCI BAR mem resource allocation "regression"

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: <B57D568CB82B0C4B897F9CD9862DE8B733BD4296E3@GVW1097EXB.americas.hpqcorp.net>
Date:	Mon, 15 Dec 2008 22:29:42 +0000
From:	"Chen, Justin" <justin.chen@...com>
To:	"Chen, Justin" <justin.chen@...com>,
	"Chiang, Alexander" <achiang@...com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"matthew@....cx" <matthew@....cx>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: PCI BAR mem resource allocation "regression"

>>-----Original Message-----
>>From: Chiang, Alexander
>>
>>> Also, is it just the error message, or does it actually affect
>>> functionality?
>>
>>Hm, that is a good question. ;) The particular device I was testing
>>with was an infiniband device, and I have never actually pushed any
>>traffic over it; just used it to reproduce the error.
>>
>>I can try and hook the card up to something and push traffic over it,
>>but that will have to wait until Monday. Maybe Justin (cc'ed) knows,
>>since he was the one who first reported this to me.
>

More information of the error:

I tried it on a LAN and infiniband cards.  After the hotplug, the device is not registered anymore.  Below is an example on the lan card (eth4, 002b:01:00.0, slot 1306):

# ls /sys/class/net
eth0   eth10  eth12  eth3   eth5   eth7   eth9   ib1    ib3
eth1   eth11  eth2   eth4   eth6   eth8   ib0    ib2    lo
# cat /sys/class/net/eth4/device/uevent
DRIVER=e1000
PCI_CLASS=20000
PCI_ID=8086:105F
PCI_SUBSYS_ID=103C:704F
PCI_SLOT_NAME=002b:01:00.0
MODALIAS=pci:v00008086d0000105Fsv0000103Csd0000704Fbc02sc00i00
# cat /sys/bus/pci/slots/1306/address
002b:01:00
# echo 0 > /sys/bus/pci/slots/1306/power
# ls /sys/class/net
eth0   eth10  eth12  eth3   eth7   eth9   ib1    ib3
eth1   eth11  eth2   eth6   eth8   ib0    ib2    lo
# echo 1 > /sys/bus/pci/slots/1306/power
PCI: Failed to allocate mem resource #0:20000@...7ee00000 for 002b:01:00.0
PCI: Failed to allocate mem resource #1:20000@...7ee00000 for 002b:01:00.0
PCI: Failed to allocate mem resource #6:20000@...7ee00000 for 002b:01:00.0
PCI: Failed to allocate mem resource #0:20000@...7ee00000 for 002b:01:00.1
PCI: Failed to allocate mem resource #1:20000@...7ee00000 for 002b:01:00.1
PCI: Failed to allocate mem resource #6:20000@...7ee00000 for 002b:01:00.1
PCI: Failed to allocate I/O resource #2:20@...00 for 002b:01:00.0
PCI: Failed to allocate I/O resource #2:20@...00 for 002b:01:00.1
e1000: 002b:01:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: 002b:01:00.1: e1000_probe: The EEPROM Checksum Is Not Valid
# ls /sys/class/net
eth0   eth10  eth12  eth3   eth7   eth9   ib1    ib3
eth1   eth11  eth2   eth6   eth8   ib0    ib2    lo
#

Justin
--
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/