From: Kasper Sandberg <lkml@metanurb.dk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Mario Limonciello <mario_limonciello@dell.com>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
Marcus Sundberg <marcus@ingate.com>,
Michael Grollman <mgrollman@nscus.com>,
netdev@vger.kernel.org, akpm@linux-foundation.org,
linux-pci@vger.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)
Date: Wed, 16 Jul 2008 17:03:18 +0200 [thread overview]
Message-ID: <1216220598.10312.12.camel@localhost> (raw)
In-Reply-To: <20080715185646.GA27023@electric-eye.fr.zoreil.com>
On Tue, 2008-07-15 at 20:56 +0200, Francois Romieu wrote:
> Mario Limonciello <mario_limonciello@dell.com> :
> [...]
> > If I was to guess (I didn't actually work out which one yours identifies
> > as), most likely your NIC isn't caught in my check for MAC_VER_13 or
> > MAC_VER_16, but Francois's patch has:
>
> +1
>
> (actually this change was contributed by Marcus Sundberg: see
> the Signed-off-by and/or the patch named
> 0003-r8169-avoid-thrashing-PCI-conf-space-above-RTL_GIGA.patch)
>
> I doubt that it will break anybody's 8101 (resp. 8102) but I would
> welcome a report from a 8101/8102 owner before sending it upstream.
Yeah, this change will definetly be good news to lots of realtek pci
express owners, googling for this issue myself i found that alot of
people are having it, and finding it difficult/annoying to grab 8168
from realteks site, not to mention often compatibility issues, so this
is a very welcome fix :D
>
> Sorry for disturbing linux-pci.
>
next prev parent reply other threads:[~2008-07-16 15:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4861800B.90703@nscus.com>
2008-06-25 21:31 ` 8169 Intermittent ifup Failure Issue With RTL8102E Chipset in Intel's New D945GCLF Atom Board (Not the Initial Modprobe Crash, Another Problem) Francois Romieu
2008-06-26 21:08 ` Michael Grollman
2008-06-26 21:59 ` Francois Romieu
2008-06-26 22:27 ` Michael Grollman
2008-06-27 2:35 ` Matthew Wilcox
2008-06-27 2:58 ` mgrollman
2008-06-27 3:25 ` Mario_Limonciello
2008-06-27 4:44 ` Michael Grollman
2008-07-07 12:53 ` Kasper Sandberg
2008-07-07 15:15 ` Mario Limonciello
2008-07-09 17:05 ` Michael Grollman
2008-07-09 17:31 ` Mario Limonciello
2008-07-09 23:31 ` Michael Grollman
2008-07-11 13:35 ` Kasper Sandberg
2008-07-11 15:26 ` Mario Limonciello
2008-07-14 16:21 ` Kasper Sandberg
2008-07-14 19:52 ` Rolf Eike Beer
2008-07-14 20:00 ` Mario Limonciello
2008-07-14 20:45 ` Kasper Sandberg
2008-07-14 21:00 ` Mario Limonciello
2008-07-15 18:56 ` Francois Romieu
2008-07-16 15:03 ` Kasper Sandberg [this message]
2008-07-15 18:58 ` Francois Romieu
2008-09-22 17:20 ` Michael Grollman
2008-06-24 23:27 Michael Grollman
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=1216220598.10312.12.camel@localhost \
--to=lkml@metanurb.dk \
--cc=akpm@linux-foundation.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-pci@vger.kernel.org \
--cc=marcus@ingate.com \
--cc=mario_limonciello@dell.com \
--cc=mgrollman@nscus.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).