public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David van Hoose <davidvh@cox.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.69
Date: Mon, 05 May 2003 11:06:43 -0500	[thread overview]
Message-ID: <3EB68C13.9080000@cox.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0305050851080.18785-100000@home.transmeta.com>

Linus Torvalds wrote:
> [ Linux-kernel added to the cc, since I got several queries about what the 
>   crashes were.. ]
> 
> On Mon, 5 May 2003, David van Hoose wrote:
> 
>>Can I get some details regarding the AGP problem? I had some really bad 
>>random crashes, panics, and hardlocks up through 2.5.68, and I'm 
>>wondering if this is the same issue. I first noticed them around 2.5.63. 
> 
> 
> 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.

Okay.. I kept having all of those problems. I guess the memory 
corruption could also explain the buffer overflow in the panic 
information I posted around the time of 2.5.65 then. I'll stick the beta 
kernel back on my system and play with it again. If I find anything 
else, I'll be sure to mention it. Don't want any nasty bugs like that 
hiding in 2.6.x.

Thanks!
David


  parent reply	other threads:[~2003-05-05 15:54 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
2003-05-05 16:06   ` David van Hoose [this message]
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=3EB68C13.9080000@cox.net \
    --to=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