From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Daniel Drake <dsd@gentoo.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: Thu, 10 May 2007 09:00:10 -0700 [thread overview]
Message-ID: <20070510090010.4c6b8589@freepuppy> (raw)
In-Reply-To: <46374784.7010401@gentoo.org>
On Tue, 01 May 2007 09:58:28 -0400
Daniel Drake <dsd@gentoo.org> wrote:
> Hi Stephen,
>
> Stephen Hemminger wrote:
> > This fixes the regression in 2.6.21 for users with 88e8056 on motherboard.
> > Allow all but the Gigabyte motherboard has some unresolved bus problems.
>
> > + /* Some Gigabyte motherboards have 88e8056 but cause problems
> > + * There is some unresolved hardware related problem that causes
> > + * descriptor errors and receive data corruption.
> > + */
> > + if (pdev->vendor == PCI_VENDOR_ID_MARVELL &&
> > + pdev->device == 0x4364 && pdev->subsystem_vendor == 0x1458) {
> > + dev_err(&pdev->dev,
> > + "88E8056 on Gigabyte motherboards not supported\n");
>
> Gentoo have reports of sky2 working fine on Gigabyte boards which have
> 88E8056 devices:
> https://bugs.gentoo.org/show_bug.cgi?id=176219
>
> Can the patch be refined further?
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.
Have tried newer BIOS and qualified memory as obvious first steps.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-05-10 16:02 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 [this message]
2007-05-13 15:55 ` Daniel Drake
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=20070510090010.4c6b8589@freepuppy \
--to=shemminger@linux-foundation.org \
--cc=curio@free.fr \
--cc=dsd@gentoo.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.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).