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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <46F85D3F.5010400@lwfinger.net>
Date:	Mon, 24 Sep 2007 19:58:39 -0500
From:	Larry Finger <larry.finger@...inger.net>
To:	LKML <linux-kernel@...r.kernel.org>
CC:	John Pierce <john.j35@...il.com>,
	Broadcom Linux <bcm43xx-dev@...ts.berlios.de>
Subject: Missing PCIe interface in lspci

In the process of advising a user on getting a BCM4311 wireless device to work with bcm43xx rather
than ndiswrapper, the device stopped appearing in an lspci output. The 'lspci -vn' output
for this device before this failure was:

03:00.0 0280: 14e4:4311 (rev 01)
        Subsystem: 103c:1363
        Flags: fast devsel, IRQ 21
        Memory at b8000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
        Capabilities: [d0] Express Legacy Endpoint IRQ 0

Fortunately, the "customer" has two identical machines. Swapping the wireless cards showed that both
BCM4311s work in the other computer, but neither works in the problem machine. Kernel Version
2.6.22.4-65.fc7 is used on both.

Doing a line-by-line comparison of the dmesg outputs, the only thing that stands out is that the line

Allocate Port Service[0000:00:03.0:pcie03]

is missing on the faulty computer. This is the bridge that should connect to the device in question.

The BIOS has been reset and reflashed without helping the problem.

Is there anything other than some failure on the motherboard that would lead to this situation? Is
there anything that we can try? The BIOS in this machine doesn't have many options.


Thanks,

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