From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: printk in m8xx_cpm_dpalloc() ???
Date: Wed, 24 Apr 2002 11:00:09 +0100 [thread overview]
Message-ID: <3CC68229.9020806@cambridgebroadband.com> (raw)
In-Reply-To: 3CC67EA1.79561746@imc-berlin.de
I had the same problem. printk() uses the CPM UART driver, and the initialisation of the CPM UART
driver uses m8xx_cpm_dpalloc(). If you make m8xx_cpm_dpalloc() use printk() then you create a
dependency loop. Don't do it.
Alex
Steven Scholz wrote:
> Hi there,
>
> I thought I put a printk just for debug reasons into the function
> m8xx_cpm_dpalloc (in arch/ppc/8xx_io/commproc.c).
>
> But now the kernel hangs while starting the CPM UART driver!
>
> ...
> Decrementer Frequency = 300000000/60
> m8xx_cpm_dpalloc: 8 bytes @ 0x0808 !!!!!!!!!!!!!
> m8xx_cpm_dpalloc: 16 bytes @ 0x0818 !!!!!!!!!!!!!
> Calibrating delay loop... 79.66 BogoMIPS
> Memory: 14596k available (1056k kernel code, 396k data, 52k init, 0k
> highmem)
> Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> CPM UART driver version 0.03
> ttyS00 at 0x0280 is a SMC !!!!!!!!!!!!!
> ...
> And nothing more happens!
>
> Does anyone know why?
>
> Cheers,
>
> Steven
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-24 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 9:45 printk in m8xx_cpm_dpalloc() ??? Steven Scholz
2002-04-24 10:00 ` Alex Zeffertt [this message]
2002-04-24 10:29 ` Steven Scholz
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=3CC68229.9020806@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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.