From: David Miller <davem@davemloft.net>
To: jarkao2@gmail.com
Cc: seraph@xs4all.nl, akpm@linux-foundation.org,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [SPARC64] INO problem Re: [Bug 10273] New: Sun GEM (PCI) - network device doesn't work
Date: Fri, 25 Apr 2008 00:26:36 -0700 (PDT) [thread overview]
Message-ID: <20080425.002636.250010462.davem@davemloft.net> (raw)
In-Reply-To: <20080402182655.GA2739@ami.dom.local>
From: Jarek Poplawski <jarkao2@gmail.com>
Date: Wed, 2 Apr 2008 20:26:55 +0200
> Nice work Jos! I forward it to the author and the lists.
I haven't forgotten about this bug report, in fact I did some
investigation and thinking about it.
I think the case being triggered in the new code is IRQ_DISABLED.
If this is the problem, I suspect that what needs to happen is that
when we re-enable the interrupt we have to forcefully hit the clear
register to put it back into transmit state. Otherwise it can
get stuck.
Please give this patch a try (this is against 2.6.23, which is the
version you reported the bug against, let me know if another version
is more convenient).
Thanks!
diff --git a/arch/sparc64/kernel/irq.c b/arch/sparc64/kernel/irq.c
index 2395609..98b68d2 100644
--- a/arch/sparc64/kernel/irq.c
+++ b/arch/sparc64/kernel/irq.c
@@ -313,6 +313,8 @@ static void sun4u_irq_enable(unsigned int virt_irq)
IMAP_AID_SAFARI | IMAP_NID_SAFARI);
val |= tid | IMAP_VALID;
upa_writeq(val, imap);
+
+ upa_writeq(ICLR_IDLE, data->iclr);
}
}
next prev parent reply other threads:[~2008-04-25 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10273-10286@http.bugzilla.kernel.org/>
2008-03-17 21:36 ` [Bugme-new] [Bug 10273] New: Sun GEM (PCI) - network device doesn't work Andrew Morton
2008-04-02 18:26 ` Fwd: [SPARC64] INO problem " Jarek Poplawski
2008-04-10 10:30 ` David Miller
2008-04-25 7:26 ` David Miller [this message]
2008-04-25 19:59 ` Jos van der Ende
2008-04-25 20:35 ` David Miller
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=20080425.002636.250010462.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=seraph@xs4all.nl \
/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).