From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Alessandro Morelli <alex@alphac.it>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH,CFT] Tentative fix for agpgart (writing on 'reserved' bits)
Date: Thu, 30 May 2002 11:41:38 +0200 [thread overview]
Message-ID: <3CF5F3D2.3020505@epfl.ch> (raw)
In-Reply-To: <fa.mm4ng1v.vmenaj@ifi.uio.no> <fa.gciunnv.cnaf99@ifi.uio.no> <3CF1EA3F.4070608@epfl.ch> <1022493086.11859.191.camel@irongate.swansea.linux.org.uk> <3CF1F4C0.5080201@epfl.ch> <1022494620.11859.207.camel@irongate.swansea.linux.org.uk> <3CF1FD4B.8060608@epfl.ch> <1022497386.11859.232.camel@irongate.swansea.linux.org.uk> <3CF205C1.6040408@epfl.ch> <1022498304.11859.239.camel@irongate.swansea.linux.org.uk> <3CF2144C.709@epfl.ch> <1022509981.11859.284.camel@irongate.swansea.linux.org.uk> <5.1.0.14.0.20020528103408.02ab1260@shiva.intra.alphac.it> <5.1.0.14.0.20020530110655.02afbb20@shiva.intra.alphac.it>
Alessandro Morelli wrote:
>
> Hello
> I managed to get rid of customers, in order to test the patches....
> Bad news...no change...
At least it is not worse (I hope ...) ;-)
> I'm starting to believe I'm mad...my PC works like charm without AGP and
> gets all mixed when I enabled it...
Does it start messing right after you enable it, or only after you write
to it (starting X...) ?
> What kind of information can I provide (/proc readings, tests, etc.) to
> shed some light?
>
> Could this be a case of interaction between AGP and VM?
>
> tlb-flush weirdness?
>
Apart from this kinda usual write-on-reserved-bits in the AGP
initialization, which has been done before on various chipsets and
almost never caused any trouble, I saw no blatant errors that may lead
to such things... In fact, we have several PCs with i815 chipsets in the
lab. People are using AGP without any troubles. The only difference is
that we run an old kernel version (2.4.3-13, thanks the sysadmin for
never upgrading....), and we have a different graphic card (Matrox).
Alan, do you have any idea about this one ?
Best regards
--
Nicolas Aspert Signal Processing Institute (ITS)
Swiss Federal Institute of Technology (EPFL)
prev parent reply other threads:[~2002-05-30 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.mm4ng1v.vmenaj@ifi.uio.no>
[not found] ` <fa.gciunnv.cnaf99@ifi.uio.no>
2002-05-27 8:11 ` PROBLEM: memory corruption with i815 chipset variant Nicolas Aspert
2002-05-27 9:51 ` Alan Cox
2002-05-27 8:56 ` Nicolas Aspert
2002-05-27 10:17 ` Alan Cox
2002-05-27 9:32 ` [PATCH,CFT] Tentative fix for mem. corruption caused by intel 815 AGP Nicolas Aspert
2002-05-27 11:03 ` Alan Cox
2002-05-27 10:09 ` Nicolas Aspert
[not found] ` <1022498304.11859.239.camel@irongate.swansea.linux.org.uk>
2002-05-27 11:11 ` Nicolas Aspert
2002-05-27 14:33 ` Alan Cox
2002-05-27 14:08 ` [PATCH,CFT] Tentative fix for agpgart (writing on 'reserved' bits) Nicolas Aspert
[not found] ` <5.1.0.14.0.20020528103408.02ab1260@shiva.intra.alphac.it>
[not found] ` <5.1.0.14.0.20020530110655.02afbb20@shiva.intra.alphac.it>
2002-05-30 9:41 ` Nicolas Aspert [this message]
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=3CF5F3D2.3020505@epfl.ch \
--to=nicolas.aspert@epfl.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alex@alphac.it \
--cc=linux-kernel@vger.kernel.org \
/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