From: <mgrollman@nscus.com>
To: "'Matthew Wilcox'" <matthew@wil.cx>,
"'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: <netdev@vger.kernel.org>, "'Kasper Sandberg'" <lkml@metanurb.dk>,
<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: Thu, 26 Jun 2008 19:58:29 -0700 [thread overview]
Message-ID: <006001c8d801$b02daf10$860aa8c0@MICHAEL1> (raw)
In-Reply-To: <20080627023523.GD7703@parisc-linux.org>
Matthew,
The only remedy I have found to date is a system reboot, sometimes a soft
one will work, sometimes a full
power down is needed. It may take a few boots to get it happy. If I can
get it to boot with the Realtek working OK, the system does not seem to
fail, even after hours of use. So either it comes up working, or it does
not.
But I am open to any ideas to try and correct! I have an extra motherboard
around, if you guys think it may be in this particular unit's hardware.
- Michael
-----Original Message-----
From: Matthew Wilcox [mailto:matthew@wil.cx]
Sent: Thursday, June 26, 2008 7:35 PM
To: Francois Romieu
Cc: Michael Grollman; netdev@vger.kernel.org; Kasper Sandberg;
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)
On Thu, Jun 26, 2008 at 11:59:18PM +0200, Francois Romieu wrote:
> (linux-pci Cced)
>
> Michael Grollman <mgrollman@nscus.com> :
> [...]
> > Per instructions, I built an 2.6.26-rc8 system on the target Intel
> > hardware, and was able to re-recreate the intermittent failure of the
8201.
> > When in failure mode, the lspci -vx' display of the pci registers
> > of the
> > 8102 is as follows:
> >
> > 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
Mmm. All f's means that the device has fallen off the bus. Nothing is
responding when we ask the device about it's config space. What do you do
to get this device into this state?
--
Intel are signing my paycheques ... these opinions are still mine "Bill,
look, we understand that you're interested in selling us this operating
system, but compare it to ours. We can't possibly take such a retrograde
step."
next prev parent reply other threads:[~2008-06-27 2:58 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 [this message]
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
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='006001c8d801$b02daf10$860aa8c0@MICHAEL1' \
--to=mgrollman@nscus.com \
--cc=akpm@linux-foundation.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=matthew@wil.cx \
--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).