linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Etsushi Kato <ekato@ees.hokudai.ac.jp>
Cc: <paulus@samba.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: tlbia and PPC603
Date: Thu, 20 Jun 2002 11:12:13 +0200	[thread overview]
Message-ID: <20020620091213.4502@smtp.adsl.oleane.com> (raw)
In-Reply-To: <20020620193505D.ekato@ees.hokudai.ac.jp>


>> Your xmon trace show something interesting: xmon itself crashes with a
>> trap 300 while trying to access the hash table. The hash beeing mapped
>> with a BAT, that shouldn't be an issue with the TLB handlers nor with
>> a stale TLB entry. I currently fail to see what could be going on there,
>> could you try to reproduce that crash ? In this case, once "h" fails
>> within xmon, type
>>
>>  di %pc
>
>>mon di %pc

Hrm... I should think before replying !

It's completely normal that "h" crashes on a 603 as there is simply no
hash table on this CPU.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-20  9:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020620174254U.ekato@ees.hokudai.ac.jp>
2002-06-20  7:53 ` tlbia and PPC603 Benjamin Herrenschmidt
2002-06-20 10:35   ` Etsushi Kato
2002-06-20  9:12     ` Benjamin Herrenschmidt [this message]
2002-06-19 11:17 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
2002-06-20 11:15   ` Gabriel Paubert
2002-06-25 14:43     ` Etsushi Kato
2002-06-24  4:02       ` 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=20020620091213.4502@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).