From: Arjan van de Ven <arjanv@redhat.com>
To: Eitan Ben-Nun <eitan@sangate.com>
Cc: linux-kernel@vger.kernel.org, Uri Lublin <uri@sangate.com>
Subject: Re: Adpter card read old memory value
Date: 01 Oct 2002 14:56:47 +0200 [thread overview]
Message-ID: <1033477007.2672.0.camel@localhost.localdomain> (raw)
In-Reply-To: <B71796881E0DF7409F066FE6656BDF2906F78A@beasley>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Tue, 2002-10-01 at 14:43, Eitan Ben-Nun wrote:
> This seems like a cache coherency problem:
> An adapter card on the pci bus send a message to pc i386 Linux to update a memory address.
> Then it reads the address and sees an old value, even though the pc cpu have performed an update to this memory address.
uhm your report is missing a pointer to the source of the driver so
nobody can help you by looking at what's going on....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-01 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 12:43 Adpter card read old memory value Eitan Ben-Nun
2002-10-01 12:56 ` Arjan van de Ven [this message]
[not found] <B71796881E0DF7409F066FE6656BDF2906F78B@beasley>
2002-10-01 14:45 ` Arjan van de Ven
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=1033477007.2672.0.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=eitan@sangate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uri@sangate.com \
/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