From: Steve Kieu <haiquy@yahoo.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Fri, 2 Sep 2005 07:21:10 +1000 (EST) [thread overview]
Message-ID: <20050901212110.19192.qmail@web53605.mail.yahoo.com> (raw)
In-Reply-To: <20050901110913.5d9fba44@dxpl.pdx.osdl.net>
> Is this the correct summary of the problem
> scenarios.
> Assume each one starts from cold boot (power off).
>
> * 2.6.13(skge) boot => Good
> * 2.6.13(sk98lin) boot => Good
> * 2.6.13 + SK version of sk98lin => Good
> * XP boot => Good
XP boot: No good if before 2.6.13 runs on the hardware
and do the normal shuttdown or reboot or power off.
The same for all linux kernel before 2.6.13 (tested
2.6.12, 2.6.11)
>
> Okay, now the cases where one OS is run first and
> a reboot is done to a second, or in the case of
> just Linux, this should be the same as rmmoding on
> driver and modprobing
>
> Second
> First | skge | sk98lin | XP
> skge | OK | BAD | BAD
> sk98lin | ok | OK | ok
> XP | ok | ok | OK
>
a litle bit confusing, just one line to describe it:
If run 2.6.13 and up the NIC, it is working. Shuttdown
or reboot using /sbin/halt (means power completely off
and on) or /sbin/reboot all other OSs failed to enable
the NIC except 2.6.13.
to restore the normal working of the NIC, boot 2.6.13
and do a hot power reset. (press the reset button)
cheers
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
next prev parent reply other threads:[~2005-09-01 21:21 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
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 [this message]
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=20050901212110.19192.qmail@web53605.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=linux-kernel@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®