From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: John Gumb <john.gumb@tandberg.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: D945GCLF intel atom board & r8169 ethernet broken in linux-2.6.27-rc5??
Date: Wed, 24 Sep 2008 11:37:31 -0700 [thread overview]
Message-ID: <48DA88EB.6030601@intel.com> (raw)
In-Reply-To: <9F6ACAE02B6DD040A1E259977622CFDB03F5BCCB@oslexcp1.eu.tandberg.int>
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?
next prev parent reply other threads:[~2008-09-24 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 11:26 D945GCLF intel atom board & r8169 ethernet broken in linux-2.6.27-rc5?? John Gumb
2008-09-24 18:37 ` Kok, Auke [this message]
2008-09-24 20:19 ` Francois Romieu
2008-09-26 21:45 ` Rafael J. Wysocki
2008-09-26 21:52 ` Francois Romieu
2008-09-26 22:27 ` Rafael J. Wysocki
2008-09-24 22:26 ` Jiri Kosina
2008-09-24 22:27 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48DA88EB.6030601@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=john.gumb@tandberg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).