From: Steve Kieu <haiquy@yahoo.com>
To: Stephen Hemminger <shemminger@osdl.org>,
Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Daniel Drake <dsd@gentoo.org>, Steve Kieu <haiquy@yahoo.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Wed, 31 Aug 2005 06:50:27 +1000 (EST) [thread overview]
Message-ID: <20050830205027.59306.qmail@web53609.mail.yahoo.com> (raw)
In-Reply-To: <20050830133918.42444cae@dxpl.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Ok, I reproduce the problem and attached several lspci
log here
--- Stephen Hemminger <shemminger@osdl.org> wrote:
> On Tue, 30 Aug 2005 13:18:57 -0700
> Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:
>
> > on 2.6.11/12 when it isn't working maybe you
> should send us the output
> > of lspci -vvv
> >
> > just a hint, I'm guessing its power management
> related, and / or
> > something to do with the pci bus code.
>
> Also, the dmesg output with skge driver will show
> chip version and revision.
> The problem is obviously some of the chip
> initialization that is complex
> with the Marvell chips. Something is probably
> missing. There was a fix
> in the latest 2.6.13 that is probably related:
>
>
>
http://www.mail-archive.com/netdev@vger.kernel.org/msg00438.html
>
S.KIEU
____________________________________________________
Do you Yahoo!?
The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database.
http://au.movies.yahoo.com
[-- Attachment #2: 2772971102-dmesg-2.6.12-nowork.log.gz --]
[-- Type: application/x-gzip, Size: 5927 bytes --]
[-- Attachment #3: 3668832883-dmesg-2613.log.gz --]
[-- Type: application/x-gzip, Size: 4868 bytes --]
[-- Attachment #4: 3470857198-lspci-2612-nowork.log.gz --]
[-- Type: application/x-gzip, Size: 2012 bytes --]
[-- Attachment #5: 1122749440-lspci-2613.log.gz --]
[-- Type: application/x-gzip, Size: 1672 bytes --]
[-- Attachment #6: 267994485-lspci-2612-work.log.gz --]
[-- Type: application/x-gzip, Size: 1672 bytes --]
next prev parent reply other threads:[~2005-08-30 20:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 8:35 Steve Kieu
2005-08-30 9:56 ` Daniel Drake
2005-08-30 9:58 ` Steve Kieu
2005-08-30 10:18 ` Daniel Drake
2005-08-30 10:24 ` Steve Kieu
2005-08-30 10:52 ` Steve Kieu
2005-08-30 11:54 ` Daniel Drake
2005-08-30 12:29 ` Steve Kieu
2005-08-30 13:31 ` Daniel Drake
2005-08-30 20:18 ` Jesse Brandeburg
2005-08-30 20:39 ` Stephen Hemminger
2005-08-30 20:50 ` Steve Kieu [this message]
2005-08-30 21:05 ` Stephen Hemminger
2005-08-30 21:49 ` Steve Kieu
2005-08-30 22:29 ` Stephen Hemminger
2005-08-31 0:09 ` Steve Kieu
2005-09-01 17:59 ` Stephen Hemminger
2005-08-31 9:56 ` Daniel Drake
2005-09-01 18:09 ` Stephen Hemminger
2005-09-01 21:21 ` Steve Kieu
2005-09-01 21:45 ` Howard Chu
2005-09-11 15:24 ` Daniel Drake
2005-09-11 18:12 ` Kalin KOZHUHAROV
2005-09-12 16:01 ` Kalin KOZHUHAROV
2005-09-12 16:50 ` Daniel Drake
2005-09-12 17:34 ` Kalin KOZHUHAROV
2005-09-12 0:02 ` Steve Kieu
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=20050830205027.59306.qmail@web53609.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=dsd@gentoo.org \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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®