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: Thu, 10 Dec 2009 07:09:06 +0200 [thread overview]
Message-ID: <4B208272.4050808@embedded-sol.com> (raw)
In-Reply-To: <20091210023136.GA31107@xw6200.broadcom.net>
Hi, Matt
Matt Carlson wrote:
> On Wed, Dec 09, 2009 at 05:45:36PM -0800, Felix Radensky wrote:
>
>> Hi, Matt
>>
>> Matt Carlson wrote:
>>
>>> I understand the problem now. The problem is that tg3_set_power_state()
>>> puts the phy into a low-power mode when it releases the device. When
>>> the phy is reacquired, a phy reset is missing to take the device back
>>> out of the low-power mode.
>>>
>>> The patch at the bottom of this email is the fix I'm currently testing.
>>> If you wish, you can try it out.
>>>
>>>
>>>
>> Thanks a lot for the fix, I'll ask the guys with access to hardware to
>> test it.
>>
>> The problem with lost link happened to me when link was synchronized
>> at 1000Mbit/sec. At 100Mbit/sec, ifdown would result in the following
>> soft lockup:
>>
>> BUG: soft lockup - CPU#0 stuck for 61s! [events/0:5]
>> Modules linked in: ehci_hcd usbcore
>> NIP: c0191f0c LR: c018774c CTR: c0191f04
>> REGS: ef83fe60 TRAP: 0901 Not tainted (2.6.31)
>> MSR: 00029000 <EE,ME,CE> CR: 24022084 XER: 00000000
>> TASK = ef8312c0[5] 'events/0' THREAD: ef83e000
>> GPR00: f1040000 ef83ff10 ef8312c0 ef8292c0 00000400 00c04808 00000000
>> 00000000
>> GPR08: 00000000 00000000 00000006 00c04800 44024084
>> NIP [c0191f0c] tg3_read32+0x8/0x18
>> LR [c018774c] _tw32_flush+0x94/0xa4
>> Call Trace:
>> [ef83ff10] [ef8314b8] 0xef8314b8 (unreliable)
>> [ef83ff30] [c0192074] tg3_adjust_link+0x98/0x24c
>> [ef83ff50] [c017eab0] phy_state_machine+0xd4/0x5b8
>> [ef83ff70] [c0037570] worker_thread+0x124/0x1b8
>> [ef83ffc0] [c003b5fc] kthread+0x78/0x7c
>> [ef83fff0] [c000f584] kernel_thread+0x4c/0x68
>>
>> Can you reproduce this ?
>>
>> Thanks a lot for your help.
>>
>
> Is this with the "Fix phylib locking strategy" patch in place?
>
>
Yes, this is with tg3.c and broadcom.c from 2.6.32. The hang occurs on
read from EMAC Mode register.
Felix.
next prev parent reply other threads:[~2009-12-10 5:09 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 [this message]
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
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=4B208272.4050808@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).