All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Boot hang with stack protector on x86_64
Date: Fri, 22 Feb 2008 11:29:37 +1100 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0802221121340.20800@us.intercode.com.au> (raw)

I've been getting an immediate hang on boot since:

e06b8b98da071f7dd78fb7822991694288047df0 kbuild: allow -fstack-protector to take effect

This is on an x86_64 system (actually an Intel SDV -- so it might be 
"special").

My .config has the following:

CONFIG_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR_ALL=y

Let me know if you need more information.


Interestingly, git-bisect was unable to identify the changeset, and 
reliably mis-identified this as the problem:

71c044752cdae89136862495f244d37073e2cf66 V4L/DVB (7080): zr364xx: add support for Pentax Optio 50

(which I don't even build).


- James
-- 
James Morris
<jmorris@namei.org>

             reply	other threads:[~2008-02-22  0:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  0:29 James Morris [this message]
2008-02-22  1:14 ` Boot hang with stack protector on x86_64 Arjan van de Ven
2008-02-22  7:59 ` Regression [Was: Boot hang with stack protector on x86_64] Sam Ravnborg
2008-02-22  9:36   ` Ingo Molnar
2008-02-22 10:33     ` James Morris
2008-02-22 12:17       ` Ingo Molnar
2008-02-22 13:02         ` James Morris
2008-02-22 13:27           ` Ingo Molnar
2008-02-23  6:18           ` Ingo Molnar
2008-02-23  7:37             ` Ingo Molnar
2008-02-24 22:53               ` James Morris
2008-02-25  8:23                 ` Ingo Molnar
2008-02-22 15:43   ` Linus Torvalds
2008-02-22 15:59     ` Arjan van de Ven
2008-02-22 16:12     ` Sam Ravnborg

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=Xine.LNX.4.64.0802221121340.20800@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.