From: "David S. Miller" <davem@redhat.com>
To: rkuhn@e18.physik.tu-muenchen.de
Cc: kwijibo@zianet.com, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at tg3.c:1557
Date: Wed, 07 Aug 2002 15:40:04 -0700 (PDT) [thread overview]
Message-ID: <20020807.154004.104177403.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208080007300.4058-100000@pc40.e18.physik.tu-muenchen.de>
From: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Date: Thu, 8 Aug 2002 00:10:31 +0200 (CEST)
Since the insertion of a dummy write solved the problem, I would say it's
the chipset's PCI reordering, which is malfunctioning in the 2466.
Roland can you retry using this patch? The difference from
my previous one is that when we use the indirect register
writing of the mailbox registers, we offset into the GRCMBOX
area of the chip registers.
This seems to be how Broadcom's driver does indirect accesses
to mailbox registers.
--- drivers/net/tg3.c.~1~ Wed Aug 7 15:42:34 2002
+++ drivers/net/tg3.c Wed Aug 7 15:45:56 2002
@@ -173,8 +173,23 @@
}
}
+static void tg3_write_indirect_mbox(struct tg3 *tp, u32 off, u32 val)
+{
+ if (/*XXX*/ 1 || (tp->tg3_flags & TG3_FLAG_PCIMEM_ORDERING_HWBUG) != 0) {
+ unsigned long flags;
+
+ spin_lock_irqsave(&tp->indirect_lock, flags);
+ pci_write_config_dword(tp->pdev, TG3PCI_REG_BASE_ADDR,
+ off + 0x5600);
+ pci_write_config_dword(tp->pdev, TG3PCI_REG_DATA, val);
+ spin_unlock_irqrestore(&tp->indirect_lock, flags);
+ } else {
+ writel(val, tp->regs + off);
+ }
+}
+
#define tw32(reg,val) tg3_write_indirect_reg32(tp,(reg),(val))
-#define tw32_mailbox(reg, val) writel(((val) & 0xffffffff), tp->regs + (reg))
+#define tw32_mailbox(reg, val) tg3_write_indirect_mbox(tp,(reg),(val))
#define tw16(reg,val) writew(((val) & 0xffff), tp->regs + (reg))
#define tw8(reg,val) writeb(((val) & 0xff), tp->regs + (reg))
#define tr32(reg) readl(tp->regs + (reg))
--- drivers/net/tg3.h.~1~ Wed Aug 7 15:44:04 2002
+++ drivers/net/tg3.h Wed Aug 7 15:44:30 2002
@@ -1740,7 +1740,8 @@
#define TG3_FLAG_POLL_SERDES 0x00000080
#define TG3_FLAG_PHY_RESET_ON_INIT 0x00000100
#define TG3_FLAG_PCIX_TARGET_HWBUG 0x00000200
-#define TG3_FLAG_WOL_SPEED_100MB 0x00000400
+#define TG3_FLAG_PCIMEM_ORDERING_HWBUG 0x00000400
+#define TG3_FLAG_WOL_SPEED_100MB 0x00000800
#define TG3_FLAG_WOL_ENABLE 0x00001000
#define TG3_FLAG_NVRAM 0x00002000
#define TG3_FLAG_NVRAM_BUFFERED 0x00004000
next prev parent reply other threads:[~2002-08-07 22:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 11:40 kernel BUG at tg3.c:1557 Roland Kuhn
2002-08-07 13:14 ` Alan Cox
2002-08-07 12:03 ` David S. Miller
2002-08-07 14:25 ` Roland Kuhn
2002-08-07 14:20 ` David S. Miller
2002-08-07 14:49 ` Roland Kuhn
2002-08-07 14:48 ` David S. Miller
2002-08-07 15:36 ` Roland Kuhn
2002-08-07 15:24 ` David S. Miller
2002-08-07 16:28 ` Roland Kuhn
2002-08-07 19:18 ` [SOLVED] " Roland Kuhn
2002-08-07 19:43 ` Roland Kuhn
2002-08-07 12:22 ` kernel
2002-08-07 13:08 ` Willy Tarreau
2002-08-07 19:52 ` kwijibo
2002-08-07 19:53 ` Roland Kuhn
2002-08-07 21:41 ` kwijibo
2002-08-07 22:10 ` Roland Kuhn
2002-08-07 22:40 ` David S. Miller [this message]
2002-08-08 8:33 ` Roland Kuhn
2002-08-08 12:39 ` Roland Kuhn
2002-08-08 15:32 ` David S. Miller
2002-08-30 23:43 ` David S. Miller
2002-09-11 9:11 ` Roland Kuhn
2002-09-18 13:57 ` Ryan Sweet
2002-08-07 23:42 ` Alan Cox
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=20020807.154004.104177403.davem@redhat.com \
--to=davem@redhat.com \
--cc=kwijibo@zianet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuhn@e18.physik.tu-muenchen.de \
/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