From: Sam Ravnborg <sam@ravnborg.org>
To: Michael Guntsche <mike@it-loops.com>,
Oliver Hartkopp <oliver@hartkopp.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
mjt@tls.msk.ru, mmarek@suse.cz
Subject: Re: 2.6.33-rc1 Reboot right after bootloader
Date: Sun, 20 Dec 2009 09:46:56 +0100 [thread overview]
Message-ID: <20091220084656.GA485@merkur.ravnborg.org> (raw)
In-Reply-To: <20091219233457.GA4288@trillian.comsick.at>
On Sun, Dec 20, 2009 at 12:34:57AM +0100, Michael Guntsche wrote:
> Good evening,
>
> I took me some time but I tracked down my reboot problem. The culprit is
> commit
>
> 4a2ff67c88211026afcbdbc190c13f705dae1b59: kbuild: fix bzImage build for
> x86
>
> The system I am compiling the kernel on has dash as its defaults shell.
> With the commit applied I get an instant reboot, reverting the patch
> makes it work again.
> If I switch my default shell to bash it works BOTH times.
> I do not know why the shell makes a difference here though.
> The version of dash is 0.5.5.1 from debian unstable.
Hi Michael & Oliver.
Just to check what is going wrong here could you try to execute the following two commands:
printf \\xa8\\x51\\x37\\x00 > x ; hexdump x
/usr/bin/printf \\xa8\\x51\\x37\\x00 > x ; hexdump x
echo -ne \\xa8\\x51\\x37\\x00 > x ; hexdump x
Please try as above and also with full path to printf (/usr/bin/printf)
On my system it looks like this:
$ printf \\xa8\\x51\\x37\\x00 > x ; hexdump x
0000000 51a8 0037
0000004
$ /usr/bin/printf \\xa8\\x51\\x37\\x00 > x ; hexdump x
0000000 51a8 0037
0000004
$ echo -ne \\xa8\\x51\\x37\\x00 > x ; hexdump x
0000000 51a8 0037
0000004
Sam
next prev parent reply other threads:[~2009-12-20 8:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 23:34 Michael Guntsche
2009-12-20 8:46 ` Sam Ravnborg [this message]
2009-12-20 9:10 ` Johannes Stezenbach
2009-12-20 10:38 ` Michael Tokarev
2009-12-20 11:10 ` Michael Tokarev
2009-12-20 11:38 ` Michael Tokarev
2009-12-20 9:11 ` Michael Guntsche
2009-12-20 10:03 ` [PATCH] kbuild: correct size calculation of bzImgae / fix x86 boot Sam Ravnborg
2009-12-20 10:20 ` Oliver Hartkopp
2009-12-20 10:28 ` Willy Tarreau
2009-12-20 10:47 ` Michael Tokarev
2009-12-20 13:09 ` Willy Tarreau
2009-12-20 11:19 ` Michael Tokarev
2009-12-20 12:02 ` Andreas Schwab
2009-12-20 12:18 ` Sam Ravnborg
2009-12-21 12:23 ` Michal Marek
2009-12-21 13:50 ` Andreas Schwab
2009-12-20 14:11 ` Sam Ravnborg
2009-12-21 14:17 ` Michal Marek
2009-12-21 16:28 ` Michael Guntsche
2009-12-21 19:53 ` Michael Tokarev
2009-12-21 20:48 ` Michael Guntsche
2009-12-21 18:28 ` H. Peter Anvin
2009-12-21 19:09 ` H. Peter Anvin
2009-12-20 13:50 ` Arkadiusz Miskiewicz
-- strict thread matches above, loose matches on Subject: below --
2009-12-18 14:06 2.6.33-rc1 Reboot right after bootloader Michael Guntsche
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=20091220084656.GA485@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@it-loops.com \
--cc=mjt@tls.msk.ru \
--cc=mmarek@suse.cz \
--cc=oliver@hartkopp.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
all inboxes | Powered by JetHome®