From: Grant Grundler <grundler@parisc-linux.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: netdev@vger.kernel.org, grundler@parisc-linux.org, kyle@mcmartin.ca
Subject: Re: tulip_rxtx_stop() on Cobalt Qube2
Date: Sun, 3 May 2009 05:32:09 -0600 [thread overview]
Message-ID: <20090503113209.GC6617@lackof.org> (raw)
In-Reply-To: <200905011238.59345.florian@openwrt.org>
On Fri, May 01, 2009 at 12:38:57PM +0200, Florian Fainelli wrote:
> Hi Grant, Kyle,
>
> I just updated my Qube2 to run a 2.6.30-rc2-00476-gd678033 kernel (also seen
> on a 2.6.29-rc2-00462-gfa04b54) and I get the following message while booting
> the box now, I have not git bisected the offending commit yet :
>
> [snip]
> Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
> PCI: Enabling device 0000:00:07.0 (0045 -> 0047)
> tulip0: Old format EEPROM on 'Cobalt Microserver' board. Using substitute
> media control info.
> tulip0: EEPROM default media type Autosense.
> tulip0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
> tulip0: MII transceiver #1 config 1000 status 7809 advertising 01e1.
> eth0: Digital DS21142/43 Tulip rev 65 at MMIO 0x12082000, 00:10:e0:00:7d:1f,
> IRQ 19.
> PCI: Enabling device 0000:00:0c.0 (0005 -> 0007)
> tulip1: Old format EEPROM on 'Cobalt Microserver' board. Using substitute
> media control info.
> tulip1: EEPROM default media type Autosense.
> tulip1: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
> tulip1: MII transceiver #1 config 1000 status 7809 advertising 01e1.
> eth1: Digital DS21142/43 Tulip rev 65 at MMIO 0x12082400, 00:10:e0:00:88:b9,
> IRQ 20.
> [snip]
> 0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xf0660000 CSR6 0xb20e2202)
I added the additional output. I'll need to grab the manuals and
look up the bits.
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
>
> The interface is still fully functional, shall we increase the timeount in
> tulip_stop_rxtx() to prevent this message from appearing ?
I expect the timeout (1.3ms) is long enough to cover "normal" cases.
If something is taking longer than "normal", I'd like to know.
If increasing it to 1.5 or 2ms makes this go away, I don't
think I'll object.
hth,
grant
>
> Thanks a lot in advance for your answer.
> --
> Best regards, Florian Fainelli
> Email : florian@openwrt.org
> http://openwrt.org
> -------------------------------
next prev parent reply other threads:[~2009-05-03 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 10:38 tulip_rxtx_stop() on Cobalt Qube2 Florian Fainelli
2009-05-03 11:32 ` Grant Grundler [this message]
2009-05-03 19:45 ` Florian Fainelli
2009-05-31 1:40 ` Grant Grundler
2009-05-31 21:02 ` Florian Fainelli
2009-05-31 23:43 ` Grant Grundler
2009-06-07 18:27 ` Florian Fainelli
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=20090503113209.GC6617@lackof.org \
--to=grundler@parisc-linux.org \
--cc=florian@openwrt.org \
--cc=kyle@mcmartin.ca \
--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).