linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: "Michel Eyckmans (MCE)" <mce@pi.be>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.38
Date: Sun, 22 Sep 2002 19:27:18 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209221924210.1208-100000@home.transmeta.com> (raw)
In-Reply-To: <200209230019.g8N0JmvC003642@jebril.pi.be>


On Mon, 23 Sep 2002, Michel Eyckmans (MCE) wrote:
> 
> The boot time lock up, that I have indeed encountered intermittently ever 
> since switching to 2.5.3{01}, may indeed be gone, but the one where just 
> moving my mouse around locks things up in a matter of seconds hasn't. 

That may just be due to the new mouse driver and/or input layer, which 
went in some weeks ago. What kind of mouse (and if it is a PS/2 mouse, can 
you get a loaner USB mouse to test with, for example?)

> Someone recently reported having similar problems and fixing them by 
> disabling MTRR, but this cannot be the entire story since I never had it 
> enabled in the first place. No wonder, on a dual P5 machine...

There was a separate MTRR atomicity problem that would cause extreme 
slowdowns on SMP with MTRR enabled when X was started, because the MTRR 
code would have re-entrancy problems and potentially leave the caches 
disabled. That should have been fixed in 2.5.36.

		Linus


  parent reply	other threads:[~2002-09-23  2:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-22  4:34 Linux 2.5.38 Linus Torvalds
2002-09-22  6:16 ` make bzImage fails on 2.5.38 Aniruddha Shankar
2002-09-22  6:31   ` Alexander Viro
2002-09-22  6:43     ` [PATCH] " Hiroshi Takekawa
2002-09-22  6:56     ` Aniruddha Shankar
2002-09-22  9:54     ` Arjan van de Ven
2002-09-22 10:14       ` Alexander Viro
2002-09-22 10:53 ` [BUG,PATCH] 2.5.38 floppy Philipp Matthias Hahn
2002-09-22 13:09 ` Linux 2.5.38 Adrian Bunk
2002-09-22 13:21   ` Alexander Viro
2002-09-22 20:02 ` Jochen Friedrich
2002-09-22 20:07   ` Arnaldo Carvalho de Melo
2002-09-22 20:22   ` Jochen Friedrich
2002-09-23  1:44     ` Peter Rival
2002-09-23  2:32       ` Linus Torvalds
2002-09-23  2:39         ` Jeff Garzik
2002-09-22 21:59 ` [PATCH] #include <linux/version.h> missing in drivers/usb/host/ohci-hcd.c Luc Van Oostenryck
2002-09-23 19:51   ` Greg KH
2002-09-23  0:19 ` Linux 2.5.38 Michel Eyckmans (MCE)
2002-09-23  0:57   ` Skip Ford
2002-09-23  2:27   ` Linus Torvalds [this message]
2002-09-23 23:06     ` Michel Eyckmans (MCE)
2002-09-23 23:23       ` Linus Torvalds
2002-09-24 22:42         ` Michel Eyckmans (MCE)
2002-09-25 17:46           ` Bill Davidsen
2002-09-26  0:43             ` Russell King
2002-09-24 12:54   ` [PATCH] export find_task_by_pid() for 2.5.38 James Morris
2002-09-23 12:53 ` Linux 2.5.38 Clemens Schwaighofer
2002-09-23 15:28 ` Linux 2.5.38 [PATCH] IrDA Philipp Matthias Hahn
2002-09-23 22:04   ` Jean Tourrilhes
2002-09-26 20:40 ` [PATCH] Re: Linux 2.5.38 Rasmus Andersen
2002-09-26 21:12 ` Rasmus Andersen

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.0209221924210.1208-100000@home.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mce@pi.be \
    /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).