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: <48DA88EB.6030601@intel.com>
Date:	Wed, 24 Sep 2008 11:37:31 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	John Gumb <john.gumb@...dberg.com>
CC:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: D945GCLF  intel atom board & r8169 ethernet broken in linux-2.6.27-rc5??

John Gumb wrote:
> Hi
> 
> I have an Intel Atom D945GCLF based system. It has a realtek RTL8101E
> PCI network interface.
> 
> With linux-2.6.27-rc4 - everything seems fine. I think we've been
> working OK since 2.6.26ish.
> 
> With linux-2.6.27-rc5, "ifconfig eth0" just hangs. lspci -vvx reports,
> after loading the driver,
> 
>> 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  
> 
> Before I load the driver lspci -vvx looks OK.
> 
> I do not have (much) time to look into this any further but hopefully
> this might help someone.
> 
> I know there are problems with this device on the atom board
> particularly around warm start but thus far I seem to have avoided this
> issue.
> 
> A cold start in this case does not help.
> 
> Lspci.bad comes from -rc5 with the r8169 driver loaded.
> Lspci.good comes from -rc4 with the r8169 driver loaded


did you check if falling back to the older kernel makes the device work again?
--
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