From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ssh-keygen seg fault
Date: Fri, 14 Jan 2011 10:40:16 +0100 [thread overview]
Message-ID: <20110114104016.252e7f90@surf> (raw)
In-Reply-To: <469243A17FE74439A7BBB6F327046F20@beraninstruments.com.local>
Hello,
On Fri, 14 Jan 2011 09:24:19 -0000
"Will Moore" <will.moore@beraninstruments.com> wrote:
> > Hard to say since we can't reproduce without having the hardware. I
> > suspect that on a "normal" x86 CPU, sshd and ssh-keygen are working
> > fine.
>
> I am working on a *similar* platform (vortex86dx VDX6354 embedded PC104)
> with buildroot for some time. I have dropbear working without problems.
Ok, good to know. We don't know if Kyle is using dropbear of the
full-fledged openssh. That might make a difference.
> > Are you sure that the Vortex 86DX supports all instructions of i486 ?
>
> I think it does.
>
> > Are you sure that the FPU is compatible ?
>
> I think it is.
>
> Certainly I have had no problems associated with running a buildroot
> generated i486 toolchain.
Ok, great.
> I think your problem may be the kernel config. Can I suggest that you
> download the X-Linux sources from http://www.dmp.com.tw/tech/os-xlinux/ then
> use the kernel configuration for the vortex86dx as your kernel
> configuration? X-Linux is currently stuck at 2.6.29.6 and I have had
> problems moving to more recent kernels (gdbserver no longer stopped at
> breakpoints, kernel panics at boot). YMMV. As X-Linux is provided by DM&P
> who make the vortex86dx I have taken the "safe" approach and stuck with
> 2.6.29.6 too and used their kernel configuration verbatim. Please note: I
> am unclear what is in the eBOX 3100 and so what the differences between this
> and the VDX6354 are. If the eBOX is actually a vortex86sx (no FPU) then I
> have also previously used the VSX6154 which contains the vortex86sx with
> buildroot using the X-Linux kernel configuration for vortex86sx.
You could probaby diff their 2.6.29.6 kernel with the official
2.6.29.6, and see what their changes were, port them over to a new
kernel release and even get them merged so that you can benefit from
newer kernel versions.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-14 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:29 [Buildroot] ssh-keygen seg fault Kyle Hayes
2011-01-14 8:07 ` Thomas Petazzoni
2011-01-14 9:24 ` Will Moore
2011-01-14 9:40 ` Thomas Petazzoni [this message]
2011-01-14 17:00 ` Kyle Hayes
2011-01-14 17:19 ` Thomas Petazzoni
2011-01-14 19:29 ` Kyle Hayes
2011-01-14 21:04 ` Michael S. Zick
2011-01-14 22:04 ` Kyle Hayes
2011-01-14 22:07 ` Kyle Hayes
2011-01-17 22:23 ` Kyle Hayes
2011-01-18 0:12 ` Kyle Hayes
2011-01-19 10:29 ` Peter Korsgaard
2011-01-19 17:50 ` Kyle Hayes
2011-01-19 19:14 ` Peter Korsgaard
2011-01-19 19:21 ` Kyle Hayes
2011-01-20 16:49 ` Kyle Hayes
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=20110114104016.252e7f90@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.