From: "Michael Chan" <mchan@broadcom.com>
To: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>
Cc: "netdev" <netdev@vger.kernel.org>
Subject: Re: tg3 does not want to go up (config space problems).
Date: Mon, 14 May 2007 10:15:23 -0700 [thread overview]
Message-ID: <1179162923.25622.22.camel@dell> (raw)
In-Reply-To: <20070514145419.GA19679@2ka.mipt.ru>
On Mon, 2007-05-14 at 18:54 +0400, Evgeniy Polyakov wrote:
> I've cought a problem with my laptop and tg3 driver.
> Suddenly (it was turned off quite for a while) tg3 driver does not start
> up.
>
> Here is dmesg messages (copied by hand, some bits are ommitted):
> acpi: ... // device enbaled in couple of words
>
> eth0: Tigon3 [partno(BMC5705mA3) rev 3003 PHY(5705)] pci:33/32, 10/100
>
> eth0: rxcsum[1] linkchgreg[0] miirq[0] asf[0] split[0] wirespeed[0]
> tsocap[1]
> eth0: dma_rwctrl[763f0000] dma_mask[64 bit]
>
> PM: writing back config space on device /* tg3 device pcix id*/ at
> offset b (was 165d14e4, writing 890103c)
> offset 3 (was 0, writing 4010)
> offset 2 (was 2000000, writing 2000003)
> offset 1 (was 2b00000, writing 2b00006)
> offset 0 (was 165d14e4, writing 165e14e4)
These messages are harmless. The way the driver saves and restores the
pci state cause these benign messages to appear.
>
> ADDRCONF(NETDEV_UP): eth0 link is not ready
>
> This problem never happend before, but suddenly appeared after quite
> long suspend to disk (several month I think).
> Nothing was changed in hardware.
> Both 2.6.18 and 2.6.21-rc3 have the same issue.
> No interrupts reported in /proc/interrupts.
I'll look into this. Thanks.
>
> I have 2.6.21-rc3 source tree in laptop, so can apply patches by hand
> reading them from main desktop, but can not (easily) install additional
> software.
>
> Thanks.
>
next prev parent reply other threads:[~2007-05-14 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 14:54 tg3 does not want to go up (config space problems) Evgeniy Polyakov
2007-05-14 15:26 ` Evgeniy Polyakov
2007-05-14 17:15 ` Michael Chan [this message]
2007-05-14 19:20 ` Michael Chan
2007-05-15 4:16 ` Evgeniy Polyakov
2007-06-30 18:30 ` Evgeniy Polyakov
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=1179162923.25622.22.camel@dell \
--to=mchan@broadcom.com \
--cc=johnpol@2ka.mipt.ru \
--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).