From: Keith Mannthey <kmannth@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: James Smart <james.smart@Emulex.Com>, Richard Lary <rlary@us.ibm.com>
Subject: gcc and kernel build trouble report
Date: Fri, 12 Mar 2010 15:38:05 -0800 [thread overview]
Message-ID: <1268437085.7745.62.camel@keith-laptop> (raw)
Hello,
At the start of the week I moved kernels forwarded. I tried
2.6.34-rc1 and 2.6.33-git15. The lpfc fiber channel driver was failing
to load and generating a hardware level pci bus fault that was resetting
the server. There is a small thread on linux-scsi from when I started.
Tried forward porting know working versions of the driver to the new
kernels but it did not fix the problem. I have to reason to suspect the
actual code in the driver is not really involved with the issue.
I booted whole older kernels until I sorted out that somewhere post
2.6.33 stock that issue started. I am not 100% sure where in the kernel
commits the problem starts I just know if is after 2.6.33.
It was identified that an alternate .config file worked and I decided
to dig on the config options.
I narrowed the config change down to:
CONFIG_CC_OPTIMIZE_FOR_SIZE
I have to set CONFIG_CC_OPTIMIZE_FOR_SIZE=y else I get a pci fault
while failing to load the lpfc driver. As I understand this passes a
different -O flag to the build.
Relevant details:
Hardware: IBM x3550m2 server. Current Intel based 2 socket system,
nothing fancy.
GCC: gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux)
Kernels: For sure, 2.6.34-rc1, 2.6.33-git15 have the problem. If the 10
or so 2.6.33 and before kernels trees I have booted I did not encounter
the issue.
Config: CONFIG_CC_OPTIMIZE_FOR_SIZE=y or bad things happen. I booted a
ton of .config changes, 100% sure this is it, it has been triple
checked.
All in all not a fun experience and I don't really have the skills to
fix this issue. I am going to try a different gcc version when I get a
few cycles.
Any suggestions on what to do with this gcc / kernel build issue? I
found it a little unsettling.
Thanks,
Keith Mannthey
LTC FS-Dev
next reply other threads:[~2010-03-12 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 23:38 Keith Mannthey [this message]
2010-03-13 10:57 ` Mikael Pettersson
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=1268437085.7745.62.camel@keith-laptop \
--to=kmannth@us.ibm.com \
--cc=james.smart@Emulex.Com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlary@us.ibm.com \
/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®