From: Thibaut VARENE <varenet@parisc-linux.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Randolph Chung <randolph@tausq.org>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
linux-parisc@vger.kernel.org
Subject: Re: HPPA hang with PCI SERR or PARITY enabling
Date: Fri, 31 Jul 2009 11:35:17 +0200 [thread overview]
Message-ID: <7d01f9f00907310235hb342840j14b7ccc3bcc01184@mail.gmail.com> (raw)
In-Reply-To: <Pine.SOC.4.64.0907310923520.710@math.ut.ee>
On Fri, Jul 31, 2009 at 8:28 AM, Meelis Roos <mroos@linux.ee> wrote:
>
> > Please see http://www.parisc-linux.org/faq/kernelbug-howto.html
>
> Well, I can not find anything about interpreting SER PIM data there?
Are you sure? There are basic explanations about the info we need. For instance:
"- The r02 register is the "return pointer" - it indicates the calling function
- The IAOQ contents specify the address of the instruction where the
fault occured."
Of course they are undecoded, that's why you need to be able to
objdump the kernel.
> My system is 2-CPU L1000, that I forgot to re-mention as I reported to
> my old report that anyone but me had probably forgotten. Using GSP.
> ALso, I rebooted the hanging computer using 'RS' from GSP, not 'TC' -
> does that garble PIM data?
After HPMC, RS is ok. Remember to always ser clearpim after collecting the info.
> > Anyway, from the output below, I suspect maybe we have some kernel functions
> > that are not in the right section, since the error happens right after
> > "Freeing unused kernel memory"?
>
> No, the real problem is below, this badness on SMP I was told to ignore
> here on this list in spring. The real problem happens after tuli driver
> loading and PCI configuration of the cards. From these, I only have the
> SER PIM data, no kernel backtrace.
PIM will contain relevant (though undecoded) information, so that's
already good to have.
HTH
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
next prev parent reply other threads:[~2009-07-31 9:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:24 HPPA hang with PCI SERR or PARITY enabling Meelis Roos
2009-06-15 13:45 ` John David Anglin
2009-07-30 17:58 ` Meelis Roos
2009-07-31 1:25 ` Randolph Chung
2009-07-31 1:45 ` John David Anglin
2009-07-31 6:28 ` Meelis Roos
2009-07-31 9:35 ` Thibaut VARENE [this message]
2009-07-31 14:46 ` John David Anglin
2009-07-31 14:50 ` John David Anglin
2009-07-31 23:16 ` Meelis Roos
2009-08-01 20:59 ` John David Anglin
2009-08-05 17:45 ` Grant Grundler
2009-08-05 19:42 ` Meelis Roos
2009-08-06 12:15 ` Bernd Gietzelt
2009-08-07 16:22 ` Grant Grundler
2009-08-08 9:31 ` Bernd Gietzelt
2009-08-09 5:27 ` Grant Grundler
2009-08-10 1:22 ` Randolph Chung
2009-08-10 8:01 ` Thibaut VARENE
2009-08-10 8:09 ` Thibaut VARENE
2009-08-10 11:08 ` Bernd Gietzelt
2009-08-10 11:18 ` Thibaut VARENE
2009-08-10 11:57 ` Bernd Gietzelt
2009-08-10 23:20 ` Grant Grundler
2009-08-11 9:27 ` Thibaut VARENE
2009-08-10 8:26 ` Bernd Gietzelt
2009-08-07 16:36 ` Grant Grundler
2009-08-29 20:19 ` Meelis Roos
2009-06-15 14:06 ` John David Anglin
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=7d01f9f00907310235hb342840j14b7ccc3bcc01184@mail.gmail.com \
--to=varenet@parisc-linux.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=randolph@tausq.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