From: "Max Alekseyev" <maxale@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22 booting hangs after "INIT: version 2.86 booting"
Date: Wed, 11 Jul 2007 18:31:10 -0700 [thread overview]
Message-ID: <d3dac270707111831v508e7c56w966df5bc2e7f855e@mail.gmail.com> (raw)
In-Reply-To: <d3dac270707111413j42ac7a0eif032636a9018df66@mail.gmail.com>
It happened that this weird behavior was caused by gcc-4.2 compiler.
After recompiling the kernel with gcc-4.1 all troubles have gone.
Max
On 7/11/07, Max Alekseyev <maxale@gmail.com> wrote:
> Hello!
>
> I have trouble with booting linux kernel 2.6.22 from kernel.org on my
> AMD dual-Opteron 250 system.
> The booting stops right after printing line "INIT: version 2.86
> booting". Nothing happens after that, but it is not a hardware hang as
> keyboard leds respond to pressing Caps/Num lock keys.
>
> If I boot with init=/bin/sh parameter I successfully get into the
> shell but attempts to run scripts from /etc/rcS.d/ all end up with
> Segmentation faults, e.g.:
>
> # sh -x /etc/rcS.d/S01glibc.sh
> ++ uname -s
> Segmentation fault
>
> I am not sure where these segfaults happen as running programs like
> 'uname' directly from the shell works OK.
>
> The 2.6.22 configuration is derived from the working 2.6.21 one. The
> kernel 2.6.21 boots on the very same system without any problems.
> Any suggestions?
>
> Thanks,
> Max
>
next prev parent reply other threads:[~2007-07-12 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 21:13 Max Alekseyev
2007-07-12 1:31 ` Max Alekseyev [this message]
2007-07-14 1:34 ` Adrian Bunk
2007-07-14 3:45 ` Max Alekseyev
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=d3dac270707111831v508e7c56w966df5bc2e7f855e@mail.gmail.com \
--to=maxale@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®