Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] rcS segfault
Date: Thu, 13 Mar 2008 14:58:50 +0100	[thread overview]
Message-ID: <1205416731.8626.17.camel@localhost> (raw)
In-Reply-To: <47D929C7.9010706@mimc.co.uk>

On Thu, 2008-03-13 at 13:19 +0000, Mark Jackson wrote:
> I'm running the Atmel ATSTK1000 AVR32 dev kit.
> 
> I have checked out the latest buildroot, and done a ...
> 
> # make atstk1002_defconfig
> # make
> 
> All the packages and the kernel compile okay.
> 
> But when I boot the dev kit, I get the following error:-
> 
> rcS[186]: segfault at 7f89c000 pc 2ab13878 sp 7f89ab54 ecr 24

This is because of one of the bash patches, remove the bash32-011 patch.
You will need to update bash32-012 patch to reflect that.

It might be related to a bug in GCC, I do not recall exactly now.

> Can't open /dev/ttyS0: No such file or directory
> Can't open /dev/ttyS0: No such file or directory
> ...
> 
> The uarts appear to have been created okay ...
> 
> atmel_usart.0: ttyS0 at MMIO 0xffe01000 (irq = 7) is a ATMEL_SERIAL
> atmel_usart.2: ttyS2 at MMIO 0xffe01800 (irq = 9) is a ATMEL_SERIAL
> 
> Can anyone shed some light on what might be going on with the rcS script ?
>

See above :)

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

      reply	other threads:[~2008-03-13 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 13:19 [Buildroot] rcS segfault Mark Jackson
2008-03-13 13:58 ` Hans-Christian Egtvedt [this message]

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=1205416731.8626.17.camel@localhost \
    --to=hans-christian.egtvedt@atmel.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