netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
	Francois Romieu <romieu@fr.zoreil.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: Mon, 14 Jul 2008 15:00:37 -0500	[thread overview]
Message-ID: <487BB065.3020709@dell.com> (raw)
In-Reply-To: <200807142152.26163.eike-kernel@sf-tec.de>

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

Kasper:

Interesting that it failed for you though.  I was able to run through a
script of 200x rmmod/modprobe without any trouble when that patch was
applied.

Regards

Rolf Eike Beer wrote:
> Kasper Sandberg wrote:
>   
>
> Is there any chance this helps with the famous 8101 problems, e.g. 
> http://bugzilla.kernel.org/show_bug.cgi?id=6807 ?
>
>   
>
> There is a typo in the description of 91ba1a976c214766b5ee8c6d17086903c10f6405 
> (serie should be series I think).
>
> Greetings,
>
> Eike
>   

-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2008-07-14 20:00 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 [this message]
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=487BB065.3020709@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=akpm@linux-foundation.org \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    --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).