From: Grant Grundler <grundler@parisc-linux.org>
To: Bernd Gietzelt <berndg@fsim-ev.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: HPPA hang with PCI SERR or PARITY enabling
Date: Fri, 7 Aug 2009 10:36:28 -0600 [thread overview]
Message-ID: <20090807163628.GB18373@lackof.org> (raw)
In-Reply-To: <20090806141542.bf48febf.berndg@fsim-ev.de>
On Thu, Aug 06, 2009 at 02:15:42PM +0200, Bernd Gietzelt wrote:
> I've done some test with actual and older kernels from debian because
> my system shows the same behavior.
...
> 2.6.30-1-parisc64 SERR & PARITY
Bernd,
BTW, this output has the same issue as the -smp where
the GSP is printing PDC chassis codes/info instead of
kernel output.
...
[ 11.924000] sym53c8xx 0000:38:00.0: enabling device (0000 -> 0003)
[ 11.940000] sym53c8xx 0000:38:00.0: enabling SERR and PARITY (0003 -> 0143)
************* SYSTEM ALERT **************
SYSTEM NAME: rfhinf238
DATE: 08/06/2009 TIME: 09:32:34
ALERT LEVEL: 7 = reserved
...
0x0000007000FF6292 000000F0 F0000000 - type 0 = Data Field Unused
0x5800087000FF6292 00006D07 06092022 - type 11 = Timestamp 08/06/2009 09:32:34
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
*****************************************
the 0x6292 indicates this is an HPMC and you've included the PIM dump
so we shouldn't need anything else at the moment. If you want
to retry with "pdcchassis=0", it would be nice to have the complete
output but I don't think it's required (yet).
I'm pointing this out since the symptom in your listing should
be "HPMC in foo()" where we look up the "IIA Offset"
(0x000000004029d6ac) in the System.map file.
(See "a.c" in http://cvs.parisc-linux.org/build-tools/ to help)
It's also good to look up GR02 (0x000000000c1d5448) at the
same time though GR02 not always as useful.
I forgot how to look up the symbol for modules since HPMC's
after /sbin/init has started often occur becuase of additional
kernel modules getting loaded or NIC interfaces are initialized
when ifconfig'd. Tulip is a suspect in this case.
thanks again,
grant
next prev parent reply other threads:[~2009-08-07 16:36 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
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 [this message]
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=20090807163628.GB18373@lackof.org \
--to=grundler@parisc-linux.org \
--cc=berndg@fsim-ev.de \
--cc=linux-parisc@vger.kernel.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