linux-kernel - Re: Bogus PCI vendor ID

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

Message-ID: <20071119092736.7cb21231@freepuppy.rosehill>
Date:	Mon, 19 Nov 2007 09:27:36 -0800
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	"Simon Arlott" <simon@...e.lp0.eu>
Cc:	"Francois Romieu" <romieu@...zoreil.com>,
	"Kai Ruhnau" <kai@...getaschen.dyndns.org>,
	"LKML" <linux-kernel@...r.kernel.org>, gregkh@...e.de,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: Bogus PCI vendor ID

On Mon, 19 Nov 2007 12:22:20 -0000
"Simon Arlott" <simon@...e.lp0.eu> wrote:

> On Sat, November 17, 2007 18:40, Francois Romieu wrote:
> > Kai Ruhnau <kai@...getaschen.dyndns.org> :
> > [...]
> >> I have a problem with two of my PCI devices showing the wrong PCI vendor
> >> ID (0001) in vanilla kernels.
> 
> Have you tried doing a cold boot at every test? I've had bogus PCI IDs
> appear before where it was the device's fault, and the ID would change
> after the first boot.
> 

With LAN devices you may even need to pull the plug because WOL will
keep the device in a warmstart state.

-- 
Stephen Hemminger <shemminger@...ux-foundation.org>
-
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/