Re: 2.6.13-rc3-mm3

[Christoph Lameter <christoph@lameter.com>]

On Tue, 2 Aug 2005, Richard Purdie wrote:

> > +	update_mmu_cache(vma, address, entry);
> > +	lazy_mmu_prot_update(entry);
> > +#endif
> 
> This locks the system up after the "INIT: version 2.86 booting" message.
> SysRq still responds but that's about it.

Hmmm. this should have returned the behavior to normal. Ah. Need to use 
new_entry instead of entry. Try this (is there any way that I could get 
access to the sytem? I am on IRC (freenode.net nick o-o) or on skype).

Index: linux-2.6.13-rc4-mm1/mm/memory.c
===================================================================
--- linux-2.6.13-rc4-mm1.orig/mm/memory.c	2005-08-01 16:11:45.000000000 -0700
+++ linux-2.6.13-rc4-mm1/mm/memory.c	2005-08-01 16:15:35.000000000 -0700
@@ -2094,6 +2094,7 @@
 		entry = pte_mkdirty(entry);
 	}
 
+#ifdef CONFIG_ATOMIC_TABLE_OPS
 	/*
 	 * If the cmpxchg fails then another processor may have done
 	 * the changes for us. If not then another fault will bring
@@ -2106,6 +2107,11 @@
 	} else {
 		inc_page_state(cmpxchg_fail_flag_update);
 	}
+#else
+	ptep_set_access_flags(vma, address, pte, new_entry, write_access);
+	update_mmu_cache(vma, address, new_entry);
+	lazy_mmu_prot_update(new_entry);
+#endif
 
 	pte_unmap(pte);
 	page_table_atomic_stop(mm);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/