From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Yesterdays git does not boot on U5
Date: Mon, 10 Oct 2005 18:33:11 +0000 [thread overview]
Message-ID: <20051010.113311.55634660.davem@davemloft.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0510101057330.28936@math.ut.ee>
From: Meelis Roos <mroos@linux.ee>
Date: Mon, 10 Oct 2005 18:19:29 +0300 (EEST)
> l0: 0000000000055114 l1: 00000000f005634f l2: 0000000000000001 l3: 0000000000000000
> l4: 0000000000000013 l5: 0000000000000013 l6: 0000000000000000 l7: 00000000003b0a20
> i0: 0000000000719840 i1: 0000000000719800 i2: 0000000000719908 i3: 0000000000000003
> i4: 0000000000000000 i5: 0000000000000000 i6: 00000000fffa95b1 i7: 000000000050822c
> I7: <prom_cif_interface+0xac/0x134>
> Instruction DUMP: 8a016004 ca700006 8a03e008 <e0016000> 81c40002
> 8a016004 c8700007 8803e008 e0016000
Actually, we are calling into the firmware explicitly.
Can you get a deeper call trace? So we can see who is calling
prom_cif_interface() and likewise that function's caller as well?
We need this information in order to debug this.
next prev parent reply other threads:[~2005-10-10 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 7:58 Yesterdays git does not boot on U5 Meelis Roos
2005-10-10 15:09 ` Patrick Finnegan
2005-10-10 15:19 ` Meelis Roos
2005-10-10 18:15 ` David S. Miller
2005-10-10 18:32 ` David S. Miller
2005-10-10 18:33 ` David S. Miller [this message]
2005-10-10 20:10 ` Meelis Roos
2005-10-10 20:22 ` Meelis Roos
2005-10-10 20:26 ` David S. Miller
2005-10-10 20:27 ` David S. Miller
2005-10-10 23:14 ` David S. Miller
2005-10-11 6:50 ` Meelis Roos
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=20051010.113311.55634660.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.