linux-kernel

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: <46543045.3030904@gmail.com>
Date:	Wed, 23 May 2007 16:15:01 +0400
From:	Manu Abraham <abraham.manu@...il.com>
To:	linux-pci@...ey.karlin.mff.cuni.cz
CC:	Greg KH <greg@...ah.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: PCIE

Hi,

Do the PCI Express chipsets also use the same PCI API ? The device
specifications are thus for the device that i am looking at:

 PCI Express interface

    * Compliant to PCI Express Base Specification 1.0a
    * The PCI Express circuit supports isochronous data traffic intended
for uninterrupted transfer of streaming data like video streaming
          o x1 PCI Express endpoint (2.5 Gbit/s)
          o Data and clock recovery from serial stream
          o Low jitter and BER
    * Type 0 configuration space header
          o 64-bit addressing
          o Single BAR; programmable address range of 17 bits, 18 bits,
19 bits or 20 bits dependent on application requirements
    * PCI Express capabilities
          o 128 bytes write packet size and 64 bytes read packet size
          o MSI support
          o Software directed power management of four device power
states (D0 to D3)
          o Active state power management of link states
          o Vendor specific capability for VC1 support; after reset VC1
isochronous capability is disabled

I have been trying the said card with a normal PCI style driver, but
while booting the kernel (2.6.21.1) i do get a message like this (an
Intel DP965LT motherboard with BIOS version:
MQ96510J.86A.1612.2006.1227.1513)
Also accessing the interrupt registers causes a hard freeze, for which
only the RESET button seems to be of any help.

Uncompressing Linux .. Ok, booting the kernel.
BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw
vendor)
PCI: Failed to allocate mem resource #6:20000@...00000 for 0000:01:00.0

Any ideas as to what could be wrong ?

Thanks,
Manu
-
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/