Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.18 SMP instability
Date: Tue, 28 May 2002 11:07:57 -0600	[thread overview]
Message-ID: <20020528170758.16D13482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jeremy Drake <jeremyd@apptechsys.com> of "Mon, 27 May 2002 14:49:24 PDT." <Pine.LNX.4.44.0205271438590.11012-200000@garibaldi.apptechsys.com>

Jeremy Drake wrote:
> I'll try.  BTW, the HPMC only happens sometimes.  Most of the time it just 
> hangs.  But HPMC starts if I hit the button on the back and let it boot.

ok. This is an interesting symptom.

...
> General Registers 0 - 31
> 00-03   0000000000000000  0000000a44b3921e  0000000000019bf0  00000000f400400
>   0

GR02 is the return pointer - but it's not a kernel address.
Possible PDC or something else.

...
> IIA Space                    = 0x0000000000000000
> IIA Offset                   = 0x0000000000019bf8

IIA is the instruction pointer. Also not a valid kernel address.
It's possible we are getting a "double fault" and the first
one is overwriting the original HPMC.

> Check Type                   = 0x20000000
> CPU State                    = 0x9e000004
> Cache Check                  = 0x00000000
> TLB Check                    = 0x00000000
> Bus Check                    = 0x0030103b
> Assists Check                = 0x00000000
> Assist State                 = 0x00000000
> Path Info                    = 0x00000000
> System Responder Address     = 0x000000fff4004014
> System Requestor Address     = 0xfffffffffffa0000

This is useful. The system *probably* died trying to access 0xf4004014.
I could try to look up CPU State but I'm out of time.


Here are the next steps:
1) figure out who is touching 0xf4004014.
   I didn't see anything in the console output.
   (http://lists.parisc-linux.org/pipermail/parisc-linux/2002-May/016342.html)
   Can you look in /proc/iomem?
   My C3000 has:
   f4000000-f4ffffff : LBA PCI LMMIO
     f4007000-f4007fff : usb-ohci
     f4008000-f40083ff : tulip

2) figure out if the access is because of bad DMA killing the IOMMU
   or just the chip not responding.

It remotely possible the latest commit I made will affect this problem.
Can you retry with -pa28 (or -pa29)?

grant

       reply	other threads:[~2002-05-28 17:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0205271438590.11012-200000@garibaldi.apptechsys.com>
2002-05-28 17:07 ` Grant Grundler [this message]
2002-05-28 19:35   ` [parisc-linux] 2.4.18 SMP instability Jeremy Drake
2002-05-28 19:45     ` Jeremy Drake
2002-05-28 21:56       ` Jeremy Drake
2002-05-29  4:56         ` Grant Grundler
2002-05-29  4:39       ` Grant Grundler
2002-05-29  6:26         ` Jeremy Drake
2002-05-29  6:35           ` Grant Grundler
2002-06-01  6:34             ` Jeremy Drake
2002-06-02 16:32               ` Grant Grundler
2002-06-02 19:48                 ` Jeremy Drake
2002-06-03  3:28                   ` Grant Grundler
2002-06-03 21:58                   ` Jeremy Drake
2002-06-05 21:24                     ` Grant Grundler
     [not found] <20020527223132.661F54843@dsl2.external.hp.com>
2002-05-29 18:56 ` Jeremy Drake
2002-05-26  0:48 Robert Stanford
2002-05-26  6:09 ` Grant Grundler
2002-05-26  7:29   ` Jeremy Drake
2002-05-26 20:23     ` Jeremy Drake
2002-05-27  2:04       ` Grant Grundler
2002-05-27  6:17         ` Jeremy Drake
2002-05-27 12:04           ` Matthew Wilcox
2002-05-27 18:44           ` Jeremy Drake

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=20020528170758.16D13482A@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=jeremyd@apptechsys.com \
    --cc=parisc-linux@lists.parisc-linux.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