All of lore.kernel.org
 help / color / mirror / Atom feed
From: indexer <indexer@internode.on.net>
To: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 14658] Regression in efi.c
Date: Mon, 23 Nov 2009 21:41:06 +1030	[thread overview]
Message-ID: <4B0A6DCA.70805@internode.on.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0911231034090.24119@localhost.localdomain>

Thomas Gleixner wrote:
> On Mon, 23 Nov 2009, indexer wrote:
>   
>>> 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?
>>>
>>>       
>> I had already done a similar bisect to this in private conversation to Huang
>> Ying, and is what prompted me to expand my bisect out. I redid it regardless
>> and will send you the information.
>>
>> commit 74fca6a42863ffacaf7ba6f1936a9f228950f657
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>> Date:   Wed Sep 9 15:13:59 2009 -0700
>>
>>    Linux 2.6.31
>>
>> Makefile |    2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>     
>
> So you are saying that 
>  
>   
>> # good: [7135a71b19be1faf48b7148d77844d03bc0717d6] aoe: allocate unused
>> request_queue for sysfs
>> git bisect good 7135a71b19be1faf48b7148d77844d03bc0717d6
>>     
>
> which is the last code changing commit before the 2.6.31 release is
> booting fine, but with the release commit which merily changes the
> Makefile it is not ?
>   
I dont know, I will test this as soon as possible. I might change the 
bisect parameters a bit, but really im quite new to all this. It may 
also be a possibility it is gen-patches breaking it as i reported 
2.6.30-gentoo was the broken kernel. Either way, the fact remains that 
on 2.6.31 and higher vanilla it is broken.
>   
>> PS - The fact remains i still cant efi boot in 2.6.32-rc7, so this bug still
>> exists, and I will keep doing what i can to help track this down.
>>     
>
> Sure, but I hope we agree that it does not make much sense to search
> 2.6.31..now when we already know that 2.6.31 is not booting and the
> change which causes the problem is between 2.6.30 and 2.6.31.
>
> Thanks,
>
> 	tglx
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   
 Oh i have no issues agreeing with you, but its really confusing me, and 
i of course may have made an error in what i reported. I am after all 
only human, and i might have made a mistake, and this is the first time 
i have ever submitted a bug, let alone found one like this. The end 
product is that 2.6.32 doesn't boot, but maybe the last working version 
was not 2.6.30-rc8, maybe it was a 2.6.31 kernel. I might redo the 
bisect and try this out again, as i'm quite intent on finding the source 
of this. I will also see if i can get my hands on another x86_64 linux 
install with efi to test it on a different machine to see if it is 
hardware specific to my computer. For the record i am running a late 
2009 macbook pro gen 5 rev 3, efi version 1.7 with refit and elilo.

William

  reply	other threads:[~2009-11-23 11:11 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   ` [Bug 14658] Regression in efi.c Thomas Gleixner
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 [this message]
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=4B0A6DCA.70805@internode.on.net \
    --to=indexer@internode.on.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.