From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: starting >=2.6.36 FATAL: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader
Date: Wed, 23 Feb 2011 13:16:28 -0800 [thread overview]
Message-ID: <4D65792C.8070703@tlinx.org> (raw)
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite
boot loader
Starting with 2.6.36, I started getting the above message.
It didn't seem what options I pruned out of the kernel
ipv6 support, iptables support, any thing I could think of
that would be a 'large chunk of space', nothing would make
it "fit" the way 2.6.35 did.
I didn't turn on options from options from 2.6.35 -> 2.6.36,
but did turn on things like BIOS blk throttling which seemed
low cost. I set the lower BIOS reserved amount to 4K, which
seemed to be the default under the old system (?), though
this system hasn't ever been tested w/standby or hibernate
so don't know if this is a correct setting, but is unlikely relevant.
So where did this extra length come from?
I *hoped* it was a fluke w/26.36, that would disappear in 26.37...but
nep. In searching for causes I saw one message pointing to the
XEN subsystem, but I made sure to remove that on both setups and that
made no difference.
So what's caused the sudden bump and how do I get around it?
next reply other threads:[~2011-02-23 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 21:16 Linda Walsh [this message]
2011-04-11 22:23 ` starting >=2.6.36 FATAL: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader Linda Walsh
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=4D65792C.8070703@tlinx.org \
--to=lkml@tlinx.org \
--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