Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@ut.ee>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Thibaut VARENE <varenet@parisc-linux.org>,
	randolph@tausq.org, linux-parisc@vger.kernel.org
Subject: Re: HPPA hang with PCI SERR or PARITY enabling
Date: Sat, 1 Aug 2009 02:16:29 +0300 (EEST)	[thread overview]
Message-ID: <Pine.SOC.4.64.0908010202020.15830@math.ut.ee> (raw)
In-Reply-To: <20090731144654.F3D374CFD@hiauly1.hia.nrc.ca>

> > 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.
> 
> I tried to download the kernel package, but it's gone from the debian
> servers.  So, you will have to run objdump yourself.  Just do
> 
> hppa64-linux-gnu-objdump vmlinux-2.6.29-2-parisc64-smp | less

Did this - managed to boot via etch netinst+chroot. The address ranges 
do not match (as suggested by an earleir post?) - they start with
0000000040100000. r02 shows 000000000c1b5c78 and I can not find anything 
sensible ending with 1b5c7XX. The only match is in the middle of 
filemap_fault:

    401b5c64:   08 19 02 49     copy r25,r9
    401b5c68:   53 5c 00 50     ldd 28(r26),ret0
    401b5c6c:   c5 fc 43 e8     bb,< ret0,f,401b5e68 <filemap_fault+0x278>
    401b5c70:   34 0b 00 00     ldi 0,r11
    401b5c74:   34 0c 00 00     ldi 0,r12
    401b5c78:   2b 60 00 00     addil L%0,dp,r1
    401b5c7c:   08 01 02 4d     copy r1,r13
    401b5c80:   2b 63 30 00     addil L%7800,dp,r1
    401b5c84:   37 c7 3f a1     ldo -30(sp),r7
    401b5c88:   08 01 02 48     copy r1,r8

Also, there is no mention of IAOQ, IIR, IOR in HPMC - are they there but 
with different names?

The disassmebly from the image is at
http://muuseum.at.mt.ut.ee/~mroos/objdump-2.6.19-2-parisc64-smp if 
sombeody can help me find my way through it. The image itself is at
http://muuseum.at.mt.ut.ee/~mroos/vmlinux-2.6.29-2-parisc64-smp

I also installed Debian's current 2.6.30-1-parisc64 kernel and it 
behaves the same - HPMC after PCI messages from tulip.

For some strange reason, 2.6.18-6-parisc64 (as fully working netbooted 
etch's uname tells) does not boot from disk either - it panics in a 
differnet place so I did not investigate it further. Maybe probles with 
my initramfs.

-- 
Meelis Roos (mroos@ut.ee)      http://www.cs.ut.ee/~mroos/

  parent reply	other threads:[~2009-07-31 23:16 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 [this message]
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=Pine.SOC.4.64.0908010202020.15830@math.ut.ee \
    --to=mroos@ut.ee \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=linux-parisc@vger.kernel.org \
    --cc=randolph@tausq.org \
    --cc=varenet@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