From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Etsushi Kato <ekato@ees.hokudai.ac.jp>
Cc: <linuxppc-dev@lists.linuxppc.org>, <paulus@samba.org>
Subject: Re: tlbia and PPC603
Date: Thu, 20 Jun 2002 08:36:24 +0200 [thread overview]
Message-ID: <20020620063624.17364@smtp.adsl.oleane.com> (raw)
In-Reply-To: <20020620165750B.ekato@ees.hokudai.ac.jp>
>Hi Ben,
>Thank you for your reply.
>
>On Wed, Jun 19, 2002 at 05:51:37AM +0200,
>Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
>> Try without the ethernet card and switch IDE DMA off and tell me if it is
>> stable, there could be some cache coherency issues with some of the
chipsets
>> used on these machines.
>
>I was able to use both IDE DMA and ethernet card on
>linux-2.4.13-pre3-ben0 without problems.
Do you still have this kernel source ? My local repository got
corrupted at some point so I can't go that far in the history.
I would appreciate if you could send me a tarball with at least
the content of arch/ppc/kernel, arch/ppc/mm and include/asm-ppc
so I can do some comparisons.
>Anyway I tried rsync kernel without CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
>and compiled tulip as modules (and not loaded), but it still dropped
>to xmon randomly.
Ok.
>> Another thing you can try is in set_context(), add an isync on the line
>> that contain the label "3:" as the doc states a context synchronizing
>> instruction should also be used for data sync. before mtsrin.
>
>I changed set_context() and it might improve stableness somewhat, but
>still dropped to xmon at some occasion.
Hrm...
>> Hrm... just in case, try also changing the definition of tlbia macro
>> in ppc_asm.h to put isync's inside the loop, both before and after the
>> tlbie's (add too much is no problem for such a test) and tell me if it
>> has any effect.
>
>With this change combined with set_context() change, crashes
>disappeared during boot time (tested 10 times and all trial
>succeeded). It is really improvement. But still sometimes (5 times
>per 10) dropped to xmon while sshd is working by ssh connection from
>other machine.
Can you send me a couple of xmon backtraces with lookup in System.map ?
Also, please try editing arch/ppc/kernel/ppc_asm.h and change the definition
of SYNC, SYNC_601 and ISYNC_601 so they unconditionally do the various sync &
isync's (that is remove the BEGIN_FTR_SECTION and END_FTR_SECTION(...) lines
from them.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-20 6:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 11:17 tlbia and PPC603 Etsushi Kato
2002-06-18 23:55 ` Benjamin Herrenschmidt
2002-06-19 3:10 ` Benjamin Herrenschmidt
2002-06-20 6:09 ` Etsushi Kato
2002-06-19 3:51 ` Benjamin Herrenschmidt
2002-06-20 7:57 ` Etsushi Kato
2002-06-20 6:36 ` Benjamin Herrenschmidt [this message]
2002-06-20 11:15 ` Gabriel Paubert
2002-06-25 14:43 ` Etsushi Kato
2002-06-24 4:02 ` Benjamin Herrenschmidt
[not found] <20020620174254U.ekato@ees.hokudai.ac.jp>
2002-06-20 7:53 ` Benjamin Herrenschmidt
2002-06-20 10:35 ` Etsushi Kato
2002-06-20 9:12 ` Benjamin Herrenschmidt
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=20020620063624.17364@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=ekato@ees.hokudai.ac.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).