public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: initramfs /init freeze
Date: Fri, 02 May 2008 01:22:16 +0000	[thread overview]
Message-ID: <200805012122.17186.vapier@gentoo.org> (raw)
In-Reply-To: <7b5883fc0804281204l7bf2f9e8me942dfc0628f30@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]

On Monday 28 April 2008, Kristoffer Ericson wrote:
> On Mon, 28 Apr 2008 21:04:49 "Roni Feldman" wrote:
> > I'm experiencing odd behavior on an SH4 setup: I have an embedded
> > initramfs in the kernel image.
> > The kernel boots fine but the sequence freezes after
> > run_init_process("/init") is executed.
> >
> > I say "freeze" because I tried code that only does "return 0;" and I
> > even wrote an init.s with
> > a _start function that jmp's to address 0 (and was supposed to cause
> > an exception, but nothing
> > appeared in ttySC1, not even a panic for the exit of the init process).
> >
> > All the printk()'s are visible, and the console handover from sercon0
> > to ttySC1 seems to work
> > fine (I have no trouble doing printk's before the call to kernel_execve).
> >
> > I also tried both static and dynamic linking when I wrote the empty
> > main().
>
> I believe the dynamic linking issue was in pre glibc 2.3.4 (atleast on SH3)
> so shouldn't be an issue atm.

and static seems to fail the same way ...

you could try enabling magic sysrq on your system.  otherwise, jtag/kgdb would 
be very useful just to see where the processor is stuck.

> > Busybox as a shell and an /init shell script seems to suffer from the
> > same symptoms.
> >
> > My setup:
> > cpu: SH7751R LE configuration
> > kernel: 2.6.25-rc8
> > gcc: Gentoo 4.1.2 p1.0.2 with glibc 2.7
> >
> > I started to suspect my too-new glibc, so now I'm struggling with
> > crossdev to compile a uclibc
> > toolchain.
>
> I know glibc 2.3.x / 2.4.x / 2.5.x works well, but never tried 2.7. Usually
> though its gcc thats causing the issues. But you should step back and build
> it with older gcc/glibc just to make sure.
>
> For reference I usually use gcc 3.4.5 & glibc 2.3.6 for kernel builds.

glibc-2.7 seems to work fine on my systems ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2008-05-02  1:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 19:04 initramfs /init freeze Roni Feldman
2008-04-28 19:32 ` Kristoffer Ericson
2008-05-02  1:22 ` Mike Frysinger [this message]
2008-05-02 11:53 ` Roni Feldman
2008-05-03 23:40 ` Mike Frysinger

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=200805012122.17186.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=linux-sh@vger.kernel.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