All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: shemminger@osdl.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: Tue, 30 Aug 2005 13:18:57 -0700	[thread overview]
Message-ID: <4807377b05083013185767744a@mail.gmail.com> (raw)
In-Reply-To: <43145FB5.6080300@gentoo.org>

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.

On 8/30/05, Daniel Drake <dsd@gentoo.org> wrote:
> Forwarding on, please reply-to-all in future.
> 
> Steve Kieu wrote:
> > Hi all,
> >
> > I have "fixed" the problem in a very wierd way.Reading
> > your post I thought maybe when removing the driver
> > itself it set some bit incorrectly. Then I decided to
> > do:
> >
> > Boot with init=/bin/bash  so bypass all other things.
> > modprobe skge
> >
> > run ifconfig eth0 ip_num  up
> >
> >
> > ping  a host
> >
> > then while pinging hit Ctrl+Alt+Del key to hot reboot
> > the system.
> >
> > I still see the light at the hub lits. Now I boot to
> > winXP and as I expected , it worked!
> >
> > No I boot 2.6.11 and it worked, so the problem resolve
> > but I am tooooo scared to run 2613 now :-)
> >
> > Hope this information helps debuging the driver.
> >
> > Thanks.
> >
> > S.KIEU
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2005-08-30 20:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  8:35 Very strange Marvell/Yukon Gigabit NIC networking problems 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 [this message]
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
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=4807377b05083013185767744a@mail.gmail.com \
    --to=jesse.brandeburg@gmail.com \
    --cc=dsd@gentoo.org \
    --cc=haiquy@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.