LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: emanuel stiebler <emu@ecubics.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ELDK 2.1.0, kernel 2.4.21, MPC8245, ntpd
Date: Tue, 19 Aug 2003 21:04:58 +0200	[thread overview]
Message-ID: <20030819190503.EA35FC59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 19 Aug 2003 12:40:23 MDT." <3F426F17.3090206@ecubics.com>


Dear Emanuel,

in message <3F426F17.3090206@ecubics.com> you wrote:
>
> I get a "Segmentation fault (core dumped)" on my system using ntpd.

This is caused by some (I2C based RTC's in "11 minute mode".

> I checked the archives, and there is one messeage about something like
> this on a 405.
>
> Is anybody working on this ? Did I missed some patches ?

We fixed this by making this mode configurable  (and  disable  it  by
default) in our version of the linuxppc_2_4_devel tree; the patch was
added on May 29, so just "cvs update" your source tree.


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
"A complex system that works is invariably found to have evolved from
a simple system that worked."             - John Gall, _Systemantics_

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

  parent reply	other threads:[~2003-08-19 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 18:40 ELDK 2.1.0, kernel 2.4.21, MPC8245, ntpd emanuel stiebler
2003-08-19 19:04 ` Mark Hatle
2003-08-19 19:32   ` emanuel stiebler
2003-08-19 19:04 ` Wolfgang Denk [this message]
2003-08-19 19:41   ` emanuel stiebler
2003-08-19 19:09 ` Dan Kegel
  -- strict thread matches above, loose matches on Subject: below --
2003-08-19 19:38 Johnson, Stephen

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=20030819190503.EA35FC59E4@atlas.denx.de \
    --to=wd@denx.de \
    --cc=emu@ecubics.com \
    --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