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: <469D1A65.8030704@opinicus.com>
Date:	Tue, 17 Jul 2007 15:37:09 -0400
From:	William Montgomery <william@...nicus.com>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
CC:	Krzysztof Halasa <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: e100 PCI bridge problem

Kok, Auke wrote:

>> 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to 
>> PCI Bridge (rev 82) (prog-if 00 [Normal decode])
>>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
>> ParErr- Stepping- SERR+ FastB2B-
>>         Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast 
>> >TAbort- <TAbort- <MAbort- >SERR- <PERR+
>
>
> PERR+ set... not good - this certainly will cause major issues
>
I know it sounds that way based on the definition (Detected parity error 
on hub side), however I have two other identical systems that have been 
running fine for months - with this same bit set - only they use an 
Adaptec ANA-64044 (4 port card - 10/100 fast ethernet - unfortunately 
discontinued). 

It seems the Pericom PCI to PCI bridge is having a problem talking to 
the LAN controllers behind the Hint bridge.

-
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