netdev - Re: 8169 Intermittent ifup Failure Issue With RTL8102E Chipset in Intel's New D945GCLF Atom Board (Not the Initial Modprobe Crash, Another Problem)

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: <486417C5.3080106@nscus.com>
Date:	Thu, 26 Jun 2008 15:27:17 -0700
From:	Michael Grollman <mgrollman@...us.com>
To:	Francois Romieu <romieu@...zoreil.com>
CC:	netdev@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: 8169 Intermittent ifup Failure Issue With RTL8102E Chipset in
 Intel's New D945GCLF Atom Board (Not the Initial Modprobe Crash,	Another
 Problem)


Francois,

The failure can be reproduced with:

    pci=nommconf

and also with:

    pci=conf1

I attached a gzip of the .config used for this build.  It should be very 
close to 'right out of the box.'

- Michael


Francois Romieu wrote:
> (linux-pci Cced)
>
> Michael Grollman <mgrollman@...us.com> :
> [...]
>   
>> Per instructions, I built an 2.6.26-rc8 system on the target Intel 
>> hardware, and was able to re-recreate the intermittent failure of the 8201. 
>>  When in failure mode, the lspci -vx' display of the pci registers of the 
>> 8102 is as follows:
>>
>> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI 
>> Express Fast Ethernet controller (rev ff) (prog-if ff)
>>    !!! Unknown header type 7f
>> 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>     
>
> Bad mojo.
>
> Can you reproduce the failure of the driver or lspci when you
> boot the kernel with "pci=nommconf" (assuming CONFIG_PCI_MMCONFIG is
> set in your .config) or "pci=conf1" (if CONFIG_PCI_DIRECT is instead).
>
> [...]
>   
>> Let me know if there is anything else I can do to collect information on 
>> this situation.
>>     
>
> The (gzipped) content of your .config.
>
> Kasper, could you check if you have the same symptoms with
> 2.6.26-rc8 (once your rendering is finished of course) ?
>
>   

-- 
Michael Grollman
National Scientific Corporation
8361 East Evans Rd Ste 106
Scottsdale, AZ.  85260  USA
Voice: +1-480-948-8324 x 303
Fax: +1-480-483-8893
mgrollman@...us.com
www.nsct.info


Download attachment "config.2.6.26r8.gz" of type "application/x-gzip" (16076 bytes)