linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: kernel boot stuck at udbg_putc_cpm()
Date: Fri, 9 Jul 2010 00:35:43 -0700	[thread overview]
Message-ID: <AANLkTinNSzP-WvxC2kqZop2kvd1kSUMDuwI01GOBXApE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimUxcsTMXNPOFfJxybp8u7Wv7Mt_nhW1EE01RqG@mail.gmail.com>

I changed my toolchain and rebuilt the kernel image. This time all the
messages below magically displayed on the serial port. :-D Are all
these the early debugging messages?

> Here is the kernel log buf dump. Anything suspicious?
>
> <6>Using My MPC870 machine description
> <5>Linux version 2.6.33.5 (shawn@ubuntu) (gcc version 4.3.3 (GCC) )
> #10 Mon Jul 5 22:58:30 PDT 2010
> <7>Top of RAM: 0x8000000, Total RAM: 0x8000000
> <7>Memory hole size: 0MB
> <4>Zone PFN ranges:
...
<snipped>
...
> <7>time_init: decrementer frequency =3D 3.750000 MHz
> <7>time_init: processor frequency =A0 =3D 120.000000 MHz
> <6>clocksource: timebase mult[42aaaaab] shift[22] registered
> <7>clockevent: decrementer mult[f5c28f] shift[32] cpu[0]
> <7> =A0alloc irq_desc for 18 on node 0
> <7> =A0alloc kstat_irqs on node 0
> <7>irq: irq 4 on host /soc@fa200000/cpm@9c0/interrupt-controller@930
> mapped to virtual irq 18

Now the kernel stuck at the while loop that waits for transmitter fifo
to be empty. It seems that the CPM UART stopped working in the middle
of printing a message. I'm using minicom to connect to the serial
port. I heard minicom is problematic. Will it be the cause here?

(gdb) target remote ppcbdi:2001
Remote debugging using ppcbdi:2001
0xc00f348c in cpm_uart_console_write (co=3D<value optimized out>,
    s=3D0xc0174df3 "console [ttyCPM0] enabled, bootconsole disabled\n", cou=
nt=3D48)
    at /home/rayan/wti/code/wti-linux-2.6.33.5/arch/powerpc/include/asm/io.=
h:154
154     DEF_MMIO_IN_BE(in_be16, 16, lhz);
(gdb) next
1161                    while ((in_be16(&bdp->cbd_sc) & BD_SC_READY) !=3D 0=
)
(gdb) next
154     DEF_MMIO_IN_BE(in_be16, 16, lhz);
(gdb) next
1161                    while ((in_be16(&bdp->cbd_sc) & BD_SC_READY) !=3D 0=
)
(gdb) list
1156            for (i =3D 0; i < count; i++, s++) {
1157                    /* Wait for transmitter fifo to empty.
1158                     * Ready indicates output is ready, and xmt is doin=
g
1159                     * that, not that it is ready for us to send.
1160                     */
1161                    while ((in_be16(&bdp->cbd_sc) & BD_SC_READY) !=3D 0=
)
1162                            ;
1163
1164                    /* Send the character out.
1165                     * If the buffer address is in the CPM DPRAM, don't

Thanks,
-Shawn.

  parent reply	other threads:[~2010-07-09  7:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05  7:23 kernel boot stuck at udbg_putc_cpm() Shawn Jin
2010-07-06 20:21 ` Scott Wood
2010-07-06 23:08   ` Shawn Jin
2010-07-06 23:18     ` Scott Wood
2010-07-07  0:17       ` Shawn Jin
2010-07-07 15:42         ` Scott Wood
2010-07-09  7:35         ` Shawn Jin [this message]
2010-07-09 15:59           ` Scott Wood
2010-07-12  6:26             ` Shawn Jin
2010-07-12 18:23               ` Shawn Jin

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=AANLkTinNSzP-WvxC2kqZop2kvd1kSUMDuwI01GOBXApE@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).