From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: akpm@zip.com.au, reid.hekman@ndsu.nodak.edu,
linux-kernel@vger.kernel.org, alan@lxorg.ukuu.org
Subject: Re: Athlon PSE/AGP Bug
Date: Tue, 22 Jan 2002 01:39:09 +0100 [thread overview]
Message-ID: <20020122013909.N8292@athlon.random> (raw)
In-Reply-To: <20020121.053724.124970557.davem@redhat.com> <20020121175410.G8292@athlon.random> <3C4C5B26.3A8512EF@zip.com.au> <20020121.142320.123999571.davem@redhat.com>
In-Reply-To: <20020121.142320.123999571.davem@redhat.com>; from davem@redhat.com on Mon, Jan 21, 2002 at 02:23:20PM -0800
On Mon, Jan 21, 2002 at 02:23:20PM -0800, David S. Miller wrote:
> From: Andrew Morton <akpm@zip.com.au>
> Date: Mon, 21 Jan 2002 10:17:10 -0800
>
> Andrea Arcangeli wrote:
> > I think this is a very very minor issue, I doubt anybody ever triggered
> > it in real life with linux.
>
> It is said that the crashes cease when the `nopentium' option
> is used, so it does appear that something is up.
>
> I does seem that the nVidia driver is usually involved.
>
> I think this is all "just so happens" personally, and all the that
> turning off the large pages really does is change the timings so that
> whatever bug is really present simply becomes a heisenbug.
My same wondering, however I wasn't sure how much the timing could
really change to make the kernel bugs trigger.
Andrea
next prev parent reply other threads:[~2002-01-22 0:38 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 10:53 Athlon PSE/AGP Bug Reid Hekman
2002-01-21 13:37 ` David S. Miller
2002-01-21 13:50 ` Arjan van de Ven
2002-01-21 16:58 ` jepler
2002-01-21 17:26 ` Ed Sweetman
2002-01-21 22:14 ` David S. Miller
2002-01-21 16:54 ` Andrea Arcangeli
2002-01-21 17:57 ` Reid Hekman
2002-01-21 18:17 ` Andrew Morton
2002-01-21 19:11 ` Harold Campbell
2002-01-21 22:23 ` David S. Miller
2002-01-22 0:39 ` Andrea Arcangeli [this message]
2002-01-22 1:08 ` David S. Miller
2002-01-22 7:05 ` Ville Herva
2002-01-22 7:08 ` David S. Miller
2002-01-22 8:05 ` Daniel Robbins
2002-01-22 0:26 ` Stuart Young
2002-01-22 0:36 ` Steve Brueggeman
2002-01-22 1:02 ` Steve Brueggeman
2002-01-22 20:13 ` Florian Weimer
2002-01-22 22:14 ` Ed Sweetman
2002-01-22 22:52 ` Steve Brueggeman
2002-01-22 23:49 ` Rik van Riel
2002-01-23 0:36 ` Stuart Young
2002-01-23 1:20 ` Rene Rebe
2002-01-23 2:01 ` Gustavo Zacarias
2002-01-23 2:11 ` Tom Hornyak
2002-01-22 22:32 ` Steve Brueggeman
2002-01-22 5:45 ` Shaya Potter
2002-01-22 12:58 ` Dave Jones
2002-01-22 15:27 ` Shaya Potter
2002-01-22 18:52 ` Greg
2002-01-22 22:08 ` Rene Rebe
2002-01-21 22:19 ` David S. Miller
2002-01-22 0:37 ` Andrea Arcangeli
2002-01-22 0:43 ` Russell King
2002-01-22 0:53 ` Andrea Arcangeli
2002-01-22 0:55 ` Russell King
2002-01-22 1:07 ` David S. Miller
2002-01-22 1:27 ` Andrea Arcangeli
2002-01-22 16:57 ` David Woodhouse
2002-01-21 19:37 ` Alan Cox
2002-01-21 19:34 ` David Weinehall
2002-01-21 19:53 ` Sipos Ferenc
2002-01-22 6:32 ` Paul G. Allen
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 14:12 Halpaap, Mark (CETA)
2002-01-22 14:51 ` Ed Sweetman
2002-01-22 23:21 ` Ian Molton
2002-01-22 14:51 ` João Seabra
2002-01-23 18:49 ` Marek Mentel
2002-01-22 17:59 Ben Carrell
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=20020122013909.N8292@athlon.random \
--to=andrea@suse.de \
--cc=akpm@zip.com.au \
--cc=alan@lxorg.ukuu.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reid.hekman@ndsu.nodak.edu \
/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