From: "claus" <claus.baumgartner@netsonic.fi>
To: linuxppc-embedded@ozlabs.org
Subject: MPC8270 with preemptible kernel stucks in early console write
Date: Thu, 20 Oct 2005 16:52:11 +0300 (EEST) [thread overview]
Message-ID: <1795.194.9.254.253.1129816331.squirrel@webmail.netsonic.fi> (raw)
Hi there,
I'm porting the 2.6.13.2 kernel to a custom board with a MPC8270.
If I compile the kernel preemptible then it gets stuck at the following
line in the cpm_uart_console_write function:
while ((bdp->cbd_sc & BD_SC_READY) != 0)
;
The early_console output works fine in the beginning of the boot but then
it gets stuck after the line "checking if image is initramfs...it isn't
(no cpio magic); looks like an initrd" is printed. The problem doesn't
seem to have anything to do with the initramfs detection though.
I can see with the debugger that the descriptors are OK and the buffers
are filled with correct data but it seems that the SCC is not sending the
characters and the main core is stuck waiting for a descriptor to be
ready for use.
Everything works fine if the kernel is not configured preemptible.
Has anyone else had similar behavior?
Any ideas?
-Claus-
reply other threads:[~2005-10-20 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1795.194.9.254.253.1129816331.squirrel@webmail.netsonic.fi \
--to=claus.baumgartner@netsonic.fi \
--cc=linuxppc-embedded@ozlabs.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