LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Hankin <shankin@rational.com>
To: phandel@cise.ufl.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-test10 boot failure on Powerbook G3
Date: Thu, 19 Oct 2000 16:51:44 -0400	[thread overview]
Message-ID: <p04320400b61508915079@[172.21.170.210]> (raw)
In-Reply-To: <Pine.LNX.4.21.0010191246070.6734-100000@like.mine.nu>


At 1:06 PM -0700 10/19/00, phandel@cise.ufl.edu wrote:
>On Thu, 19 Oct 2000, Scott Hankin wrote:
>
>>  vector: 300 at pc = c016d060, lr = c016c8f4, msr = 9032, sp = c07b1cc0
>>  [c07b1c10]
>>  dar = 7ac, dsisr = 40000000
>>  current = c07b0000, pid = 1, comm = swapper
>>  mon>
>
>As Ben has suggested, take a look in the System.map file that was created
>to see where the problem is.  I've seen the same thing on my PowerCenter,
>and it turned out to be in do_fork(), but I haven't had the time to check
>out why that is dying.

It turned out that the pc was in do_install_cmap, and lr was in
atyfb_set_var.  The latter calls the former near the end of the
routine (check out drivers/video/atyfb.c:2940) but as to why it's
bombing, I have no clue.

Ben suggested:
>Looks like the driver is beeing passed garbage for the console number or
>the currcon. You can try adding some debug xmon_printf to atyfb.c to
>locate what's going on. I suspect a latent bug that is always present but
>will appear or not depending on the random content of memory.

I'm in the process of adding xmon_printf statements to see what is
coming in.  I'll try and take it from there.  Is there a way of
forcing a mon> dump?

- Scott

-----------------------------
Scott Hankin (shankin@rational.com)  In the beginning, there was nothing, then
Rational Software                    God said, "Let there be light."  And there
20 Maguire Road                      was light.  There was still nothing, but
Lexington, MA 02421                  you could see it a lot better.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-10-19 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19 17:13 2.4.0-test10 boot failure on Powerbook G3 Scott Hankin
2000-10-19 17:36 ` Benjamin Herrenschmidt
2000-10-19 17:44 ` Benjamin Herrenschmidt
2000-10-19 20:06 ` phandel
2000-10-19 20:51   ` Scott Hankin [this message]
2000-10-20  1:38     ` Paul Mackerras
2000-10-20 13:46       ` Scott Hankin

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='p04320400b61508915079@[172.21.170.210]' \
    --to=shankin@rational.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=phandel@cise.ufl.edu \
    /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