From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
indexer@internode.on.net, Feng Tang <feng.tang@intel.com>,
bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14658] Regression in efi.c
Date: Sun, 22 Nov 2009 18:49:53 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0911221817200.24119@localhost.localdomain> (raw)
In-Reply-To: <200911212017.nALKHLSC029634@demeter.kernel.org>
On Sat, 21 Nov 2009, bugzilla-daemon@bugzilla.kernel.org wrote:
Switched to email. Please reply by mail (reply-to-all) and not in the
bugzilla.
> --- Comment #1 from Rafael J. Wysocki <rjw@sisk.pl> 2009-11-21 20:17:21 ---
> Caused by:
>
> commit 7bd867dfb4e0357e06a3211ab2bd0e714110def3
That's completely bogus. That commit is not in 2.6.31. It was merged in the
2.6.32 merge window.
>From the original bug report:
http://marc.info/?l=linux-kernel&m=125846988820120&w=4
> I would like to report a possible regression in efi.c with kernels
> 2.6.31 , 2.6.32-rc5 and 2.6.32.rc7.
>
> Attempting to boot x86_64 with elilo succeeds using 2.6.30 . Using the
> same config cannot boot with any of the 3 afore mentioned kernels.
So the problem exists with 2.6.31 already which excludes the above
commit.
The above commit indeed caused problems on 64bit efi systems in
2.6.32-rc. The fix was merged between 32-rc5 and 32-rc6.
The bisect was done with:
git bisect start
# good: [59a3759d0fe8d969888c741bb33f4946e4d3750d] Linux 2.6.30-rc7
git bisect good 59a3759d0fe8d969888c741bb33f4946e4d3750d
# bad: [156171c71a0dc4bce12b4408bb1591f8fe32dc1a] Linux 2.6.32-rc7
while the bisect should have be done with
good 2.6.30
bad 2.6.31
William, could you please go through the bisect pain again?
Thanks,
tglx
next parent reply other threads:[~2009-11-22 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14658-6666@http.bugzilla.kernel.org/>
[not found] ` <200911212017.nALKHLSC029634@demeter.kernel.org>
2009-11-22 17:49 ` Thomas Gleixner [this message]
2009-11-23 2:42 ` indexer
[not found] ` <EADF0A36011179459010BDF5142A457501CFFF3AE2@pdsmsx502.ccr.corp.intel.com>
2009-11-23 6:56 ` indexer
2009-11-23 9:45 ` Thomas Gleixner
2009-11-23 11:11 ` indexer
2009-11-25 0:35 ` indexer
2009-11-25 0:50 ` Huang Ying
2009-11-25 2:25 ` indexer
2009-11-25 9:42 ` indexer
2009-11-26 7:40 ` Tang, Feng
2009-11-29 16:43 ` indexer
2009-11-21 14:59 2.6.32-rc8-git1: Reported regressions 2.6.30 -> 2.6.31 Rafael J. Wysocki
2009-11-21 15:02 ` [Bug #14658] Regression in efi.c Rafael J. Wysocki
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=alpine.LFD.2.00.0911221817200.24119@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=feng.tang@intel.com \
--cc=indexer@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
Powered by JetHome