From: "Tommy S. Christensen" <tch@avanticore.com>
To: Venkata Rajesh Bikkina <rajeshbv@intotoinc.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-mips@oss.sgi.com
Subject: Re: RAMDISK problem on 79s334A board.
Date: Thu, 16 May 2002 10:52:52 +0200 [thread overview]
Message-ID: <3CE37364.945C40A7@avanticore.com> (raw)
In-Reply-To: E177ypv-0001up-00@the-village.bc.nu
Alan Cox wrote:
>
> > But the same module is working fine and kernel is also fine if i use NFS
> > and insert the module.
> > Any further info ?
>
> Not really. The fact it works with NFS and not ramdisk may simply be that
> in one case it corrupts memory that is used, and the other it corrupts
> memory that isnt
Using a ramdisk increases the pressure on memory. So the difference could
be that one case hits the cache aliasing problem, the other doesn't.
Try this patch and see if it helps.
-Tommy
Index: mm/vmalloc.c
===================================================================
RCS file: /cvs/linux/mm/vmalloc.c,v
retrieving revision 1.28
retrieving revision 1.28.2.1
diff -u -r1.28 -r1.28.2.1
--- mm/vmalloc.c 2001/10/19 01:25:06 1.28
+++ mm/vmalloc.c 2001/12/28 21:06:01 1.28.2.1
@@ -163,6 +163,7 @@
ret = 0;
} while (address && (address < end));
spin_unlock(&init_mm.page_table_lock);
+ flush_cache_all();
return ret;
}
next prev parent reply other threads:[~2002-05-16 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 8:42 RAMDISK problem on 79s334A board Venkata Rajesh Bikkina
2002-05-15 11:00 ` Alan Cox
2002-05-15 11:00 ` Alan Cox
2002-05-15 12:00 ` Venkata Rajesh Bikkina
2002-05-15 13:28 ` Alan Cox
2002-05-15 13:28 ` Alan Cox
2002-05-16 8:52 ` Tommy S. Christensen [this message]
2002-05-16 10:22 ` Venkata Rajesh Bikkina
2002-05-16 12:30 ` Tommy S. Christensen
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=3CE37364.945C40A7@avanticore.com \
--to=tch@avanticore.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@oss.sgi.com \
--cc=rajeshbv@intotoinc.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