public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ismael Luceno <ismael.luceno@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: r8169 with 64bit DMA is broken
Date: Wed, 31 Mar 2010 09:23:15 -0300	[thread overview]
Message-ID: <20100331092315.1a5ac86a@gmail.com> (raw)
In-Reply-To: <51f3faa71003291915g7a51ee18q8bc64a0ab7023114@mail.gmail.com>

El Mon, 29 Mar 2010 20:15:47 -0600
Robert Hancock <hancockrwd@gmail.com> escribió:
> That sounds similar to a previous report.. Can you CC the thread on
> linux-kernel (if you've seen it)?

Sorry, I am not subscribed.

> Also, what does dmesg show when loading the driver? There should be a
> string showing the chip version, something like this:
<...>

r8169 0000:05:00.0: eth0: RTL8102e at 0xffffc900100be000,
00:26:b9:a0:33:86, XID 04e00000 IRQ 28

Then, after initialization, it shows two "link up" messages, and that's
all it reports. It's a nice blackhole :P.

> On Mon, Mar 29, 2010 at 2:05 AM, Ismael Luceno
> <ismael.luceno@gmail.com> wrote:
> > On 2.6.33 it worked fine, but then I decided to upgrade to
> > 2.6.34-rc2 and it simply didn't detected the carrier correctly
> > anymore (it was like if the cable was always plugged...).
> >
> > After a short inspection, the obvious offender was commit
> > 353176888386d9025062a12dcec08d49af10cf2c.
> >
> > I tried with use_dac=0, but it didn't work (I had no time to
> > investigate it further), but after reverting the commit it worked
> > again.
> >
> > The system is a Dell Inspiron mini 1012, lspci reports:
> > 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
> > Subsystem: Dell Device 041a Flags: bus master, fast devsel, latency
> > 0, IRQ 28 I/O ports at 2000 [size=256]
> >        Memory at f0f20000 (64-bit, prefetchable) [size=4K]
> >        Memory at f0f10000 (64-bit, prefetchable) [size=64K]
> >        [virtual] Expansion ROM at f0f40000 [disabled] [size=128K]
> >        Capabilities: <access denied>
> >        Kernel driver in use: r8169
> >        Kernel modules: r8169
> >

           reply	other threads:[~2010-03-31 12:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <51f3faa71003291915g7a51ee18q8bc64a0ab7023114@mail.gmail.com>]

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=20100331092315.1a5ac86a@gmail.com \
    --to=ismael.luceno@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@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