From: Michael Grollman <mgrollman@nscus.com>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
Francois Romieu <romieu@fr.zoreil.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, 09 Jul 2008 16:31:03 -0700 [thread overview]
Message-ID: <48754A37.6040200@nscus.com> (raw)
In-Reply-To: <4874F60F.2030501@dell.com>
Mario,
I think patch noted below worked to resolve the remaining issues I have
been experiencing with with realtek Ethernet port on the Intel D945GCLF
motherboard (Atom Mini-ITX). I tested with the 2.6.26-rc9 kernel this
time, although I applied the patch to the 2.6.25's r8169.c.
Likely it is my inexperience, but the patch as I copied it from the
netdev@vger.kernel.org posting did not apply cleanly using the patch
tool, so I had to hand-apply the patch code changes to 8169.c. However,
once this was done and compiled, the Ethernet began working much
better. I have not been able so far to make it fail, even more than two
dozen or more cold and warm resets. Previous failure rate was at least
during 50% of resets, so it is at a minimum much more stable on startup.
Much thanks!
- Michael
Mario Limonciello wrote:
> Hi Michael:
>
> Sorry, I posted this to the list I received your message from
> (netdev@vger.kernel.org). I don't believe it's been applied by anyone
> as of yet.
>
> Regards
>
> Michael Grollman wrote:
>
>> Mario,
>>
>> Apologies in advance for my ignorance.
>>
>> When you write below about 'the patch' and 'the list,' can you be a
>> bit more specific, particularly about which list you posted it to?
>>
>> Also, I think Kasper's question below related to, was the patch you
>> used to fix your 8169 issues now part of rc9, or is it still
>> independent of the main tree? For those like me not used to be
>> bleeding edge, its cleaner to just snag the rc candidate than to try
>> the hand patch method.
>>
>> Any insight you can offer is appreciated.
>>
>> Cheers,
>>
>> - Michael
>>
>> Mario Limonciello wrote:
>>
>>> Kasper:
>>>
>>> Particularly try the patch that I posted to the list. It solved the
>>> ifup (and resume) failures for me on two platforms using that chipset.
>>>
>>> Regards
>>>
>>> Kasper Sandberg wrote:
>>>
>>>
>>>> On Thu, 2008-06-26 at 23:59 +0200, Francois Romieu wrote:
>>>> Sorry for the delay, i had to do an onsite thing in another
>>>> country, so
>>>> i first see your message now.
>>>>
>>>> Would it be okay if i took rc9 instead? also, i saw you posted a set of
>>>> patches to sync more with realteks code, is this something you would
>>>> like me to test too, or aswell? (remember, i have the 8111c).
>>>>
>>>> Btw, a thought just crossed my mind as to a possible reason why this
>>>> might be happening, i was googling around, and it seems the TWO nic's
>>>> are supposed to have some sort of hardware bonding thing, could it be
>>>> because such stuff isnt handled?
>>>>
>>>> mvh.
>>>> Kasper Sandberg
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>>
>>>
>>>
>
>
--
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@nscus.com
www.nsct.info
next prev parent reply other threads:[~2008-07-09 23:31 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 [this message]
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
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=48754A37.6040200@nscus.com \
--to=mgrollman@nscus.com \
--cc=akpm@linux-foundation.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=mario_limonciello@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.