From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: David van Hoose <davidvh@cox.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.69
Date: Mon, 5 May 2003 09:02:22 -0700 [thread overview]
Message-ID: <20030505160222.GP8931@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305050851080.18785-100000@home.transmeta.com>
On Mon, May 05, 2003 at 08:56:41AM -0700, Linus Torvalds wrote:
> They actually started in 2.5.60 if it's the same bug.
> And yes, you'd get random crashes, panics, lockups and even reboots. The
> problem was that the pmd/pgd's were put in the slab cache in between
> 2.5.59 and 2.5.60, and that was simply wrong because the AGP code changes
> the cacheability of the kernel pages when it maps stuff into the AGP
> aperture. That in turn will change the page tables but it won't update the
> cached entries in the pmd slab caches.
> So what happens is that once you exit X, and the page tables are put back
> together without the cacheability changes, and you start a new program,
> that program may get a page table with partly bogus kernel page table
> entries.
> That, in turn, when it happens will cause _major_ memory corruption, and
> your machine is toast, often in very interesting ways because the internal
> kernel data structures got corrupted. It can also cause random SIGSEGV's
> etc.
> But it only happens with AGP, and a lot of people either don't use it or
> run only one X session.
Any chance one of you could try out the fixed slabification patches?
Message-ID: <20030505105213.GO8931@holomorphy.com>
-- wli
next prev parent reply other threads:[~2003-05-05 15:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EB602ED.3080207@cox.net>
2003-05-05 15:56 ` Linux 2.5.69 Linus Torvalds
2003-05-05 16:02 ` William Lee Irwin III [this message]
2003-05-05 16:06 ` David van Hoose
2003-05-05 16:16 ` Steven Cole
2003-05-05 18:49 ` Dave Jones
2003-05-05 18:53 ` Linus Torvalds
2003-05-06 22:03 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 7:00 Voluspa
[not found] <fa.m5ekdiv.15gu98j@ifi.uio.no>
2003-05-05 13:00 ` walt
2003-05-05 4:19 Voluspa
2003-05-05 0:48 Linus Torvalds
2003-05-05 4:30 ` Florin Iucha
2003-05-05 4:41 ` Linus Torvalds
2003-05-05 6:31 ` Anders Karlsson
2003-05-05 7:08 ` Anders Karlsson
2003-05-05 13:07 ` Florin Iucha
2003-05-05 13:20 ` Florin Iucha
2003-05-05 8:14 ` Benjamin Herrenschmidt
2003-05-05 21:05 ` John Cherry
2003-05-05 21:39 ` Sam Ravnborg
2003-05-05 21:45 ` Arnaldo Carvalho de Melo
2003-05-05 23:22 ` John Cherry
2003-05-06 10:08 ` Paweł Gołaszewski
2003-05-06 13:39 ` Roger Luethi
2003-05-06 14:08 ` David S. Miller
2003-05-06 18:24 ` Arnaldo Carvalho de Melo
2003-05-07 2:22 ` Rusty Russell
2003-05-07 19:44 ` Geert Uytterhoeven
2003-05-07 19:35 ` Ben Collins
2003-05-07 22:07 ` Linus Torvalds
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=20030505160222.GP8931@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davidvh@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).