linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Eli Brin <eli.brin@rokonet.co.il>
Cc: "'VanBaren,
	Gerald (AGRE)'" <Gerald.VanBaren@smiths-aerospace.com>,
	"'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Watchdog timer reset
Date: Thu, 12 Aug 2004 14:52:16 +0200	[thread overview]
Message-ID: <20040812125221.482DDC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 12 Aug 2004 14:35:08 +0200." <023EF71CB65AA949A2C510353690C86B027FB4@rokonet-e.rokonet.co.il>


In message <023EF71CB65AA949A2C510353690C86B027FB4@rokonet-e.rokonet.co.il> you wrote:
>
> But, strangely, if I don't do any printk() and printf() no resets.
>
> Can the printing to console from kernel/user "block" the kernel for so long?

Yes, printk() can block the kernel for a long  time.  Try  increasing
the  console  baudrate,  and  or not using output to a serial port at
all.

> Where is the MMU support?

What do you mean?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
It is dangerous to be right on a subject  on  which  the  established
authorities are wrong.                                    -- Voltaire

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

  reply	other threads:[~2004-08-12 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 12:35 Watchdog timer reset Eli Brin
2004-08-12 12:52 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-12 14:11 Eli Brin
2004-08-12 13:14 VanBaren, Gerald (AGRE)
2004-08-11 11:05 Eli Brin

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=20040812125221.482DDC109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Gerald.VanBaren@smiths-aerospace.com \
    --cc=eli.brin@rokonet.co.il \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).