From: Grant Grundler <grundler@parisc-linux.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: Grant Grundler <grundler@parisc-linux.org>,
netdev@vger.kernel.org, kyle@mcmartin.ca
Subject: Re: tulip_rxtx_stop() on Cobalt Qube2
Date: Sun, 31 May 2009 17:43:42 -0600 [thread overview]
Message-ID: <20090531234342.GD3291@lackof.org> (raw)
In-Reply-To: <200905312302.22608.florian@openwrt.org>
On Sun, May 31, 2009 at 11:02:22PM +0200, Florian Fainelli wrote:
> Hi Grant,
...
> > The RX/TX engines are in a wedged state to begin with. :(
>
> I suppose this is due to the Bootloader, either CoLo or the original Cobalt
> microservers bootloader.
Yeah - either bootloader or BIOS - whatever talked to the NIC most recently.
...
> > I have not tested or even compiled this patch...will do so on parisc/ia64
> > machines once I get some feedback on this patch.
> >
> > And I just noticed pci_clear_master() is not called *anywhere*. :(
> > Need to add such a call after tulip_stop_rxtx() some place (many places?).
> > This patch is just RFC and not suitable for merging upstream.
>
> The patch below does not help on my Qube2, I am still having the same message
> appearing.
Are you sure?
I thought I removed all calls to tulip_stop_rxtx() in the initialization
code path and didn't think it would get called. Did I overlook one?
Can you add "dump_stack()" to tulip_stop_rxtx() failure case?
Can you also modify the driver version to make sure you are using
the correct/most recenly built module?
And the please post the dmesg output from the driver again (plus 10
lines of output before and after).
thanks,
grant
next prev parent reply other threads:[~2009-05-31 23:43 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
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 [this message]
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=20090531234342.GD3291@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).