From: Jarek Poplawski <email@example.com>
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
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).
diff --git a/arch/sparc64/kernel/irq.c b/arch/sparc64/kernel/irq.c
index 2395609..98b68d2 100644
@@ -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(ICLR_IDLE, data->iclr);
I applied the patch against 2.6.24-gentoo-r4, the current kernel on this machine. It worked fine, with only an offset of 12 lines. Nothing unusual during compile either.
The first results are hopeful: I am no longer able to trigger this bug by loading sym53c8xx before sungem, nor by having them both loaded by udev. Nothing odd in dmesg and the machine is completely functional.
I don't have much time for testing today, but if desired I will gladly do some more testing tomorrow or Sunday.
Jos van der Ende <firstname.lastname@example.org>