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: Thu, 08 Aug 2002 08:32:15 -0700 (PDT) [thread overview]
Message-ID: <20020808.083215.41828271.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208081431210.4739-100000@pc40.e18.physik.tu-muenchen.de>
From: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Date: Thu, 8 Aug 2002 14:39:56 +0200 (CEST)
If I can do more to help sort this out, please tell me. With my fix to
prefix every write with a dummy read, the system is rock solid, not a
single glitch on 12 machines in the last 14 hours.
I'll figure out why this indirect register stuff isn't working.
I'm very curious on how this all works, so would somebody please give me a
pointer where to start reading concerning linux and PCI
reordering/pci_write_config_dword?
The PCI controller might be illegally reordering PCI MEM space
accesses to the card's registers with asynchronous DMA activity.
If that is true, the explanation is that the PCI config space
accesses synchrnoize wrt. pending DMA operations the device is
doing.
next prev parent reply other threads:[~2002-08-08 15:41 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
2002-08-08 8:33 ` Roland Kuhn
2002-08-08 12:39 ` Roland Kuhn
2002-08-08 15:32 ` David S. Miller [this message]
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=20020808.083215.41828271.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