linux-kernel - Re: D945GCLF intel atom board & r8169 ethernet broken in linux-2.6.27-rc5??

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

Message-ID: <9F6ACAE02B6DD040A1E259977622CFDB03F5C24B@oslexcp1.eu.tandberg.int>
Date:	Thu, 25 Sep 2008 15:58:17 +0200
From:	"John Gumb" <john.gumb@...dberg.com>
To:	<linux-kernel@...r.kernel.org>
Subject: Re: D945GCLF  intel atom board & r8169 ethernet broken in linux-2.6.27-rc5??

My fault

linux-2.6.27-rc7 fixes this. I should have tested this.

Thanks to all who responded with fixes.

John

-----Original Message-----
From: John Gumb 
Sent: 24 September 2008 12:26
To: linux-kernel@...r.kernel.org
Cc: 'netdev@...r.kernel.org'
Subject: D945GCLF intel atom board & r8169 ethernet broken in
linux-2.6.27-rc5??

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

Cheers

John
--
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/