From: "J�rn Engel" <joern@dublin.logfs.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2)
Date: Mon, 15 Mar 2010 16:10:41 +0100 [thread overview]
Message-ID: <20100315151041.GA15667@Dublin.logfs.org> (raw)
In-Reply-To: <20100315150806.GA15354@Dublin.logfs.org>
Forgot to Cc: lkml.
On Mon, 15 March 2010 16:08:06 +0100, J�rn Engel wrote:
>
> Hello Robert!
>
> Looks like 353176888386d9025062a12dcec08d49af10cf2c broke one of my
> machines. Reverting that patch fixes things again. Machine is
> running an x86_64 kernel. Lspci gives me this:
>
> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
> Subsystem: ASRock Incorporation Device 8136
> Flags: bus master, fast devsel, latency 0, IRQ 26
> I/O ports at e800 [size=256]
> Memory at fdeff000 (64-bit, prefetchable) [size=4K]
> Memory at fdee0000 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at fde00000 [disabled] [size=128K]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Endpoint, MSI 01
> Capabilities: [ac] MSI-X: Enable- Count=2 Masked-
> Capabilities: [cc] Vital Product Data
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [140] Virtual Channel <?>
> Capabilities: [160] Device Serial Number 08-00-00-00-ff-ff-00-00
> Kernel driver in use: r8169
>
> If you have any test patches to try, please send them my way. :)
>
> J�rn
next parent reply other threads:[~2010-03-15 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100315150806.GA15354@Dublin.logfs.org>
2010-03-15 15:10 ` J�rn Engel [this message]
2010-03-15 18:57 ` [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2) David Miller
2010-03-15 23:28 ` Robert Hancock
2010-03-16 8:35 ` J�rn Engel
2010-03-16 23:30 ` Robert Hancock
2010-03-16 23:40 ` David Miller
2010-03-26 0:56 ` Robert Hancock
2010-03-26 3:29 ` David Miller
2010-03-26 9:12 ` J�rn Engel
2010-03-27 1:55 ` Robert Hancock
2010-03-27 6:38 ` J�rn Engel
2010-03-27 17:46 ` Robert Hancock
2010-03-27 22:00 ` J�rn Engel
2010-03-27 11:57 ` =?unknown-8bit?B?RnJhbsOnb2lz?= Romieu
2010-03-17 20:52 ` Francois Romieu
2010-03-18 9:03 ` J�rn Engel
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=20100315151041.GA15667@Dublin.logfs.org \
--to=joern@dublin.logfs.org \
--cc=davem@davemloft.net \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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