linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@norran.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [pre PATCH] freezes
Date: Thu, 15 Feb 2001 15:29:12 +0100	[thread overview]
Message-ID: <01021515291200.01148@dox> (raw)

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

Hi,

I have had occasional freezes (complete NumLock won't work) for some time.
I blamed HW, irq conflicts, temperature problems, ...

But suddenly with 2.4.2-pre1 the problems disappeared!

Since 2.4.2-pre1 was rather short I took the time to try to find out what 
could be the fix.

I found one candidate, the setting of  TASK_RUNNING in handle_mm_fault.

Since the problem had appeared on both 2.4 and 2.2.18 I started to try to 
reproduce the problem in an unpatched 2.2 - it took some time, got the freeze
today.

During this time I have tried to collect information of the freezes on KDE 
mailing lists - I do now have three additional reports (one running 2.2.17)
Hardware has varied.

I have now compiled and installed this patch but since it can't be proven
to fix the problem I submit it now.

/RogerL

-- 
Home page:
  none currently

[-- Attachment #2: patch-2.2.18-handle_mm_fault --]
[-- Type: text/plain, Size: 266 bytes --]

--- linux/mm/memory.c.orig	Wed Feb 14 00:58:59 2001
+++ linux/mm/memory.c	Wed Feb 14 00:59:16 2001
@@ -935,6 +935,7 @@
 	pte_t * pte;
 	int ret;
 
+	current->state = TASK_RUNNING;
 	pgd = pgd_offset(vma->vm_mm, address);
 	pmd = pmd_alloc(pgd, address);
 	if (!pmd)

                 reply	other threads:[~2001-02-15 14:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01021515291200.01148@dox \
    --to=roger.larsson@norran.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).