From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ssh-keygen seg fault
Date: Fri, 14 Jan 2011 09:07:52 +0100 [thread overview]
Message-ID: <20110114090752.5f01ade5@surf> (raw)
In-Reply-To: <AANLkTi=OafFhejBCDjz-rffd3_gFR99kzxcGP3o+EmEM@mail.gmail.com>
Hello Kyle,
On Thu, 13 Jan 2011 13:29:42 -0800
Kyle Hayes <kyle@greenmonitor.com> wrote:
> I am getting a seg fault when ssh-keygen tries to run and when sshd
> tries to start. Here is my set up:
>
> Buildroot: GIT checkout from 1/11/11
> Kernel: 2.6.37
> Initrd type: CPIO/gzip
>
> machine: DMP eBox 3100 (PC-compatible x86 machine w/256MB of RAM)
>
> I've got extlinux installed, the kernel boots fine and I get a login
> prompt. However, I see errors that ssh-keygen and sshd are seg
> faulting.
>
> I would appreciate any tips on how to debug/fix this. Buildroot is
> exactly the system I was looking for.
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.
So the best you could do is use gdbserver on the target and a
cross-gdb (both can be built by Buildroot) and start ssh-keygen without
gdbserver in order to find the location of the segfault in ssh-keygen.
That would really in understanding the issue.
Are you sure that the Vortex 86DX supports all instructions of i486 ?
Are you sure that the FPU is compatible ? The documentation of the
Vortex 86DX states that it has a FPU, but I don't know if it's the same
as the one in normal x86 CPUs. Maybe you could try to build Buildroot
with BR2_SOFT_FLOAT=y (config options: "Use software floating point by
default").
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 8:07 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 [this message]
2011-01-14 9:24 ` Will Moore
2011-01-14 9:40 ` Thomas Petazzoni
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=20110114090752.5f01ade5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox