From: art <art@sigrand.ru>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re[4]: Problem with TLB mcheck!
Date: Fri, 2 Jun 2006 19:58:08 +0700 [thread overview]
Message-ID: <2832.060602@sigrand.ru> (raw)
In-Reply-To: <Pine.LNX.4.64N.0606021324420.23118@blysk.ds.pg.gda.pl>
Hello Maciej,
Friday, June 02, 2006, 7:27:18 PM, you wrote:
MWR> Hello Art,
>> I was inattentive - you told about not my patch! Now I'am no use this!
>> So DON'T tell me more about this :), sorry for my mistake.
>>
>> And about latest kernel version:
>> 1. I think this problem is in memory management subsystem (am I
>> right?)
>> 2. If 1 is right - then now I have latest memory management sybsystem,
>> because I apply all TLB-related patches (only one Ralfs really).
MWR> Wait, wait! Please start from the beginning: if you try the kernel as of
MWR> the top of the tree at www.linux-mips.org, then can you still trigger the
MWR> machine check or does the kernel work fine? If the former, then please
MWR> send the dump of state produced.
MWR> Maciej
Yes machine check was still occuring with latest kernel (2.6.16 with
patched mm subsystem - how I sed - I've searched gitweb to find all
changes from 20 March (when 2.6.16 was released)).
Then I start watching tlbex.c, because patch which was recomended (but
irrelevant as you say - and you were wright!) make mcheck occuring not
so often. So I make second changes :
--- /home/artpol/router/buildroot/kernels/linux-2.6.16-old/arch/mips/mm/tlbex.c 2006-03-20 11:35:39.000000000 +0000
+++ tlbex.c 2006-05-31 16:57:58.000000000 +0000
@@ -838,6 +838,7 @@
break;
case CPU_R4300:
+ case CPU_4KC:
case CPU_5KC:
case CPU_TX49XX:
case CPU_AU1000:
@@ -852,13 +853,12 @@
case CPU_R10000:
case CPU_R12000:
- case CPU_4KC:
case CPU_SB1:
case CPU_SB1A:
case CPU_4KSC:
case CPU_20KC:
case CPU_25KF:
- tlbw(p);
+ tlbw(p);
break;
case CPU_NEVADA:
@@ -1260,7 +1260,7 @@
}
Till that I have no machine check at all!
--
Best regards,
art mailto:art@sigrand.ru
parent reply other threads:[~2006-06-02 12:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.64N.0606021324420.23118@blysk.ds.pg.gda.pl>]
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=2832.060602@sigrand.ru \
--to=art@sigrand.ru \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.