netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Michael Chan <mchan@broadcom.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: tg3: link is permanently down after ifdown and ifup
Date: Mon, 04 Jan 2010 15:41:28 +0200	[thread overview]
Message-ID: <4B41F008.6070404@embedded-sol.com> (raw)
In-Reply-To: <4B2FEE16.2020808@embedded-sol.com>

Hi, Matt

Felix Radensky wrote:
> Hi, Matt
>
> Matt Carlson wrote:
>>>
>>> There was another problem in 2.6.32 that I reported, namely kernel 
>>> soft lockup
>>> when link is synchronized at 100Mbit/sec and tg3 with 57780 goes 
>>> down . Were
>>> you able to reproduce it ?
>>>     
>>
>> No, but perhaps I don't understand the problem well enough.  Are you
>> saying that you encounter the problem when you run
>> 'ifconfig bcm57780 down', or is it that losing link itself causes the
>> problem?
>>
>>   
> It is enough to connect the NIC to 10/100 switch and run 'ifconfig 
> ethX down' to reproduce
> the problem.
>
Did you have a chance to look into this ?

Thanks.

Felix.

      reply	other threads:[~2010-01-04 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 15:16 tg3: link is permanently down after ifdown and ifup Felix Radensky
2009-11-19 16:08 ` Felix Radensky
2009-11-19 22:50   ` Michael Chan
2009-11-21 11:03     ` Felix Radensky
2009-12-09  8:43     ` Felix Radensky
2009-12-10  1:19       ` Matt Carlson
2009-12-10  1:45         ` Felix Radensky
2009-12-10  2:31           ` Matt Carlson
2009-12-10  5:09             ` Felix Radensky
2009-12-20 16:44         ` Felix Radensky
2009-12-21 18:19           ` Matt Carlson
2009-12-21 21:52             ` Felix Radensky
2010-01-04 13:41               ` Felix Radensky [this message]

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=4B41F008.6070404@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=mcarlson@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.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).