From: Francois Romieu <romieu@fr.zoreil.com>
To: "J�rn Engel" <joern@dublin.logfs.org>
Cc: Robert Hancock <hancockrwd@gmail.com>,
David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2)
Date: Wed, 17 Mar 2010 21:52:06 +0100 [thread overview]
Message-ID: <20100317205206.GA2699@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20100316083501.GA3489@Dublin.logfs.org>
On Tue, Mar 16, 2010 at 09:35:01AM +0100, J�rn Engel wrote:
[...]
> I just noticed lspci is also unhappy.
>
> With patch in:
> Bikini:~# lspci -vv > lspci
> pcilib: sysfs_read_vpd: read failed: Connection timed out.
>
> With patch reverted:
> Bikini:~# lspci -vv > lspci2
> Bikini:~# diff -u lspci*
> --- lspci 2010-03-16 09:03:02.000000000 +0100
> +++ lspci2 2010-03-16 09:09:36.000000000 +0100
> @@ -246,7 +246,7 @@
> Vector table: BAR=4 offset=00000000
> PBA: BAR=4 offset=00000800
> Capabilities: [cc] Vital Product Data
> - Not readable
> + Unknown small resource type 00, will not decode more.
Neither looks good.
Did lspci output look different with an older kernel ?
--
Ueimor
next prev parent reply other threads:[~2010-03-17 21:00 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
2010-03-15 18:57 ` 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 [this message]
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=20100317205206.GA2699@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=davem@davemloft.net \
--cc=hancockrwd@gmail.com \
--cc=joern@dublin.logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®