linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, <jon@jon-foster.co.uk>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.6-mm] Fix 4G/4G X11/vm86 oops
Date: Tue, 18 Nov 2003 23:24:04 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0311182310430.23026-100000@home.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0311190147060.11537@montezuma.fsmlabs.com>


On Wed, 19 Nov 2003, Zwane Mwaikambo wrote:
> 
> I just tried the RH9 2.96 and it also triple faulted. Oh my.. The only 
> unique thing about this hardware compared ot the other stuff i have here 
> is that it's an AMD K6. Everything else is Intel.

Different TLB sizes (and organizations) etc can _easily_ matter, if the 
Intel one just happens to work because something stays in the TLB while 
the page table mapping is incorrect and keeps the system afloat.

Or - and in this case more likely - since the problem is fixed by running
a (complex) thing that trashes all over the DTLB/ITLB, it's more likely
that there might be a _missing_ TLB invalidate somewhere, and that the
Intel boxes stay up because they have a smaller TLB and the stale entry
gets flushed out early from them.

But you already tried a "flush_tlb_all()" which _should_ have flushed
absolutely everything, including global tables. I dunno. It could be
hitting a CPU bug too, of course. 

It would be interesting to hear if other K6 users see problems..

			Linus


  reply	other threads:[~2003-11-19  7:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 23:48 Re:Re: [PATCH][2.6-mm] Fix 4G/4G X11/vm86 oops Jon Foster
2003-11-19  3:24 ` Zwane Mwaikambo
2003-11-19  5:45   ` Andrew Morton
2003-11-19  6:50     ` Zwane Mwaikambo
2003-11-19  7:24       ` Linus Torvalds [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-14 21:47 2.6.0-test9-mm3 Linus Torvalds
2003-11-15  0:55 ` 2.6.0-test9-mm3 Zwane Mwaikambo
2003-11-15 19:34   ` [PATCH][2.6-mm] Fix 4G/4G X11/vm86 oops Zwane Mwaikambo
2003-11-15 19:52     ` Zwane Mwaikambo
2003-11-17 21:46     ` Zwane Mwaikambo
2003-11-17 22:42       ` Linus Torvalds
2003-11-17 23:01         ` Zwane Mwaikambo
2003-11-17 23:14           ` Zwane Mwaikambo
2003-11-18  7:21             ` Zwane Mwaikambo
2003-11-18 15:47               ` Linus Torvalds
2003-11-18 16:16                 ` Zwane Mwaikambo
2003-11-18 16:37                   ` Linus Torvalds
2003-11-18 17:08                     ` Zwane Mwaikambo
2003-11-18 17:38                       ` Martin J. Bligh
2003-11-18 17:22                         ` Zwane Mwaikambo
2003-11-19 20:32                     ` Matt Mackall
2003-11-19 23:09                       ` Matt Mackall
2003-11-20  7:14                         ` Zwane Mwaikambo
2003-11-20  7:44                         ` Matt Mackall
2003-11-20  7:53                           ` Andrew Morton
2003-11-20  8:13                           ` Matt Mackall

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=Pine.LNX.4.44.0311182310430.23026-100000@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=jon@jon-foster.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@arm.linux.org.uk \
    /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).