From: Daniel Drake <dsd@gentoo.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
netdev@vger.kernel.org, stable@kernel.org,
Francois SIMOND <curio@free.fr>
Subject: Re: [PATCH] sky2: re-enable 88E8056 for most motherboards
Date: Sun, 13 May 2007 11:55:29 -0400 [thread overview]
Message-ID: <464734F1.2020103@gentoo.org> (raw)
In-Reply-To: <20070510090010.4c6b8589@freepuppy>
Stephen Hemminger wrote:
> I can use DMI to narrow down to one motherboard.
> Or just let everything through and let user's discover what's unstable, it fails
> relatively quickly.
>
> Could you please get full PCI info lspci -vvxxx for working/non-working 88e8056 (Yukon EC-U)
> systems? It might be some PCI Express setup by the BIOS, but so far haven't
> found any difference that mattered.
I haven't seen any reports of systems affected by the corruption issue
so I can't provide any data there.
Here is the full lspci output for a few systems with 88E8056 devices
that work fine:
Gigabyte P965-S3
http://bugs.gentoo.org/attachment.cgi?id=118827&action=view
Gigabyte P965-S3 (from another user)
http://bugs.gentoo.org/attachment.cgi?id=118848&action=view
Asus P5B deluxe
http://bugs.gentoo.org/attachment.cgi?id=119038&action=view
Daniel
next prev parent reply other threads:[~2007-05-13 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 21:23 [PATCH] sky2: re-enable 88E8056 for most motherboards Stephen Hemminger
2007-05-01 13:58 ` Daniel Drake
2007-05-02 22:42 ` Stephen Hemminger
2007-05-03 19:23 ` Daniel Drake
2007-05-10 16:00 ` Stephen Hemminger
2007-05-13 15:55 ` Daniel Drake [this message]
2007-05-14 19:02 ` Stephen Hemminger
2007-05-17 2:09 ` Daniel Drake
2007-05-17 2:58 ` Jeff Garzik
2007-05-17 3:21 ` Daniel Drake
2007-05-08 5:23 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2007-05-14 1:27 kernel
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=464734F1.2020103@gentoo.org \
--to=dsd@gentoo.org \
--cc=curio@free.fr \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).